Issue while deploying Supervisor namespace in Invoke-DriDeployment

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

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

Error while Deploying a Supervisor Namespace for Developer Ready Infrastructure for VMware Cloud Foundation

Error or Debug Output

Error at Script Line 9030
Relevant Command: $StatusMsg = Add-Namespace -Server $sddcManagerFqdn -user $jsonInput.sddcManagerUser -pass $jsonInput.sddcManagerPass -domain $jsonInput.tanzuSddcDomainName -Cluster $jsonInput.supervisorClusterName -Namespace $jsonInput.supervisorNamespaceName -StoragePolicy $jsonInput.storagePolicyName -WarningAction SilentlyContinue -ErrorAction SilentlyContinue -WarningVariable WarnMsg -ErrorVariable ErrorMsg
Error Message: Cannot validate argument on parameter 'server'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.

Expected Behavior

It should work without any issues

Actual Behavior

In server input -server $jsonInput.sddcManagerFqdn should be updated instead of -Server $sddcManagerFqdn

Steps to Reproduce

Run Invoke-driDeployment

Log Fragments and Files

No response

Screenshots

No response

References

No response

[Ashwini-Ravi]

In server input -server $jsonInput.sddcManagerFqdn should be updated instead of -Server $sddcManagerFqdn

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