Skip to content

4.7 RN: Add known Kuryr issue with UPI #29462

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maxwelldb merged 4 commits into from
Feb 12, 2021
Merged

4.7 RN: Add known Kuryr issue with UPI #29462

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a10b239
4.7 RN: Add known Kuryr issue with UPI
dulek Feb 12, 2021
b26a8f5
Restore BZ link
maxwelldb Feb 12, 2021
9d4dbc7
Update release_notes/ocp-4-7-release-notes.adoc
maxwelldb Feb 12, 2021
1b002c3
Adding plus signs
maxwelldb Feb 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions release_notes/ocp-4-7-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1014,6 +1014,36 @@ The root cause of this issue is unknown and no workaround currently exists.
+
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1913279[*BZ#1913279*])

* Installing a cluster on {rh-openstack} that uses Kuryr times out with the following messages during bootstrapping:
+
[source,terminal]
----
INFO Waiting up to 20m0s for the Kubernetes API at https://api.ostest.shiftstack.com:6443...
INFO API v1.20.0+ba45583 up
INFO Waiting up to 30m0s for bootstrapping to complete...
ERROR Attempted to gather ClusterOperator status after wait failure: listing ClusterOperator objects: Get "https://api.ostest.shiftstack.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp 10.46.44.166:6443: connect: connection refused
INFO Use the following commands to gather logs from the cluster
INFO openshift-install gather bootstrap --help
FATAL failed to wait for bootstrapping to complete: timed out waiting for the condition
----
+
The timeout is caused by changes in how Kuryr detects the {rh-openstack} Networking service (neutron) subnet of the cluster's nodes.
+
As a workaround, do not remove the control plane machine manifests as described by the "Creating the Kubernetes manifest and Ignition config files" section in the installation documentation. When you are instructed to run the following command:
Comment thread
maxwelldb marked this conversation as resolved.
+
[source,terminal]
----
$ rm -f openshift/99_openshift-cluster-api_master-machines-*.yaml openshift/99_openshift-cluster-api_worker-machineset-*.yaml
----
+
Run this command instead:
+
[source,terminal]
----
$ rm -f openshift/99_openshift-cluster-api_worker-machineset-*.yaml
----
+
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1927244[*BZ#1927244*])
Comment thread
maxwelldb marked this conversation as resolved.

Comment thread
maxwelldb marked this conversation as resolved.
[id="ocp-4-7-asynchronous-errata-updates"]
== Asynchronous errata updates
Expand Down