Bug 2224523 - Instance creation fails if the IP address of the associated port is referred by allowed-address of another port
Summary: Instance creation fails if the IP address of the associated port is referred ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: async
: 17.1
Assignee: Greg Rakauskas
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 2190348
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-21 10:36 UTC by Rodolfo Alonso
Modified: 2023-08-30 20:38 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
In RHOSP networking environments, when creating a VM instance, do not bind the instance to a virtual port (vport). Instead, use a port whose IP address is not a member of another port's allowed address pair. + Binding a vport to an instance prevents the instance from spawning and produces an error message similar to the following: + ---- WARNING nova.virt.libvirt.driver [req-XXXX - - - default default] [instance: XXXXXXXXX] Timeout waiting for [('network-vif-plugged', 'XXXXXXXXXX')] for instance with vm_state building and task_state spawning.: eventlet.timeout.Timeout: 300 seconds ----
Clone Of: 2190348
Environment:
Last Closed: 2023-08-30 15:28:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26807 0 None None None 2023-07-21 10:37:26 UTC


Note You need to log in before you can comment on or make changes to this bug.