Bug 1903660 - Cannot install with Assisted Installer on top of IPv6 since network provider is not started
Summary: Cannot install with Assisted Installer on top of IPv6 since network provider ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: All
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Alexander Constantinescu
QA Contact: Ori Amizur
Depends On:
TreeView+ depends on / blocked
Reported: 2020-12-02 15:23 UTC by Ori Amizur
Modified: 2023-09-15 00:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:37:21 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 954 0 None closed Bug 1903660: Don't error when expected master node amount is not met 2021-02-11 19:38:45 UTC
Github openshift ovn-kubernetes pull 406 0 None closed Bug 1903660: Handle pruning of unhealthy db files on disk 2021-02-11 19:38:45 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:37:55 UTC

Description Ori Amizur 2020-12-02 15:23:45 UTC
Description of problem:

Unable to install Openshift cluster above IPv6 with Assisted Installer since the bootstrap of OVNKubernetes plugin expects all the master nodes according to the replicas definition to be up before it starts the plugin.

The reason for the above is that in Assisted Installer there is no dedicated bootstrap node.  Instead, initially there are 2 master nodes and a bootstrap.  When the installation of the 2 master nodes completes, the bootstrap becomes the third master.

 Here is the place in the code that checks that the number of available masters is the same as the replicas count:


Version-Release number of selected component (if applicable):

Actual results:

The network provider is not started

Expected results:

The expected behavior is that if there is at least a single master node, the network plugin should be started.

Comment 1 Alexander Constantinescu 2020-12-02 16:06:16 UTC
Setting this to not-blocker as it's not a regression.

Comment 2 Eran Cohen 2020-12-02 16:07:18 UTC
This is how cluster-authentication-operator is stating without 3 master nodes:

This is what assisted-instalelr is doing to allow etcd to start with just 2 master nodes:

This is what etcd dose for allowing the assisted-installer to start today:

This is the new implementation for scaling etcd:

Comment 3 Rom Freiman 2020-12-02 20:28:28 UTC
The question is if it's possible to do something for 4.7 timeframe with a very limited scope (protected by a flag that assisted installer will set).
For 4.8 it should be addressed in a correct way.

Comment 5 Alexander Constantinescu 2021-01-28 12:07:30 UTC
@Ori Amizur: can you coordinate with QE and validate that the assisted install now works?

Comment 6 Anurag saxena 2021-02-08 16:43:10 UTC
As per @oamizur , he has verified that the fix works fine on 4.7. Ori, pleae feel free to update verification steps here if needed

Comment 9 errata-xmlrpc 2021-02-24 15:37:21 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.


Comment 10 Red Hat Bugzilla 2023-09-15 00:52:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days

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