-
Notifications
You must be signed in to change notification settings - Fork 48
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
run tests from docker image directly #556
Conversation
Fixes #539 |
Hi, @deitch Seems, we should return to the tested (pre-update) version somehow. There are several reasons for it:
But for now I cannot find how to return back to pre-update version. After update we have testing time, we can return to previous version automatically in the case of crash. But we cannot fire reboot in this time. Also, I tried to reset config to the empty one with |
So we agree we should do it, but we don't know how :-) @rvs got ideas? |
What exactly is your question @deitch ? |
Now that #558 is merged in, I rebased this on that, added the reset, and will let this run. |
This looks clean now. Put a review on @giggsoff please |
Hi, @deitch. Please add your test into workflow after lines eden/tests/workflow/eden.workflow.tests.txt Lines 122 to 123 in 00efce0
Also, you should change version inside your test. For now, version 6.1.0 is the version of builded image in Eden by default Line 51 in 00efce0
|
Sure thing. |
Done @giggsoff take another look at it |
The tests failed, I messed up the |
Looks like it passed CI. Huzzah! Back at you @giggsoff |
# Run monitoring of Info messages to obtain info with PartitionState inprogress or active and previously defined ShortVersion | ||
message 'Waiting for EVE update...' | ||
{{$test}} -out InfoContent.dinfo.SwList[0].ShortVersion 'InfoContent.dinfo.SwList[0].PartitionState:inprogress|active InfoContent.dinfo.SwList[0].ShortVersion:{{ $short_version }}' |
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.
Actually it is discussible, but, in case of subsequent revert, we should wait for active (not inprogress or active) state here. You can decrease testing time to do it faster like inside
eden controller edge-node update --config timer.test.baseimage.update=30 |
WDYT, @deitch?
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 think I am ok either way. Whatever you want, either take this as is, or tell me you prefer with just active
and I will change it
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 suggest you to change to active and modify testing time. Without it we just move our waiting onto nested script (revert_eve_image_update).
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.
Done.
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.
Thank you!
Signed-off-by: Avi Deitcher <[email protected]>
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.
Looks good, thank you!
This adds tests to update the image from an OCI image directly.
It uses version 6.1.0. I checked, and that version does, indeed, have the right labels to work.
A few open questions:
tests/update_eve_image/eden.update_eve_image.tests.txt
, and then the test intests/update_eve_image/testdata/update_eve_image_oci.txt
testdata/update_eve_image.txt
before running the next test? Should we intestdata/update_eve_image_oci.txt
? If so, how do we do it?