[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1766703
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1784837
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Confirmed
** Changed in: keystone
Status: Confirmed => Triaged
** Changed in: keystone
Importance: Undecided => Critical
** Changed in: keystone
Assignee:
Reviewed: https://review.openstack.org/616444
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8ad11697f95400d6453d502c5a04b9f3f05827c1
Submitter: Zuul
Branch:master
commit 8ad11697f95400d6453d502c5a04b9f3f05827c1
Author: liuyamin
Date: Thu Nov 8 16:00:12 2018 +0800
Reviewed: https://review.openstack.org/613633
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=50e3fe5c945c3d3241f4607a57a0e67a3f55b21d
Submitter: Zuul
Branch:master
commit 50e3fe5c945c3d3241f4607a57a0e67a3f55b21d
Author: Morgan Fainberg
Date: Fri Oct 26 09:19:57
Public bug reported:
EphemeralIPv4Network exists in success too early on network devices with
link down.
When run against a network interfaces which already has the requested ip
configuration and routes but hapeens to be "link down",
EphemeralIPv4Network.bringup_device exits immediately after
There is an online data migration:
https://review.openstack.org/#/c/377138/62/nova/objects/resource_provider.py@917
But it's only when listing/showing resource providers. The allocation
candidates code must be getting the providers and relying on the
root_provider_id using sqla model objects
Public bug reported:
I have multiple backends set up in an S-1 devstack and make this call:
data.json:
[
{
"op": "add",
"path": "/locations/-",
"value": {"url":
"https://review.openstack.org/static/title.svg?e=6b20e64d6472edfb0e38b30442683e8a;,
Reviewed: https://review.openstack.org/615362
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=9f937c5ab745fd6612ec105195350417fc8a1b63
Submitter: Zuul
Branch:master
commit 9f937c5ab745fd6612ec105195350417fc8a1b63
Author: caoyuan
Date: Sat Nov 3 09:45:23 2018 +0800
Looks like the failure is here?
http://logs.openstack.org/26/615126/5/check/tempest-
full/69d913a/controller/logs/screen-n-super-
cond.txt.gz#_Nov_06_19_48_37_408999
The test is failing to unshelve the server because unshelve fails during
scheduling b/c of that placement failure. I saw this the
Hmm, nova-api is failing to RPC cast to the nova-conductor service. What
is the value of the [conductor]/topic configuration option in nova.conf?
It should be 'conductor'. Do you have it set to 'nova'?
https://docs.openstack.org/nova/queens/configuration/config.html#conductor.topic
Otherwise
Public bug reported:
When using ceph in nova and glance, the image in nova will be cloned
from glance images. Then the parent image in nova images will be pointed
to glance pool. This will cause a lower availability. when glance pool
is broken, the vm image is affected too.
For higher
Public bug reported:
I think fa-eye-slash should be used when hiding passwords. fa-eye should
be used when displaying passwords.
** Affects: horizon
Importance: Undecided
Assignee: pengyuesheng (pengyuesheng)
Status: In Progress
--
You received this bug notification because
13 matches
Mail list logo
