-
Bug
-
Resolution: Can't Do
-
Normal
-
None
-
4.10.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
One of the worker nodes was not able to go through with the upgrade due to it not being able to apply the new ocp-art version. Error seen on the cluster: Node ip-10-xx-xx-xxx.ec2.internal is reporting: "failed to update OS to quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ea41674620d30467f70352efa33f5335db701dff9a29e590ca9ab83553395780 : error running rpm-ostree rebase --experimental /run/mco-machine-os-content/os-content-920228627/srv/repo:14261ed9f09d893e744a03db41a0588d6041fe155ecea6edab7e7c7fd600a850 --custom-origin-url pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ea41674620d30467f70352efa33f5335db701dff9a29e590ca9ab83553395780 --custom-origin-description Managed by machine-config-operator: error: Transaction in progress: (null)\n: exit status 1
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
A workaround is restarting rpm-ostreed.service on the affected node
- relates to
-
OCPBUGS-15381 Upgrade stuck due to wedged rpm-ostreed.service
-
- Closed
-