From my understanding, network fencing with the azure agent doesn't actually work (the machine must be rebooted before it is moved into a separate subnet). We need to verify that this is still the case, and if so, remove the feature from upstream and RHEL.
(In reply to Chris Feist from comment #0) > From my understanding, network fencing with the azure agent doesn't actually > work (the machine must be rebooted before it is moved into a separate > subnet). Does that imply that it doesn't work? It sounds like it requires a downtime for configuration, which is inconvenient and should be noted if so -- but it could still be usable after initial configuration. My understanding from the metadata is that this option requires adding a subnet (which may still require a reboot to take effect) but doesn't require moving from one subnet to another.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.