yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95467
[Bug 2101182] [NEW] Live-migrations failing on stx-openstack with openstack@2024.1 (Caracal)
Public bug reported:
Description
===========
There is a problem regarding a neutron policy that was added during the Bobcat version and is interfering with the live-migration.
2025-03-05 20:20:12.284 1 WARNING nova.scheduler.utils [None
req-378c4684-cf0a-457b-8b72-9da70b590d58
a23a091108164ce3bd0c3ccb56b5bc41 2188be8c27ae46d99ab83aa5d62d7e44 - -
default default] [instance: 92176c56-64b0-4ef6-91e7-0b88ff579744]
Setting instance to ERROR state.: nova.exception.Forbidden:
rule:create_port_binding is disallowed by policy
There is another launchpads talking about exactly this problem: https://bugs.launchpad.net/nova/+bug/2051907
https://bugs.launchpad.net/openstack-helm/+bug/2078002
Steps to reproduce
==================
1. Create VM:
openstack server create --flavor=<flavor id or name> --image=<image id or name> --network <network id or name> <vm name>
2. Request live migration:
openstack server migrate --live--block-migration <vm id>
3. Verify VM in error state:
openstack server list --all or
openstack server show <vm id>~
4. Check logs from nova pod:
kubectl logs <nova-pod> -n openstack | grep ERROR
** Affects: starlingx
Importance: Undecided
Status: New
** Project changed: nova => starlingx
** Description changed:
Description
===========
There is a problem regarding a neutron policy that was added during the Bobcat version and is interfering with the live-migration.
2025-03-05 20:20:12.284 1 WARNING nova.scheduler.utils [None
req-378c4684-cf0a-457b-8b72-9da70b590d58
a23a091108164ce3bd0c3ccb56b5bc41 2188be8c27ae46d99ab83aa5d62d7e44 - -
default default] [instance: 92176c56-64b0-4ef6-91e7-0b88ff579744]
Setting instance to ERROR state.: nova.exception.Forbidden:
rule:create_port_binding is disallowed by policy
- There is another launchpad talking about exactly this problem:
- https://bugs.launchpad.net/nova/+bug/2051907
-
+ There is another launchpads talking about exactly this problem: https://bugs.launchpad.net/nova/+bug/2051907
+ https://bugs.launchpad.net/openstack-helm/+bug/2078002
Steps to reproduce
==================
1. Create VM:
- openstack server create --flavor=<flavor id or name> --image=<image id or name> --network <network id or name> <vm name>
+ openstack server create --flavor=<flavor id or name> --image=<image id or name> --network <network id or name> <vm name>
2. Request live migration:
- openstack server migrate --live--block-migration <vm id>
-
+ openstack server migrate --live--block-migration <vm id>
3. Verify VM in error state:
openstack server list --all or
openstack server show <vm id>~
4. Check logs from nova pod:
kubectl logs <nova-pod> -n openstack | grep ERROR
** Summary changed:
- Live-migrations failing on stx-openstack
+ Live-migrations failing on stx-openstack with openstack@2024.1 (Caracal)
--
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/2101182
Title:
Live-migrations failing on stx-openstack with openstack@2024.1
(Caracal)
Status in StarlingX:
New
Bug description:
Description
===========
There is a problem regarding a neutron policy that was added during the Bobcat version and is interfering with the live-migration.
2025-03-05 20:20:12.284 1 WARNING nova.scheduler.utils [None
req-378c4684-cf0a-457b-8b72-9da70b590d58
a23a091108164ce3bd0c3ccb56b5bc41 2188be8c27ae46d99ab83aa5d62d7e44 - -
default default] [instance: 92176c56-64b0-4ef6-91e7-0b88ff579744]
Setting instance to ERROR state.: nova.exception.Forbidden:
rule:create_port_binding is disallowed by policy
There is another launchpads talking about exactly this problem: https://bugs.launchpad.net/nova/+bug/2051907
https://bugs.launchpad.net/openstack-helm/+bug/2078002
Steps to reproduce
==================
1. Create VM:
openstack server create --flavor=<flavor id or name> --image=<image id or name> --network <network id or name> <vm name>
2. Request live migration:
openstack server migrate --live--block-migration <vm id>
3. Verify VM in error state:
openstack server list --all or
openstack server show <vm id>~
4. Check logs from nova pod:
kubectl logs <nova-pod> -n openstack | grep ERROR
To manage notifications about this bug go to:
https://bugs.launchpad.net/starlingx/+bug/2101182/+subscriptions