-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[4.11.2]: rolling upgrade of VR results in duplicate VRs #2880
Comments
@resmo restart of network with cleanup=true triggers the rolling restart of a single isolated network, in case of errors you may end up with more than one VR for that network and restart required flag will be true for that network. The next restart will destroy any/all the older VRs. |
The problem with duplicated VRs are the result, the issue is the exception I appended to the bug description |
I can not upgrade routers after this bug, not even stopping VRs... rolling back to 4.11.1 and try to reproduce |
I am able to reproduce. This time with a already deleted router and run restartNetwork cleanup=true 😞 |
I was unable to reproduce with latest 4.11. Let me test again, look at the code around the exceptions and get back to you @resmo. It would help if we can get access to your test env or more details on your setup. /cc @PaulAngus |
I think, I am able to reproduce this issue, I even run into it in 4.11.1:
|
Thanks @resmo I'll have a look. |
@resmo I've tried your steps, but I couldn't reproduce the problem you're having, can you think of any other detail that may help reproducing it. |
Moved this to 4.11.3.0/future milestone as this with #2900 admin can opt for legacy behaviour |
@rhtyd still hitting this exception in rc3 with
😢 |
Thanks for sharing @resmo let me investigate and get back to you |
I'm still unable to reproduce, likely the case happens due to concurrency issue when the VR is stopped/started simultaneous probably by the VM power sync manager. Ping @resmo can you test the following:
|
@rhtyd Did set the |
Thanks for sharing @resmo, as @PaulAngus replied the power off issue during rolling restart has been fixed now as well. |
I'll close this issue based on confirmation from @resmo, the poweroff PR has been merged as well. Please reopen if you can reproduce this issue again in future. |
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
restartNetwork cleanup=true
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: