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.

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

Incorrect order of deployments and of current deployment before/after updates and rollbacks #22

Open
flozanorht opened this issue Jan 21, 2025 · 0 comments

Comments

@flozanorht
Copy link
Collaborator

From Yi He [email protected] (RHEL for Edge QE engineer) on slack: https://redhat-internal.slack.com/archives/C022TDCV3FH/p1737452677286359?thread_ts=1736955677.870649&cid=C022TDCV3FH

I have reviewed the documents you listed there as
@micah
’s request, and I didn't find anything wrong there, looks good to me.
However, I may found some mistakes in other chapters:
in 6.i , there are two deployments listed, I think the second one "commit-httpd-v1" should be "commit-httpd-v2"
in 8.ii , should switch "commit-httpd-v3" and "commit-httpd-v2", the reason is that the vm is rollbacked from v3 to v2 but not reboot yet, so "commit-httpd-v2" should be the first deployment here, which means in next boot it will be the first and default deployment to boot. And as the vm is currently booted with "commit-httpd-v3", so the ● should be placed before it.

Have to check if this was already addressed alongside other fixes or not. Because I tested the course carefully for switching to HOL014, I think it's unlikely that I missed those. But checking means redoing all activities, from scratch, so not quick to verify.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant