When vSAN File Services is enabled the workload domain shutdown attempts to shutdown the service nodes

[tenthirtyam]

Code of Conduct

• I have read and agree to the Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation

4.5

PowerShell Version

Windows PowerShell 5.1

PowerCLI Version

13.0.0

Module Version

1.1.0

PowerVCF Version

2.3.0

Guest Operating System

Windows Server 2019

Environment Details

No response

Description

When vSAN File Services is enabled on vSAN cluster, the workload domain shutdown script attempts to shutdown the vSAN file service nodes when shutdowncustomerVM flag is provided.

As the virtual machines are managed by EAM, the script should not shutdown the virtual machines.

"vSAN cluster shutdown"/"Restart cluster" process would shutdown/startup them automatically.

Error or Debug Output

See screenshot.

Expected Behavior

Allow EAM to manage the vSAN File Service nodes shutdown process.

Actual Behavior

The workload domain shutdown script attempt to shutdown the vSAN file service notes when shutdowncustomerVM flag is provided.

Steps to Reproduce

Run the workload domain shutdown script with the shutdowncustomerVM flag.

Log Fragments and Files

No response

Screenshots

References

Ref : https://vmware.slack.com/archives/C037S8SAT9A/p1668177125983159

[github-actions]

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

[github-actions]

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

[github-actions]

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

[burnsjared0415]

will pick up

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.