Bug 1838032
Summary: | [IPI][OSP] installer fails on user-provided-network if .1 address is on use | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | David Sanz <dsanzmor> |
Component: | Installer | Assignee: | egarcia |
Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | egarcia, m.andre, pprinett |
Version: | 4.5 | Keywords: | UpcomingSprint |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:40:28 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
David Sanz
2020-05-20 11:51:15 UTC
Openstack DHCP takes the .1 address by default. I'm not sure we can do anything about this. This is happening in the context of BYO Network, the simple solution is to stop creating a router in this case. https://github.com/openshift/installer/pull/3632 should fix it. Also having problems with ingress_port: 12:55:20 level=error msg="Error: Error creating openstack_networking_port_v2: Expected HTTP response code [] when accessing [POST https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13696/v2.0/ports], but got 409 instead" 12:55:20 level=error msg="{\"NeutronError\": {\"message\": \"IP address 192.168.0.7 already allocated in subnet c15de955-d2f7-4c27-bc98-a583ba8ff7b6\", \"type\": \"IpAddressAlreadyAllocated\", \"detail\": \"\"}}" The issue with the router being created on user-provisioned networks is solved. @morenod do you mind reporting any further problem in a separate BZ? Marking as MODIFIED. Verified Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |