[Bug 2083489] Re: Upgrading dbus tear down network

I am marking this bug as invalid, since this seems related to systemd reload instead and not a dbus issue. ** Changed in: dbus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchp

[Bug 2083489] Re: Upgrading dbus tear down network

This seems related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083489 Title: Upgrading dbus tear down network To manage notifica

[Bug 2083489] [NEW] Upgrading dbus tear down network

Public bug reported: While running a dist-ugprade on Jammy machines part of a Ceph cluster, dbus got updated ``` 2024-09-25 04:35:25 status triggers-pending dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:35:36 status triggers-pending dbus:amd64 1.12.20-2ubuntu4.1 2024-09-25 04:37:28 trig

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

Hello Mauricio, thanks for providing the nova patch. It worked as expected. I installed on a node with xsaves enabled and updated nova.conf # dpkg -l | grep nova ii nova-api-metadata 2:21.2.4-0ubuntu2.7~ppa3 all OpenStack Compute - met

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

One thing I notice is that the libvirt xml from EPYC at /usr/share/libvirt/cpu_map/x86_EPYC-Rome.xml ofc is not updated but also a new one for using -v4 is not rendered. That means I can't instruct nova to use EPYC-Rome-v4 with # grep -i epyc /etc/nova/nova.conf cpu_model = EPYC-Rome-v4 because

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

Hello Sergio, thanks for providing the patch. I have installed qemu on my test machine. The new epyc-rome-v4 is now listed by qemu ``` # qemu-system-x86_64 -enable-kvm -cpu help| grep -i epyc-rome-v x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-Rome-v2

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

Hello Sergio, I can help with testing. I have access to EPYC-Rome CPU machines. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048517 Title: EPYC-Rome model without XSAVES may break live mi

[Bug 1950186] Re: Nova doesn't account for hugepages when scheduling VMs

Even using a flavor with hw:mem_page_size='small' I am still able to request more memory of what is physically available. While the update of max_unit seems to be reverted to the original value when the compute node checks its records so can't be used as a valid workaround. -- You received this

[Bug 1950186] Re: Nova doesn't account for hugepages when scheduling VMs

This can be reproduced on Focal/ussuri: Computes: $ os resource provider list +--+-++--+--+ | uuid

[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table

I can confirm that on Bionic upgrading to 20.03.2-0ubuntu0.20.04.1~cloud0 fixed this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917475 Title: RBAC Permissions too strict for Port_Binding t

[Bug 1931275] [NEW] ovn-controller fails to start

Public bug reported: When using Openstack Ussuri with OVN 20.03 in Bionic and starting an ovn-controller this sometime fails with the following: 2021-06-07T14:13:34.803Z|1|vlog|INFO|opened log file /var/log/ovn/ovn-controller.log 2021-06-07T14:13:34.805Z|2|reconnect|INFO|unix:/var/run/op

[Bug 1928031] Re: neutron-ovn-metadata-agent AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl'

I am seeing same issue once we upgraded to 16.3.2 https://pastebin.canonical.com/p/F6NxGkrBcx/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928031 Title: neutron-ovn-metadata-agent AttributeError:

[Bug 1773765] Re: There is a possibility that 'running' notification will remain

Version in use: dpkg -l | grep masaka ii masakari-api 9.0.0-0ubuntu0.20.04.3~cloud0 all Virtual Machine High Availability (VMHA) for OpenStack - API Server ii masakari-common 9.0.0-0ubuntu0.20.04.3~cloud0 all

[Bug 1773765] Re: There is a possibility that 'running' notification will remain

We are still seeing this happening in bionic ussuri $ os notification list | grep running | a5a79aba-c3e3-464e-9b0b-3cedd272fd4d | 2021-02-18T04:57:01.00 | running | COMPUTE_HOST | 88eae267-fabc-48d2-b6cc-4acdb6f9b5e2 | {'event': 'STOPPED', 'cluster_status': 'OFFLINE', 'host_status': 'NORMA

[Bug 1839477] Re: Firewall group stuck in PENDING_UPDATE

** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839477 Title: Firewall group stuck in PENDING_UPDATE To manage notifications about this bug go to: https://bugs.lau

[Bug 1839477] [NEW] Firewall group stuck in PENDING_UPDATE

Public bug reported: neutron-common 2:14.0.2-0ubuntu1~cloud0 neutron-fwaas-common1:14.0.0-0ubuntu1~cloud0 neutron-plugin-ml2 2:14.0.2-0ubuntu1~cloud0 neutron-server 2:14.0.2-0ubuntu1~cloud0 python3-neutron 2:14.0.2-0ubuntu

[Bug 1813007] Re: Unable to install new flows on compute nodes when having broken security group rules

** Description changed: - It appears that we have found that neutron-openvswitch-agent appears to have a bug where a security group that has two different port ranges that overlap tied to the same parent security group will cause neutron to not be able to configure networks on the compute nodes