** Description changed:
I noticed that qemu-guest-agent does not start automatically in VMs
using image ubuntu-24.04-server-cloudimg-amd64.img (see exact versions
at the end) in a libvirt/qemu/kvm VM. I would expect it to start
automatically after each boot.
This is what I first notic
Public bug reported:
I noticed that qemu-guest-agent does not start automatically in VMs
using image ubuntu-24.04-server-cloudimg-amd64.img (see exact versions
at the end) in a libvirt/qemu/kvm VM. I would expect it to start
automatically after each boot.
This is what I first noticed from the Deb
Sorry for the slow followup.
I did reconfigure my ovn environment so I could change the internal
network to a geneve network and with that did the same test as above. I
was able to ping 10.0.0.2 from vm0 both before and after the floating IP
creation. So currently I'm not able to reproduce the bug
Sorry for the slow reaction. Thanks for the bug report. I was able to
reproduce the bug by your instructions - with traffic too.
** Changed in: neutron
Status: New => Triaged
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you are a m
I built a master ovn devstack (first using vlan networks) to reproduce
this but I could not, this is what I did:
# physical bridge, bridge mappings, hostname
sudo ovs-vsctl --may-exist add-br br-physnet0
sudo ovs-vsctl set Open_vSwitch .
external_ids:ovn-bridge-mappings=public:br-ex,physnet0:br-p
Could you please provide a set of commands leading to this error? Also
what behavior you expected and what happened instead?
I'm asking this because there are many moving parts here. If you meant
the enable_snat bit in the API, I'm afraid it's impossible to
automatically set that, since we can't p
** Tags added: ovn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922089
Title:
[ovn] enable_snat cannot be disabled once enabled
To manage notifications about this bug go to:
https://bugs.launchpa
As far as I can remember the enable_snat bit in the
external_gateway_info of a router should only control the generic SNAT-
ting of all traffic from internal networks to the external. Support for
floating IPs should be orthogonal to the enable_snat bit.
Could you please elaborate on the connectivi
** Tags added: ovn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924765
Title:
[ovn] fip assignment to instance via router with snat disabled is
broken
To manage notifications about this bug go
** Changed in: neutron
Status: In Progress => Triaged
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923453
Title:
[focal-wallaby] Ser
** Changed in: neutron
Status: In Progress => Triaged
** Changed in: neutron
Importance: Undecided => High
** Tags added: wallaby-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
FYI: Running openstack (master) with python2 will not work for long any
more since in ussuri we dropped support for it:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Most projects did not willingly broke python2 compatibility but dropped
python2 gate jobs, so it's only
12 matches
Mail list logo
