Bug 1898238 - Installer validations allow same floating IP for API and Ingress
Summary: Installer validations allow same floating IP for API and Ingress
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: egarcia
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks: 1901238
TreeView+ depends on / blocked
 
Reported: 2020-11-16 16:50 UTC by egarcia
Modified: 2021-02-24 15:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:33:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 4385 0 None closed Bug 1898238: Validate the the API and Ingress FIPs are not the same 2020-11-23 03:40:38 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:34:06 UTC

Description egarcia 2020-11-16 16:50:02 UTC
Version: 4.7
Platform: openstack
Please specify: IPI
What happened?

Install Config:
---
apiVersion: v1
baseDomain: 10.0.103.240.nip.io
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 2
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
metadata:
  name: wj45ios1019a
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 192.168.0.0/18
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  openstack:
    cloud: upshift
    computeFlavor: m1.large
    externalNetwork: provider_net_cci_8
    ingressFloatingIP: 10.0.100.234
    lbFloatingIP: 10.0.100.234
    octaviaSupport: '0'
    region: regionOne
    trunkSupport: '1'
publish: External

What should have happened: 
Error: cannot use IP 10.0.100.234 for both API and Ingress FIP

What happened:
nothing

Reproducible: always

Comment 3 weiwei jiang 2020-11-23 07:07:45 UTC
verified with 
$ ./openshift-install-4.7 version
./openshift-install-4.7 4.7.0-0.nightly-2020-11-22-204912
built from commit 68282c185253d4831514b20623b1717535c5e6f2
release image registry.svc.ci.openshift.org/ocp/release@sha256:fbcdfceb2cd55cae21792960d2fa1f371ac5ef4ab38a4e51cd5256c78934d03b

---
apiVersion: v1
baseDomain: 10.0.103.240.nip.io
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 2
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
metadata:
  name: wj45ios1019a
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 192.168.0.0/18
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  openstack:
    cloud: upshift
    computeFlavor: m1.large
    externalNetwork: provider_net_cci_8
    ingressFloatingIP: 10.0.102.198
    lbFloatingIP: 10.0.102.198
    octaviaSupport: '0'
    region: regionOne
    trunkSupport: '1'
publish: External
pullSecret: Hidden
sshKey: Hidden
Running: ./openshift-install-4.7 create manifests --dir /tmp/tmp.1aW3bwNNE0 2>&1
level=fatal msg=failed to fetch Master Machines: failed to load asset "Install Config": platform.openstack.ingressFloatingIP: Invalid value: "10.0.102.198": ingressFloatingIP can not be the same as apiFloatingIP

Comment 6 errata-xmlrpc 2021-02-24 15:33:36 UTC
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633


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