Grafana Status code was 503 and not [200]: HTTP Error 503: Service Unavailable

Bug #1796229 reported by men
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Undecided
Unassigned

Bug Description

queens kolla:

I can log in at this address. http://51.0.1.170:3000/login

ntrol01 closed.\r\n')
<control01> ESTABLISH SSH CONNECTION FOR USER: None
<control01> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/c95568e57f control01 '/bin/sh -c '"'"'rm -f -r /root/.ansible/tmp/ansible-tmp-1538709662.1-265960612579780/ > /dev/null 2>&1 && sleep 0'"'"''
<control01> (0, '', '')
The full traceback is:
  File "/tmp/ansible_IWlsjW/ansible_module_uri.py", line 535, in main
    js = json.loads(u_content)
  File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")

fatal: [control01]: FAILED! => {
    "attempts": 10,
    "cache_control": "no-cache",
    "changed": false,
    "connection": "close",
    "content": "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n",
    "content_type": "text/html",
    "invocation": {
        "module_args": {
            "attributes": null,
            "backup": null,
            "body": null,
            "body_format": "raw",
            "client_cert": null,
            "client_key": null,
            "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": {},
            "http_agent": "ansible-httpget",
            "method": "GET",
            "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"
            ],
            "timeout": 30,
            "unsafe_writes": null,
            "url": "http://51.0.1.170:3000/login",
            "url_password": null,
            "url_username": null,
            "use_proxy": true,
            "validate_certs": true
        }
    },
    "msg": "Status code was 503 and not [200]: HTTP Error 503: Service Unavailable",
    "redirected": false,
    "status": 503,
    "url": "http://51.0.1.170:3000/login"
}

NO MORE HOSTS LEFT *****************************************************************************************************************************************
        to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry

PLAY RECAP *************************************************************************************************************************************************
ceph01 : ok=178 changed=4 unreachable=0 failed=0
ceph02 : ok=95 changed=2 unreachable=0 failed=0
ceph03 : ok=95 changed=2 unreachable=0 failed=0
control01 : ok=473 changed=92 unreachable=0 failed=1
control02 : ok=382 changed=70 unreachable=0 failed=0
control03 : ok=382 changed=70 unreachable=0 failed=0
localhost : ok=1 changed=0 unreachable=0 failed=0

Revision history for this message
men (keyi) wrote :

Modify user and password,Then the installation is normal:
 /usr/share/kolla-ansible/ansible/roles/grafana/tasks/post_config.yml

 user: "admin"
password: "ml6H21Itaxbb7tYNhAwHqgZBDPMZeCEfEVjN7ZBy"

Changed in kolla:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.