** Changed in: vitrage-dashboard
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1785606
Title:
When working with python3
Reviewed: https://review.openstack.org/588931
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=330c95090881a21eddf9f1483762e453330d6e45
Submitter: Zuul
Branch:master
commit 330c95090881a21eddf9f1483762e453330d6e45
Author: Takashi NATSUME
Date: Sun Aug 5 02:39:47 2018 +0
Reviewed: https://review.openstack.org/589006
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=00b585a1b94099e58177a04b204ca94fa0bc5908
Submitter: Zuul
Branch:master
commit 00b585a1b94099e58177a04b204ca94fa0bc5908
Author: Yikun Jiang
Date: Mon Aug 6 10:33:27 2018 +0800
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a-
0ubuntu1~18.04.2
---
cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.2) bionic-proposed; urgency=medium
* cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on
(LP: #1784685)
cloud-init (18.3-9-g2e62cb8
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a-
0ubuntu1~16.04.2
---
cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.2) xenial-proposed; urgency=medium
* cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on
(LP: #1784685)
cloud-init (18.3-9-g2e62cb8
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a-
0ubuntu1~16.04.2
---
cloud-init (18.3-9-g2e62cb8a-0ubuntu1~16.04.2) xenial-proposed; urgency=medium
* cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on
(LP: #1784685)
cloud-init (18.3-9-g2e62cb8
This bug was fixed in the package cloud-init - 18.3-9-g2e62cb8a-
0ubuntu1~18.04.2
---
cloud-init (18.3-9-g2e62cb8a-0ubuntu1~18.04.2) bionic-proposed; urgency=medium
* cherry-pick 3cee0bf8: oracle: fix detect_openstack to report True on
(LP: #1784685)
cloud-init (18.3-9-g2e62cb8
Reviewed: https://review.openstack.org/585629
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=633897ae549257789961014afa81cf209c0e05d5
Submitter: Zuul
Branch:master
commit 633897ae549257789961014afa81cf209c0e05d5
Author: zhubx007
Date: Wed Jul 25 12:12:27 2018 +0800
Reviewed: https://review.openstack.org/585639
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=446abc41bfe562bcc1d2933bd42d0225c6f3cb53
Submitter: Zuul
Branch:master
commit 446abc41bfe562bcc1d2933bd42d0225c6f3cb53
Author: zhubx007
Date: Wed Jul 25 14:08:50 2018 +0800
Public bug reported:
when neutron dns-integration is not enabled (the default devstack
configuration), key error for dns_name and dns_domain occurs when we
access the admin floating IP panel. The admin floating IP panel is
completely broken in this case.
** Affects: horizon
Importance: Criti
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/pike
Assignee: (unassigned) => s10 (vlad-esten)
** Changed in: nova/queens
Assignee: (unassigned) => s10 (vlad-esten)
**
*** This bug is a duplicate of bug 1746483 ***
https://bugs.launchpad.net/bugs/1746483
** This bug has been marked a duplicate of bug 1746483
Not able to boot from Volume / Volume snapshot when using isolated_images
--
You received this bug notification because you are a member of Yahoo!
As noted this isn't a bug, so marking it invalid. Would require a spec
to change this behavior, but I doubt we'd do it, since nova shouldn't
have access to the guest once it's created. You'd have to rebuild the
server if you wanted to change the hostname in the guest.
** Changed in: nova
St
Is this still an issue? If so, please explain what the issue is in more
detail - what is the user impact?
Conductor is now passing the migration record it creates down to the
compute, so I don't think RT creates it anymore and this shouldn't be an
issue. See:
https://github.com/openstack/nova/com
Looks like this is fixed for nova as of
https://review.openstack.org/#/c/539164/
** Tags added: api
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
*** This bug is a duplicate of bug 1777505 ***
https://bugs.launchpad.net/bugs/1777505
This isn't a nova bug, it's a devstack bug, and already fixed.
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: nova
Status: Confirmed => Invalid
** This bug has
Reviewed: https://review.openstack.org/589121
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f7eefaa9937f2fc1e05caee65334cdd0d93159c9
Submitter: Zuul
Branch:master
commit f7eefaa9937f2fc1e05caee65334cdd0d93159c9
Author: Yuval Adar
Date: Mon Aug 6 14:14:24 2018 +030
I believe this should be fixed in Nova Placement. Not sure this belongs
to tripleo.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
** Changed in: tripleo
Status: Triaged => Won't Fix
--
You received this bug notific
Public bug reported:
In environments where DVR is enabled and when an instance with floating
IPs is moved from one host to another (due to live migration or shelving
/ un-shelvinng) the Neutron server produces the following traceback:
Traceback (most recent call last):
File
"/usr/local/lib/pyt
Public bug reported:
Description
===
Periodic task update_available_resource takes 20 seconds for 100
instances on local storage:
https://github.com/openstack/nova/blob/stable/pike/nova/compute/resource_tracker.py#L694
Steps to reproduce
==
1. /etc/nova/nova.conf:
[DEFAUL
Public bug reported:
Description
===
Fail to delete a volume after detaching the volume using Cinder command.
[stack@undercloud~(tm5)]$ openstack volume list
+--+--+++---
Public bug reported:
Description of problem:
New qos policy delete action not working correctly and returning error not
found message.
How reproducible:
Every time
Actual results:
Try to delete qos policy. Returns error message.
Expected results:
Try to delete qos policy. Qos policy deleted.
Public bug reported:
openstack:Q
centos7.5
(openstack) compute service list
++--+--+--+-+---++
| ID | Binary | Host | Zone | Status | State | Updated
At |
++---
Public bug reported:
During reverting a resize or a migration Nova still hits the legacy
allocation handling code even if the migration is started without any
old compute or controller in the system. Search for "Doing legacy
allocation math" in [2] for examples.
It is caused by a faulty logic in
*** This bug is a duplicate of bug 1722959 ***
https://bugs.launchpad.net/bugs/1722959
** Changed in: cloud-init
Status: New => Invalid
** This bug has been marked a duplicate of bug 1722959
Implement Key-Value Pair Telemetry for Azure
--
You received this bug notification because
25 matches
Mail list logo
