Bug 2127840

Summary: OVB stack creation failed, IPAddressGenerationFailureClient
Product: Red Hat OpenStack Reporter: Amol K <akahat>
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED NOTABUG QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17.1 (Wallaby)CC: cjeanner, mburns
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-19 10:22:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amol K 2022-09-19 08:26:40 UTC 
Description of problem:
OVB stack creation failed.

Actual results:

Resource CREATE failed: IpAddressGenerationFailureClient: resources.private_network.resources.router: No more IP addresses available on network 36e46f70-99ff-48f5-aa9d-7bbd22b6218a. 
Neutron server returns request_ids: ['req-db69b298-b605-4963-97e8-6132c2c26704']


Additional Info:
2022-09-15 13:45:49.696963 | TASK [ovb-manage : Fail if stack did not deploy successfully]
2022-09-15 13:45:49.815748 | primary | ERROR
2022-09-15 13:45:49.816042 | primary | {
2022-09-15 13:45:49.816079 | primary |   "msg": "Stack baremetal_13010 did not deploy successfully. See the stack status message above."
2022-09-15 13:45:49.816104 | primary | }
2022-09-15 13:45:49.851758 |
Comment 2 Cédric Jeanneret 2022-09-19 09:28:09 UTC 
Hello there,

I guess the issue is:
No more IP addresses available on network 36e46f70-99ff-48f5-aa9d-7bbd22b6218a

namely, the mentioned network is too small... Without any more info, it's hard to say.

Also, 17.1 isn't out nor even close to GA nor Beta - lowering the severity.

Please provide more information about the env, and check the network range.
Comment 3 Amol K 2022-09-19 10:22:43 UTC 
I've seen this issue while back but in zuul retry it's resolved. I could see the jobs are passing. 
Closing this issue.