Public bug reported:
The router namespace routes for other segment CIDRs, should have the
"via" parameter to the gateway IP address.
The environment I'm using has HA routers; I didn't test yet with DVR or
legacy routers.
For example, in my env [1]:
- Network: public
- Subnets:
(s1) aebc3fc1-d9
** Changed in: nova/victoria
Status: In Progress => Fix Released
** Changed in: nova/ussuri
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).
https://bugs.l
** Changed in: nova/ussuri
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).
https://bugs.launchpad.net/bugs/1907511
Title:
nova-multi-cell fails on stable branc
** Changed in: nova/victoria
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).
https://bugs.launchpad.net/bugs/1899541
Title:
archive_deleted_rows archives pci_d
** Changed in: nova/victoria
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).
https://bugs.launchpad.net/bugs/1897950
Title:
doc: setting [compute]max_disk_devi
** Changed in: nova/ussuri
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).
https://bugs.launchpad.net/bugs/1893284
Title:
Per-user quotas not scoped correctly
** Changed in: nova/ussuri
Status: Fix Committed => Fix Released
--
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/1907522
Title:
test_*_with_qos_min_bw_allocation f
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Changed in: nova/victoria
Status: New => Fix Released
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Changed in: nova/ussuri
Status: New => Fix Released
--
You received this
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Changed in: nova/ussuri
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpa
** Changed in: nova/ussuri
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).
https://bugs.launchpad.net/bugs/1903545
Title:
Nova does not support older than N -
** Changed in: nova/ussuri
Status: Fix Committed => Fix Released
** Changed in: nova/train
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.
** Changed in: nova/ussuri
Status: New => Fix Released
--
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/1900731
Title:
Huge pages in nova
Status in OpenStack Compu
** Changed in: nova/train
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).
https://bugs.launchpad.net/bugs/1898715
Title:
Live migration fails despite matching
** Changed in: nova/ussuri
Status: In Progress => Fix Released
** Changed in: nova/train
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).
https://bugs.laun
** Changed in: nova/ussuri
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).
https://bugs.launchpad.net/bugs/1896463
Title:
evacuation failed: Port update failed
** Changed in: nova/ussuri
Status: Fix Committed => Fix Released
--
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/1888395
Title:
live migration of a vm using the si
** Changed in: nova/train
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).
https://bugs.launchpad.net/bugs/1881944
Title:
nova-api returns empty block-device-ma
** Changed in: nova/ussuri
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).
https://bugs.launchpad.net/bugs/1799298
Title:
Metadata API cross joining instance_m
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-21.04
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.lau
Public bug reported:
Since few days all neutron-tempest-plugin-scenario jobs which runs with
"ha=True" setting (linuxbridge, openvswitch, openvswitch-iptables_hybrid) are
failing often due to failure to authenticate via ssh to the instances.
>From the console log it seems that in every such case
Public bug reported:
Until wallaby, ml2/ovn and networking-ovn, despite having support for
the Agent API, did not implement "delete" support. This means that when
scaling down compute nodes, etc. there are orphaned agents that cannot
be removed.
** Affects: neutron
Importance: Undecided
Public bug reported:
When a Neutron FIP is created with --dns-name and --dns-domain options
and respective project where the designate zone (either forward or
reverse) is located has not enough recordset quota - user will get an
HTTP 500 error.
Basically, Neutron should propagate the OverQuota er
** Changed in: neutron
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1746627
Title:
Reverse floating IP records are not removed when floating IP is
** Also affects: ubuntu
Importance: Undecided
Status: New
** Package changed: ubuntu => neutron (Ubuntu)
** Also affects: neutron (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also af
25 matches
Mail list logo