Bug 2151109 - Failed to create an instance with error Failed to allocate the network "aborted: Failed to allocate the network(s), not rescheduling"
Summary: Failed to create an instance with error Failed to allocate the network "abort...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: z5
: 16.2 (Train on RHEL 8.4)
Assignee: Slawek Kaplonski
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-06 07:06 UTC by Chorong Park
Modified: 2023-07-24 09:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-24 09:58:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20711 0 None None None 2022-12-06 07:26:11 UTC

Description Chorong Park 2022-12-06 07:06:38 UTC 
Description of problem:
The network allocation failed during the VM creation.

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform release 16.2.1 GA (Train)
Red Hat Enterprise Linux release 8.4 (Ootpa)
puppet-neutron-15.6.0-2.20210601015533.7f36270.el8ost.2.noarch

How reproducible:
They intermittently fail to create an instance,
but I'm not clear on why the instance creation is failing.

Steps to Reproduce:
1.
2.
3.

Actual results:
Instances fail.

Expected results:
Instances to not fail.

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