Bug: Facing issue with Get-WMNamespace during Invoke-DRI deployment

[Ashwini-Ravi]

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

5.1

Module Version

2.10.0.1022

PowerShell Version

7.3.6

PowerCLI Version

13.1.0.21624340

PowerVCF Version

2.4.1.1000

Guest Operating System

windows server 2019

Environment Details

No response

Description

Issue: Facing issue during Invoke-Dri Deployment

After adding namespace the Get-WMNamespace is not able to get the details immediately. but after that if we retry the workflow Invoke-DRI Deployment it goes through fine.

Error or Debug Output

Function: Invoke-DRI deployment
Error 1:
[04-23-2024_05:34:37] [INFO] Creating Namespace (sfo-w01-ns01) in Supervisor Cluster (sfo-w01-cl01) in vCenter Server (sfo-w01-vc01.sfo.rainpole.io): SUCCESSFUL
[04-23-2024_05:34:37] [ERROR] 4/23/2024 05:34:33 Get-WMNamespace WMNamespace with name 'sfo-w01-ns01' was not found using the specified filter(s).

Error2:

[04-23-2024_05:45:33] [INFO] Creating Namespace (sfo-w01-tkc01) in Supervisor Cluster (sfo-w01-cl01) in vCenter Server (sfo-w01-vc01.sfo.rainpole.io): SUCCESSFUL
[04-23-2024_05:45:33] [ERROR] 4/23/2024 05:45:29 Get-WMNamespace WMNamespace with name 'sfo-w01-tkc01' was not found using the specified filter(s).

Expected Behavior

There should not be any errors during Invoke-DRI deployement

Actual Behavior

Facing issue while getting namespace immediately after namespace creation.

Steps to Reproduce

Run Invoke-DRI deployment.

Log Fragments and Files

No response

Screenshots

No response

References

No response

[GaryJBlake]

Not an issue with the code in PowerValidatedSolutions

Issue related to multiple versions of the PowerValidatedSolutions module installed on the system and the Add-Namespace function was being called from a previous version.

Fixed issue by removing all older versions of PowerValidatedSolutions using the following syntax:

Uninstall-Module -Name PowerValidatedSolutions -RequiredVersion 2.10.0.1017 -Force

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