-
Notifications
You must be signed in to change notification settings - Fork 8
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
Ci for 9.3 #268
Ci for 9.3 #268
Conversation
Signed-off-by: Justin Cinkelj <[email protected]>
Signed-off-by: Justin Cinkelj <[email protected]>
Signed-off-by: Justin Cinkelj <[email protected]>
See https://github.com/ScaleComputing/HyperCoreAnsibleCollection/actions/runs/6334360083/job/17229911477#step:8:62 A guess - we tried to use SnapshotSchedule before it was fully created. Signed-off-by: Justin Cinkelj <[email protected]>
https://github.com/ScaleComputing/HyperCoreAnsibleCollection/actions/runs/6349507160
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm mixed about adding the sleeps. Would it instead be better to rely on the user (and the tests) to use ansible features like until
in their tasks in the event of request failures?
The |
ISOs were removed/recreated while some other VMs were using them https://github.com/ScaleComputing/HyperCoreAnsibleCollection/actions/runs/6347832281/job/17243445064#step:8:113 Signed-off-by: Justin Cinkelj <[email protected]>
Signed-off-by: Justin Cinkelj <[email protected]>
We were missing wait on tasktag for SnapshotSchedule create, and wait on object begin delete for SnapshotSchedule and VirtualDisk.
Other changes are just small CI speedup, and fix how CI test check if HyperCore version >= 9.2.