[Yahoo-eng-team] [Bug 1537076] Re: Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

2016-02-11 Thread Sean Dague
It seems really weird about why keystone just stops working. That is the thing that really needs to be sorted out. ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack

[Yahoo-eng-team] [Bug 1537076] Re: Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

2016-01-27 Thread OpenStack Infra
Reviewed: https://review.openstack.org/273129 Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=fde62528afd5c88737999a3deabeba6c2d389e88 Submitter: Jenkins Branch:master commit fde62528afd5c88737999a3deabeba6c2d389e88 Author: Dmitry Tantsur Date:

[Yahoo-eng-team] [Bug 1537076] Re: Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

2016-01-27 Thread Dmitry Tantsur
New finding: it looks like keystone does not even start when the failure happens. We should probably NOT fail Nova on start up if we can't connect to it... ** Also affects: nova Importance: Undecided Status: New ** Tags added: ironic -- You received this bug notification because you