VPC Offering silently changed when activating "Make redundant" when restarting the VPC.

[zidz]

problem

I have a few dual stack VPCs.
I did activate "Make redundant" when restarting the VPC, I realized that IPv6 addresses where gone from my VMs and BGP did not ask it's neighbor to create IPv6 routes. After some troubleshooting I realized that the VPC had a new VPC offering. I had to change the offering back (and the redundant setting) by altering the tables in MariaDB.

There needs to be some information (warning) that the VPC offering is changed when this function is activated, potentially removing functionality of the VPC.

versions

Cloudstack version 4.22

The steps to reproduce the bug

1. Activate "Make redundant" when restarting a VPC.

What to do about it?

No response

[DaanHoogland]

@zidz , this function is under on-going debate.
camp 1: It should not be there
camp 2: it must be there and well documented
camp 3: it must be there behind feature flags of sorts.

Did you use the UI or the API to make the VPC redundant?

[zidz]

I did use the UI to enable it.

[mathwest]

@DaanHoogland Is there perhaps an ongoing discussion you could link to? As i am Strongly of the opinion of camp 1 but would potentially be a camp 3 if i read it as By default NOT there but if you enable a flag that allows failover to different offering if no suitable offering is pre-selected, preferably the ability to "pair" redundant and non redundant offerings as the ones that can be shifted between, perhaps this would count as an camp 4?