-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.15, 4.16
-
None
-
Moderate
-
None
-
uShift Sprint 263
-
1
-
False
-
-
-
Bug Fix
-
In Progress
Description of problem:
After boot, pods in 'openshift-gitops' namespace are showing ImagePullBackoff error. ImagePullPolicy in manifest is set to 'Always' $ cat /usr/lib/microshift/manifests.d/020-microshift-gitops/application-controller/argocd-application-controller-statefulset.yaml | grep imagePullPolicy: imagePullPolicy: Always
Version-Release number of selected component (if applicable):
4.15.z and 4.16.z
How reproducible:
Always, affecting off-line deployments
Steps to Reproduce:
1. Created a 'RHEL for Edge ISO' with 'microshift' and 'microshift-gitops' packages in blueprint.
2. Blueprint name = "gitops-os" description = "GitOps OS Blueprint" version = "1.0.0" modules = [] groups = [] distro = "" [[packages]] name = "microshift" version = "4.16.4" [[packages]] name = "microshift-gitops" version = "1.12.1" [[packages]] name = "openshift-clients" version = "4.16.0"
3. Deploy the ostree commit in a disconnected network. Ensure that MicroShift it comes online at first time.
4. reboot the node, pods in 'openshift-gitops' namespace are showing ImagePullBackoff error.
Actual results:
In a disconnected network, another rebooting the node, pods in 'openshift-gitops' namespace are showing ImagePullBackoff error.
Expected results:
In a disconnected networks, all embedded images must be in a Running state.
Additional info: