I'm confused. Is this a bug report that OSDs flap after node reboot? If so, is it a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2167341?

Or is this a feature request to allow changing the network mode after installation? If so, the feature work is done, but we will still need QE validation. In the meantime, the best strategy is to deploy ODF in a test environment first to ensure everything works as expected. If a config doesn't work well, reinstalling a test environment shouldn't be an issue. Once there is a stable test install, then install to production.

(In reply to Blaine Gardner from comment #2)
> I'm confused. Is this a bug report that OSDs flap after node reboot? If so,
> is it a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2167341?
> 
> Or is this a feature request to allow changing the network mode after
> installation? If so, the feature work is done, but we will still need QE
> validation. In the meantime, the best strategy is to deploy ODF in a test
> environment first to ensure everything works as expected. If a config
> doesn't work well, reinstalling a test environment shouldn't be an issue.
> Once there is a stable test install, then install to production.

Yes. I was wondering if there are any way to add a new network and configuring multus 
to use old and new network for public and cluster traffic. I agree, this is more of feature request
as we have to configure network interfaces before deploying the ODF cluster. Let me convert this BZ in a RFE.

What limitation do we have from rook side to support on the fly network changes ? I assume this is more of multus 
and OVN limitations rather than rook.

I'm not sure what OVN limitations would exist. I don't believe any multus limitations should exist. It may be necessary to create a new NAD rather than modify the existing NAD, but that is not a limitation IMO. With upstream code that will be in ODF 4.13, moving from one multus configuration to another should happen automatically, but mons will need to be manually failed over. Something that will need to be tested, of course.

Moving RFEs out of 4.13

Closing since this isn't a rook issue and the transition can be completed with a reboot. If I'm missing something, please reopen.