soreana opened a new issue, #8055:
URL: https://github.com/apache/cloudstack/issues/8055
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VR, VPC
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advance zone with isolated network
##### SUMMARY
<!-- Explain the problem/feature briefly -->
One of our CloudStack environments has been upgraded from `4.17.2` to
`4.18.1`, last week. After restarting VPC there, we noticed that the backup VR
stays in the starting state forever. We don't have any clue about what went
wrong yet, we checked the following but they weren't the root cause.
* Pod, host and cluster have enough capacity to start the VR.
* Backup VR hasn't been started on any host so there is zero chance of VRRP
packets being lost.
* We removed the backup VR manually, master VR works perfectly.
* VR uses the correct system vm template.
* We removed all of our custom features from Cloudstack and ran exactly the
community version but that didn't help.
**P.S**: If we create a new VPC with EXACT same config, add VMs to the VPC
and delete the old one, we can fix the issue. So the issue only happens to the
VPC that are migrated from 4.17.2 to 4.18.1
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create a VPC and attach some VMs to it.
2. Upgrade CloudStack from 4.17.2 to 4.18.1
3. Restart the VPC with clean up.
4. Master VR starts but the backup VR stays at starting state.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Both VRs run successfully.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Master VR starts but the Backup one stays in the starting state for ever.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
