Bug 1956959
Summary: | ipv6 disconnected sno crd deployment hive reports success status and clusterdeployrmet reporting false | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | bjacot |
Component: | assisted-installer | Assignee: | Daniel Erez <derez> |
assisted-installer sub component: | Deployment Operator | QA Contact: | bjacot |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | urgent | CC: | alazar, aos-bugs, keyoung, mfilanov, sasha |
Version: | 4.8 | Keywords: | TestBlocker, Triaged |
Target Milestone: | --- | ||
Target Release: | 4.8.0 | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | AI-Team-Hive | ||
Fixed In Version: | OCP-Metal-v1.0.20.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 23:06:09 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
bjacot
2021-05-04 18:26:13 UTC
The reason that we found was related to extra space in the ssh-key. This space is trimmed in the backend and the controller sees this as a change and tries to update the backend again, causing a reconcile loop. There is a good reason for the trim and it resolves a bug that if there is a new line in the ssh key the boot will fail. so the solution should be that the controller match back-end behavior and trim ssh key before comparing it to the backend. In addition, we could try to avoid calling updates in specific cases or specific states. I was able to perform an SNO deployment and updated my automation to trim blank space. 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.8.2 bug fix and security 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-2021:2438 |