Bug 2037760

Summary:	Verify that network fencing option for azure doesn't work and remove it from upstream/RHEL
Product:	Red Hat Enterprise Linux 8	Reporter:	Chris Feist <cfeist>
Component:	resource-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED WONTFIX	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	agk, cluster-maint, fdinitto, nwahl, sbradley
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-06 07:28:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Feist 2022-01-06 13:56:44 UTC

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.

Comment 1 Reid Wahl 2022-01-06 18:17:05 UTC

(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.

Comment 3 RHEL Program Management 2023-07-06 07:28:06 UTC

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.