Closed kaovilai closed 1 year ago
Tried recreating the disconnected pod but with the pod's .spec.imagePullSecrets removed and the pod was able to get to running status. Perhaps another thing for openshift-velero-plugin to implement.
OADP-1.1 issue https://issues.redhat.com/browse/OADP-1487
Application YAML deployed
BuildConfigs triggered, builds, and push image to ImageStreams
image output: {&BuildStatusOutputTo{ImageDigest:sha256:5bf85296fbc9ab386a0e1cc153002db38637e23936a2593c261f72e236cbd0a7,}}
DeploymentConfig redeploy using image generated from new build
image-registry.openshift-image-registry.svc:5000/mongo-persistent/todolist-mongo-go@sha256:5bf85296fbc9ab386a0e1cc153002db38637e23936a2593c261f72e236cbd0a7
Pod is running
Backup successfully with imagestreamtag backedup
level=info msg="[istag-backup] Backing up imagestreamtag todolist-mongo-go:latest"
Destroy Namespace (everything gone, including imagestreams
Restore completed successfully
[istag-restore] Restoring imagestreamtag todolist-mongo-go:latest
[istag-restore] Local image: image-registry.openshift-image-registry.svc:5000/mongo-persistent/todolist-mongo-go@sha256:5bf85296fbc9ab386a0e1cc153002db38637e23936a2593c261f72e236cbd0a7
BuildConfig that got restored triggered another build
Build pushes a new todolist-mongo-go:latest image overriding previous restored :latest tag. However as seen in the next few steps the first restored SHAs should still be pullable.
DeploymentConfig create a new pod based on ConfigChange trigger due to ImageStreamTag update
Disconnected pod will have sha from build in original backup which should be pullable.
Expected: all pods are running
Actual: sometimes the disconnected pod would have ImagePullBackOff related issues due to registry Auth errors
oc registry login && docker pull
did verify that imagestreamtag sha can be pulled