Public bug reported:
# Problem description
I'm using horizon of openstack wallaby on Ubuntu 20.04. I installed it
with devstack.
And I set ANGULAR_FEATURES.users_panel as True in local_settings.py. By
the way, the default value of ANGULAR_FEATURES.users_panel is False.
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Groovy)
@axino, if you think there's something here MAAS should do, please add
this to the Features category in discourse. i think this is working
pretty much as expected, given the circumstances.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a
Reviewed: https://review.opendev.org/c/openstack/glance/+/795772
Committed:
https://opendev.org/openstack/glance/commit/9b683678b2a19bb1069aace58e054150a78b5f6f
Submitter: "Zuul (22348)"
Branch:master
commit 9b683678b2a19bb1069aace58e054150a78b5f6f
Author: Erno Kuvaja
Date: Thu Jun 10
Yes, that is expected behaviour actually. Expected I mean until we
remove the legacy policy rules where the reader is nothing but the
owner.
We have not removed the legacy policy support yet and they are still
present as deprecated rule
-
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1933813
Title:
OSError: Premature eof waiting for privileged process error in
** No longer affects: nova
** Changed in: cinder
Assignee: Lee Yarwood (lyarwood) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1860913
Title:
Public bug reported:
When spawning a new instance, it's possible to force the instance to a
specific host by using a special 'availability_zone[:host[:node]]'
syntax for the 'availability_zone' field in the request. For example,
when using OSC:
openstack server create --availability-zone
As gibi said above, this is unlikely to be either a nova or a neutron
problem, but more likely a deployment problem. I don't believe the
various neutron log lines quoted have anything to do with the root
cause.
To help with the debugging:
What deployment software did you use?
Are you using
Reviewed: https://review.opendev.org/c/openstack/neutron/+/799162
Committed:
https://opendev.org/openstack/neutron/commit/ec550f5f52c5377f57499eeadd7e0d665dcdb73d
Submitter: "Zuul (22348)"
Branch:master
commit ec550f5f52c5377f57499eeadd7e0d665dcdb73d
Author: ramishra
Date: Fri Jul 2
Reviewed: https://review.opendev.org/c/openstack/neutron/+/799438
Committed:
https://opendev.org/openstack/neutron/commit/3b46df48476fdfd5a479ad537d190474f39e395b
Submitter: "Zuul (22348)"
Branch:master
commit 3b46df48476fdfd5a479ad537d190474f39e395b
Author: LIU Yulong
Date: Mon Jul 5
The nova stack trace shows that your nova-compute service cannot
connect to neutron on the URL
http://localhost:9696/v2.0/networks?id=163f0b54-e337-40ac-81af-
958c24ceeb7f . Did you verified that neutron API is available on that
URL?
>From this limited information I suspect that you have a
Public bug reported:
Description
===
It seems that nova may leak network interface in guest
if a port deletion is run in the middle of the a port attachment
in compute manager, attach_interface run atomically
the following tasks:
-update port in neutron(Binding)
-...
13 matches
Mail list logo
