That behavior was intended: in case of misconfiguration the server needs to
stop loading and notify about the error.
Also, we can't just skip duplicate because we don't know which one is correct.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification
The no_admin_token_auth-paste.ini should be generated by the test itself
(during setup of the class):
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/tests/test_no_admin_token_auth.py?h=stable%2Fhavana#n41
There are a couple of things that could be causing this issue: bad
permission
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core
Milestone: None => 1.17.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/897645
Title:
ju
The `_` function is installed in the entry of the keystone
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1250309
Title:
I think this subject should be address.
I reopened the bug.
** Changed in: neutron
Status: Expired => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1212338
Title:
Auto-creat
It's via rpm, so yeah, it's a packaging bug. Note that RDO already
handles it in their neutron spec for the linuxbridge sub-package:
https://github.com/redhat-openstack/openstack-neutron/blob/master
/openstack-neutron.spec#L189
** Changed in: neutron
Status: Incomplete => Invalid
--
You
I think it is better we have metadata-agent in agent-list. It is not
integrated yet.
** Changed in: neutron
Status: Invalid => Confirmed
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
I can still see the contradictory code in horizon/__init__.py. Should that be
fixed too?
I mean, if we decide that we do require Dashboard, Panel and PanelGroup, then
maybe we should remove the try-except and warnings? If we decide that they are
optional after all, then we should remove the asse
Metadata agent is not a subject for scheduling so it doesn't report it's state,
hence it is not listed in the output.
It's an intended behavior.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
IMO, the bug reported is a question rather than deviation from
functionality.
The CLI command "keystone user-role-list --user " will work
according to the environment variables specified via OS_* variables (
OS_TENANT_NAME )
We have to specify the tenant name explicitly, if the user is different
Duplicated blueprint https://blueprints.launchpad.net/horizon/+spec
/vpnaas-ui-update
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs
11 matches
Mail list logo
