Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Super Contributor.. Aaron_Corneliso Super Contributor..
Super Contributor..
537 views

Service Manager Service Portal error pointing to Operations Orchestration

I'm in the process of installing the SM Service Portal 9.51 version.  The install seemed to be going good, but has now stopped with a failure.  According to the below error it looks like it is trying to connect to HP Operations Orchestration.  We do not use OO so I'm wondering why it is getting an error on this.  Does the Service Portal install a part or all of OO during the install?  Is this needed to run the Service Portal or can we maybe skip this step somehow?  NOTE:  I've replaced actual server name below with "fqdn of Server".

fatal: [fqdn of server]: FAILED! => {
    "changed": false,
    "connection": "close",
    "content": "\n\n\n\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n<html lang=\"en\">\n<head>\n    <meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"/>\n    <title>HP Operations Orchestration</title>\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\n\n    <link href=\"/oo/features/theme/css/oo-theme.css\" rel=\"stylesheet\">\n    <script type=\"text/javascript\">\n        //this is a workaround to a defect in the glorious ie,\n        // apparently it throws an exception if we try to write to the console and the console is not open...\n        if (!window.console) {\n            window.console = {\n                log : function (obj) { /*do nothing here since the console is closed*/\n                }\n            };\n        };\n    </script>\n</head>\n\n<body>\n\n<div class=\"modal login-container container-fluid\">\n    <div class=\"row-fluid\">\n        <div class=\"span2\">\n            <img src=\"/oo/features/theme/images/HP_Blue_RGB_72_SM.gif\" />\n        </div>\n\n        <div class=\"container span10\">\n            <div>\n                <div id=\"header\" class=\"header-login\">Operations Orchestration</div>\n\n                <div class=\"modal-body form-container\">\n                    <div id=\"logout_label\">A general error has occurred. Contact your administrator for more details.</div>\n                </div>\n\n            </div>\n        </div>\n    </div>\n</div>\n</body>\n\n</html>\n",
    "content_type": "text/html;charset=UTF-8",
    "date": "Mon, 27 Mar 2017 14:48:37 GMT",
    "failed": true,
    "invocation": {
        "module_args": {
            "backup": null,
            "body": "{\"username\":\"admin\",\"password\":\"xxxxxxxx\",\"roles\":[{\"name\":\"ADMINISTRATOR\"},{\"name\":\"END_USER\"},{\"name\":\"EVERYBODY\"},{\"name\":\"PROMOTER\"},{\"name\":\"SYSTEM_ADMIN\"}]}",
            "body_format": "json",
            "content": null,
            "creates": null,
            "delimiter": null,
            "dest": null,
            "directory_mode": null,
            "follow": false,
            "follow_redirects": "safe",
            "force": false,
            "force_basic_auth": false,
            "group": null,
            "headers": {
                "Content-Type": "application/json"
            },
            "http_agent": "ansible-httpget",
            "method": "POST",
            "mode": null,
            "owner": null,
            "regexp": null,
            "remote_src": null,
            "removes": null,
            "return_content": false,
            "selevel": null,
            "serole": null,
            "setype": null,
            "seuser": null,
            "src": null,
            "status_code": [
                "200",
                "201"
            ],
            "timeout": 30,
            "unsafe_writes": null,
            "url": "https://fqdn of Server:8443/oo/rest/latest/users",
            "url_password": null,
            "url_username": null,
            "use_proxy": false,
            "validate_certs": false
        },
        "module_name": "uri"
    },
    "msg": "Status code was not [200, 201]: HTTP Error 500: Internal Server Error",
    "redirected": false,
    "server": "Apache-Coyote/1.1",
    "status": 500,
    "transfer_encoding": "chunked",
    "url": "https://fqdn of Server:8443/oo/rest/latest/users",
    "vary": "Accept-Encoding"
}
        to retry, use: --limit @/opt/hp/propel_complete_installer/ansible_content/deploy_rhel_complete.retry

0 Likes
4 Replies
Highlighted
Honored Contributor.. Ivis Honored Contributor..
Honored Contributor..

Re: Service Manager Service Portal error pointing to Operations Orchestration

Hi 

Did you manage to solve this? I have the same issue.. 

BR Ivis. 

0 Likes
Super Contributor.. Aaron_Corneliso Super Contributor..
Super Contributor..

Re: Service Manager Service Portal error pointing to Operations Orchestration

Unfortunately, I still haven't solved this issue.  I keep getting stuck at the same point.  I continue to work with our contractors to help.  If you find a solution, please post here.

Thanks

0 Likes
Visitor.. C ULKER
Visitor..

Re: Service Manager Service Portal error pointing to Operations Orchestration

You seem to be blocked on this step (/ansible_content/roles/oo/tasks/main.yml)

 

- name: "Setup the admin user in OO"
uri:
url: https://{{ ansible_fqdn }}:8443/oo/rest/latest/users
method: POST
body_format: json
body: '{"username":"admin","password":"","roles":[{"name":"ADMINISTRATOR"},{"name":"END_USER"},{"name":"EVERYBODY"},{"name":"PROMOTER"},{"name":"SYSTEM_ADMIN"}]}'
validate_certs: no
use_proxy: no
status_code: "200,201"

can you connect to your hp oo instance? (https://{{ ansible_fqdn }}:8443/oo)

You can check your oo install log :/opt/hp/oo/installer.log or the oo log /opt/hp/oo/central/var/logs also

 

 

0 Likes
Respected Contributor.. Hazem Dessouky Respected Contributor..
Respected Contributor..

Re: Service Manager Service Portal error pointing to Operations Orchestration

hello gents, i am facing the same error with SM 9.52 and SM 9.51, any clue whats the issue?? Did anyone solve it?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.