[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
ubuntu 18.04 uses netplan to manage networks, netplan could either use
NetworkManager or systemd-networkd
internally, but it does not use networking.
cloud-init.service explicitly depends on networking.service to complete which
might be problematic
because network service
This is a bug in the patch that we cherry-picked to queens doesn't match
what is in upstream stable/queens.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: horizon
Status: New => Invalid
** Changed in: cloud-archive
Status: New => Triaged
Public bug reported:
[Environment]
Xenial/Queens
Horizon 13.0.3 >
[Description]
Horizon horizon (3:13.0.3-0ubuntu2) introduced patch CVE-2020-29565, which
breaks X/Q clouds the reason
is that the allowed_host argument was introduced in 1.11
Public bug reported:
I've been seeing lots of failures caused by timeouts in
test_volume_backed_live_migration during the live-migration and
multinode grenade jobs, for example:
https://zuul.opendev.org/t/openstack/build/bb6fd21b5d8c471a89f4f6598aa84e5d/logs
During check_can_live_migrate_source
Public bug reported:
I ran into a problem when the network inside the newly created VM is not
working.
* Pre-conditions:
- the neutron ovs agent has not yet seen any ports from the VM network;
- any other bridge (except for the network in which the VM is created) is
recreated on the node.
*
Yes, only enabling the one service would explain why cloud-init isn't
fully running. If you enable the others, cloud-init should work as
expected.
Is there a reason you can't use the cloud image as your base in packer?
Then you shouldn't have to change anything about cloud-init at all.
Since it
** Changed in: cloud-archive/victoria
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1907686
Title:
ovn: instance unable to retrieve metadata
Status in
A translation bug should be fixed in https://translate.openstack.org/.
All translations are automatically imported, so there is nothing that the
horizon team can do.
** Project changed: horizon => openstack-i18n
--
You received this bug notification because you are a member of Yahoo!
This bug was fixed in the package neutron - 2:16.3.1-0ubuntu1.1
---
neutron (2:16.3.1-0ubuntu1.1) focal; urgency=medium
[ Hemanth Nakkina ]
* Fix to check L3 agent gateway port robustly (LP: #1883089)
- d/p/0001-L3-Check-agent-gateway-port-robustly.patch.
-- Chris
Public bug reported:
I have a keystone cluster running on 3 controller nodes. On each node,
the process is running under mod_wsgi daemon mode. Keystone version is
16.0.1
I am experiencing a problem which is caused by inconsistency between in-process
memory cache data and the database.
Here is
12 matches
Mail list logo
