Public bug reported:
Description
===
I want to show region_name in mete_date. Do you have any Suggestions and
ideas?
In the instance execution 'curl
http://169.254.169.254/openstack/2013-04-04/mete_date.json ', the
information of the current instance region (region_name) is
Public bug reported:
Description
===
I want to show region_name in mete_date. Do you have any Suggestions and
ideas?
In the instance execution 'curl
http://169.254.169.254/openstack/2013-04-04/mete_date.json ', the
information of the current instance region (region_name) is
This bug was fixed in the package nova - 2:21.0.0~b2~git2020021008
.1fcd74730d-0ubuntu2
---
nova (2:21.0.0~b2~git2020021008.1fcd74730d-0ubuntu2) focal; urgency=medium
* d/p/monkey-patch-original-current-thread-active.patch: Cherry-picked from
Public bug reported:
Description
===
We have two deployments, one with ~150 bare metal nodes, and another with ~300.
These are each managed by one nova-compute process running the Ironic driver.
After upgrading from the Ocata release, we noticed that instance launches would
be stuck in
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1853160
Title:
uptime code does not work on FreeBSD with python
Reviewed: https://review.opendev.org/706868
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=e65d4a131a7ebc02261f5df69fa1b394a502f268
Submitter: Zuul
Branch:master
commit e65d4a131a7ebc02261f5df69fa1b394a502f268
Author: Balazs Gibizer
Date: Mon Feb 10 15:48:04 2020
** Also affects: neutron
Importance: Undecided
Status: 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/1863982
Title:
Upgrade from Rocky to Stein, router namespace
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Importance: Undecided => Low
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
Assignee: (unassigned) => Balazs Gibizer (gibizer)
--
You received this bug
Hello Jorge, or anyone else affected,
Accepted neutron into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
** Changed in: neutron
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
nova 2:19.0.1-0ubuntu2 has been released for a while now.
** Changed in: cloud-archive/stein
Status: Fix Committed => Fix Released
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
@jorge, thanks. I've uploaded neutron 2:10.0.7-0ubuntu1~cloud3 which
will revert them.
** Changed in: cloud-archive/ocata
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
While instance has disabled port security its not able to reach DHCP service.
Looks like the change [1] introduced this regression.
Port has [unknown] address set:
This should not be an issue with Python 3, which is all we support now.
Closing as a result.
** Changed in: python-novaclient
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Public bug reported:
The following was discovered using Fedora 30 and a virt-preview job in
the below change:
zuul: Add the fedora-latest-virt-preview job to the experimental queue
https://review.opendev.org/#/c/704573/
Feb 19 16:45:21.405351 fedora-30-rax-ord-0014691277 nova-compute[2019]:
Public bug reported:
Upgrade All-in-one from Rocky to Stein.
Upgrading finished but the router namespace disappears.
Before:
ip netns list
qrouter-79658dd5-e3b4-4b13-a361-16d696ed1d1c (id: 1)
qdhcp-4a183162-64f5-49f9-a615-7c0fd63cf2a8
Public bug reported:
Most probably a follow-up of https://review.opendev.org/#/c/704084/ dropping
py2.7 testing, stable branches reviews now fail on
neutron-tempest-plugin-designate-scenario job with failure like:
2020-02-20 08:05:43.987705 | controller | 2020-02-20 08:05:43.987 | Collecting
27 matches
Mail list logo
