Public bug reported:
++++++++++++++++++++++++
Problematic Environment:
++++++++++++++++++++++++
~~~
OS: Ubuntu 22.04
Kernel: 5.15.0-134-generic
OpenStack Release: 2023.1 aka Antelope
~~~
++++++
Issue:
++++++
Wanted to apply some nova overrides, so added that in ``user-variable``
~~~
nova_nova_conf_overrides:
libvirt:
cpu_mode: custom
cpu_models: EPYC-Milan
cpu_model_extra_flags: "-erms, -fsrm"
~~~
and ran the ``os-nova-install.yml`` applied to all node without the
issue,
* This playbook also restarts the compute services across the cluster.
After that all 100's of running instances was unreachable, ping was not
happened.
+++++++++++
Workaround:
+++++++++++
* To block the users immediately restarted openvswitch on all computes and
bring back the instance live, rechability form and users were able to access
the VM.
Looking for a resolution even if we restart the nova-computes on any
node.
Thanks,
cNilesh.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: neutron nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2106793
Title:
after running ``os-nova-install.yml`` lost instances connectivity Edit
Status in neutron:
New
Bug description:
++++++++++++++++++++++++
Problematic Environment:
++++++++++++++++++++++++
~~~
OS: Ubuntu 22.04
Kernel: 5.15.0-134-generic
OpenStack Release: 2023.1 aka Antelope
~~~
++++++
Issue:
++++++
Wanted to apply some nova overrides, so added that in ``user-
variable``
~~~
nova_nova_conf_overrides:
libvirt:
cpu_mode: custom
cpu_models: EPYC-Milan
cpu_model_extra_flags: "-erms, -fsrm"
~~~
and ran the ``os-nova-install.yml`` applied to all node without the
issue,
* This playbook also restarts the compute services across the cluster.
After that all 100's of running instances was unreachable, ping was
not happened.
+++++++++++
Workaround:
+++++++++++
* To block the users immediately restarted openvswitch on all computes and
bring back the instance live, rechability form and users were able to access
the VM.
Looking for a resolution even if we restart the nova-computes on any
node.
Thanks,
cNilesh.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2106793/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
