We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The failing tests run on RancherManager v2.7.6.
Resume of tests:
And weirdly no issue with tests on Rancher Manager HEAD version:
Here some logs when it works: https://github.com/rancher/elemental/suites/15950137856/artifacts/910657747. Here some logs when it fails (from the same test where the screenshot were made): https://github.com/rancher/elemental/suites/15959129746/artifacts/911235902.
When it fails I can see that when the 2nd node is added in the cluster the state of the 1st node is changed to Waiting for plan to be applied.
Waiting for plan to be applied
It can be easily reproduce in the CI and an environment for live debugging can be provisioned.
Here some screenshots when it fails:
The text was updated successfully, but these errors were encountered:
Fix by this PR: rancher/elemental-operator#526.
Sorry, something went wrong.
No branches or pull requests
The failing tests run on RancherManager v2.7.6.
Resume of tests:
And weirdly no issue with tests on Rancher Manager HEAD version:
Here some logs when it works: https://github.com/rancher/elemental/suites/15950137856/artifacts/910657747.
Here some logs when it fails (from the same test where the screenshot were made): https://github.com/rancher/elemental/suites/15959129746/artifacts/911235902.
When it fails I can see that when the 2nd node is added in the cluster the state of the 1st node is changed to
Waiting for plan to be applied
.It can be easily reproduce in the CI and an environment for live debugging can be provisioned.
Here some screenshots when it fails:

The text was updated successfully, but these errors were encountered: