Bug 2224523
| Summary: | Instance creation fails if the IP address of the associated port is referred by allowed-address of another port | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Rodolfo Alonso <ralonsoh> |
| Component: | documentation | Assignee: | Greg Rakauskas <gregraka> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 17.1 (Wallaby) | CC: | chrisw, ekuris, gregraka, jamsmith, jlibosva, mflusche, ralonsoh, scohen, yatanaka |
| Target Milestone: | async | Keywords: | Triaged |
| Target Release: | 17.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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
----
|
Story Points: | --- |
| Clone Of: | 2190348 | Environment: | |
| Last Closed: | 2023-08-30 15:28:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2190348 | ||
| Bug Blocks: | |||
|
Comment 11
Greg Rakauskas
2023-08-30 15:28:36 UTC
|