Bug 2089696
| Summary: | CR reconciliation is stuck in daemonset lifecycle | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Constantin Vultur <cvultur> |
| Component: | Special Resource Operator | Assignee: | yevgeny shnaidman <yshnaidm> |
| Status: | CLOSED ERRATA | QA Contact: | Constantin Vultur <cvultur> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.11 | CC: | bthurber |
| Target Milestone: | --- | ||
| Target Release: | 4.11.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: | 2022-08-10 11:13:40 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: | |||
With the latest bundle from release-4.11 and over a an intensive create/delete of multiple charts the "lifecycle availability of the DaemonSet" was not seen anymore. Marking as 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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069 |
Description of problem: The daemonset lifecycle got stuck while deploying simple-kmod with the latest bundle Version-Release number of selected component (if applicable): release-4.11 How reproducible: Steps to Reproduce: 1. deploy SRO bundle from branch release-4.11 2. Create ns and configmap for simple-kmod 3. deploy simple-kmod Actual results: Deployment for simple-kmod errors out with error: Status: Conditions: Last Transition Time: 2022-05-24T09:09:31Z Message: Reason: ErrorHasOccurred Status: False Type: Progressing Last Transition Time: 2022-05-23T12:45:32Z Message: Reason: ErrorHasOccurred Status: False Type: Ready Last Transition Time: 2022-05-24T09:09:31Z Message: failed to deploy SpecialResource's chart: failed to reconcile SpecialResource /simple-kmod: cannot reconcile hardware states: failed to create state templates/1000-driver-container.yaml: failed to create resources from yaml for chart simple-kmod: failed to create object from YAML: failed to execute after crud for object simple-kmod/simple-kmod-driver-container-e383247e62b56585: failed to wait for resource, object simple-kmod/simple-kmod-driver-container-e383247e62b56585: waiting too long for resource DaemonSet simple-kmod/simple-kmod-driver-container-e383247e62b56585: lifecycle availability of the DaemonSet simple-kmod/simple-kmod-driver-container-e383247e62b56585 is not verified yet: old pod simple-kmod/simple-kmod-driver-container-e383247e62b56585-gvkrj is still running Reason: FailedToDeployChart Status: True Type: Errored State: Errored: failed to deploy SpecialResource's chart: failed to reconcile SpecialResource /simple-kmod: cannot reconcile hardware states: failed to create state templates/1000-driver-container.yaml: failed to create resources from yaml for chart simple-kmod: failed to create object from YAML: failed to execute after crud for object simple-kmod/simple-kmod-driver-container-e383247e62b56585: failed to wait for resource, object simple-kmod/simple-kmod-driver-container-e383247e62b56585: waiting too long for resource DaemonSet simple-kmod/simple-kmod-driver-container-e383247e62b56585: lifecycle availability of the DaemonSet simple-kmod/simple-kmod-driver-container-e383247e62b56585 is not verified yet: old pod simple-kmod/simple-kmod-driver-container-e383247e62b56585-gvkrj is still running Events: <none> Expected results: deployment to succeed Additional info: