Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When rebooting the cluster, existing Labs are out of sync #193

Closed
blues-man opened this issue Feb 19, 2021 · 2 comments
Closed

When rebooting the cluster, existing Labs are out of sync #193

blues-man opened this issue Feb 19, 2021 · 2 comments
Labels
bug

Comments

@blues-man
Copy link
Contributor

blues-man commented Feb 19, 2021 •
edited

It looks we have some problems with Homeroom when cluster is stopped from RHPDS and restarted, existing labs are not getting right image hash and deployments fail.

From homeroom's log:

2021-01-26 09:58:16+00:00 [Warning] Failed to pull image "quay.io/openshiftlabs/lab-getting-started@sha256:f621a8faad2ba97611759c68d1384a87ef1ecb6690eb7776b87497424016f27e": rpc error: code = Unknown desc = Error reading manifest sha256:f621a8faad2ba97611759c68d1384a87ef1ecb6690eb7776b87497424016f27e in quay.io/openshiftlabs/lab-getting-started: manifest unknown: manifest unknown

The same type of error appears for the .NET, Java and Python workshops too.
@blues-man blues-man added the bug label Feb 19, 2021
@blues-man
Copy link
Contributor Author

Possible solutions/mitigations:

  • use imagePullPolicy: IfNotPresent in spawner Pods
  • use image tag versioning per release on Quay

@blues-man
Copy link
Contributor Author

Apparently fixed by removing ocp-ops-view from AgnosticV

@blues-man blues-man mentioned this issue May 14, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blues-man