questions);
openstack-in...@lists.openstack.org
*Subject:* [openstack-dev] [neutron][devstack][keystone] Devstack
failures due to empty service catalogue
Hi All,
I noticed that our CI got hit sometime last night. Neutron is unable to
create private network as there is no Tenant
On Thu, Jan 22, 2015 at 09:42:50AM +0100, Jakub Libosvar wrote:
It is caused by using old python-openstackclient [1]. We should be using
= 1.0.2 - fix is about to be merged [2].
Thanks Jakub for helping me debug this on the IRC yesterday!
I hope these kind of backward incompatible changes can
Hi All,
I noticed that our CI got hit sometime last night. Neutron is unable to
create private network as there is no Tenant ID.
Please see the error log here - http://paste.openstack.org/show/159912/
It appears that keystone is not creating tenant. Keystone screen log did
not show anything
-in...@lists.openstack.org
*Subject:* [openstack-dev] [neutron][devstack][keystone] Devstack
failures due to empty service catalogue
Hi All,
I noticed that our CI got hit sometime last night. Neutron is unable to
create private network as there is no Tenant ID.
Please see the error log here
Subject: [openstack-dev] [neutron][devstack][keystone] Devstack failures due to
empty service catalogue
Hi All,
I noticed that our CI got hit sometime last night. Neutron is unable to create
private network as there is no Tenant ID.
Please see the error log here - http://paste.openstack.org/show
