Skip to content
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

VR Redundant State not accurate for Single Virtual Router #9674

Open
btzq opened this issue Sep 12, 2024 · 1 comment
Open

VR Redundant State not accurate for Single Virtual Router #9674

btzq opened this issue Sep 12, 2024 · 1 comment

Comments

@btzq
Copy link

btzq commented Sep 12, 2024

ISSUE TYPE
  • Improvement Request
COMPONENT NAME
Virtual Router
CLOUDSTACK VERSION
4.19.1.1
CONFIGURATION
OS / ENVIRONMENT
SUMMARY

In our Cloudstack, we have some networks using a mix of

  • Redundant Virtual Router
  • Single Virtual Router

As long as we have 1 Redundant Virtual Router, then the Virtual Router page (Under Infrastructure) displays the column 'Redundant State'.

When viewing the 'Redundant State', RVRs will get either the displays (Primary/Backup) -> This is correct.

However, Single VRs will always show as 'Unkown'.

This makes it very difficult to keep track. In the event the RVR really goes into an 'Unkown' state, it would be incredibly difficult to identify.

Would like to request, that if its a single VR, then display:

  • Redundant State: SingleRouter

This will avoid confusion and improve admin experience.

Screenshot 2024-09-12 at 6 23 21 PM

STEPS TO REPRODUCE
1. Create 1 VPC with Single Router
2. Create 1 VPC with Redundant Virtual Router
3. Go to 'Virtual Router' page (Under Infrastructure)
4. Observer the 'Redundant State' Field in the table. 
EXPECTED RESULTS
Display 'Redundant State' for Single Virtual Router more accurately
ACTUAL RESULTS
'Redundant State' for Single Virtual Router is always set to 'Unkown'
@btzq btzq changed the title VR Redundant State not accurate when using both Redundant VR and Single VR in different VPCs VR Redundant State not accurate for Single Virtual Router Sep 12, 2024
@DaanHoogland DaanHoogland added this to the 4.21.0.0 milestone Sep 16, 2024
@weizhouapache
Copy link
Member

it could be simple UI change, the domainrouterresponse already has the following values

image

@DaanHoogland DaanHoogland modified the milestones: 4.21.0.0, 4.20.1.0 Sep 20, 2024
@weizhouapache weizhouapache self-assigned this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants