Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error enabling Harbor Registry Service #369

Closed
4 tasks done
Ashwini-Ravi opened this issue Oct 4, 2023 · 3 comments · Fixed by #385
Closed
4 tasks done

Error enabling Harbor Registry Service #369

Ashwini-Ravi opened this issue Oct 4, 2023 · 3 comments · Fixed by #385
Assignees
Labels
bug Bug ci Related to CI Pipeline with PlatformTools vvs/dri Developer Ready Infrastructure
Milestone

Comments

@Ashwini-Ravi
Copy link
Contributor

Ashwini-Ravi commented Oct 4, 2023

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

PowerShell Version

7.3.6

PowerCLI Version

13.1.0.21624340

PowerVCF Version

2.3.0.1004

Guest Operating System

windows server 2019

Environment Details

No response

Description

31, 61, 12 | VI Workload Domain | vCenter with Tanzu: Enable the Registry Service on the Supervisor Cluster

Error or Debug Output

[10-04-2023_12:14:22] [...] INFO  Error at Script Line 6893  Relevant Command: $configStatus = Get-WMRegistry -cluster $cluster | Get-WMRegistryHealth  Error Message: A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
[10-04-2023_12:14:22] [...] ERROR System.Management.Automation.CmdletInvocationException: {"majorErrorCode":404,"name":"com.vmware.vapi.rest.httpNotFound","localizableMessages":[{"args":[],"defaultMessage":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}],"type":"com.vmware.vapi.std.errors.not_found","value":{"messages":[{"args":[],"default_message":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}]}}
 ---> Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
   --- End of inner exception stack trace ---
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) {"majorErrorCode":404,"name":"com.vmware.vapi.rest.httpNotFound","localizableMessages":[{"args":[],"defaultMessage":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}],"type":"com.vmware.vapi.std.errors.not_found","value":{"messages":[{"args":[],"default_message":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}]}} A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'. A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
  
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
[10-04-2023_12:14:22] [...] NOTE Finished the Process of Enabling the Harbour Regitry on the Cluster

Expected Behavior

Should work without any error message.

Actual Behavior

Shows an error message as mentioned.

Steps to Reproduce

31, 61, 12 | VI Workload Domain | vCenter with Tanzu: Enable the Registry Service on the Supervisor Cluster

Running the above option shows error mentioned.

Observed on VCF 5.1

Log Fragments and Files

No response

Screenshots

No response

References

No response

@Ashwini-Ravi Ashwini-Ravi added bug Bug needs-triage Needs Triage labels Oct 4, 2023
@github-actions github-actions bot added the pending-review Pending Review label Oct 4, 2023
@tenthirtyam
Copy link
Collaborator

@Ashwini-Ravi could you ensure the output is formatted with the markdown for readability?

@tenthirtyam tenthirtyam changed the title bug:DRI:Error while enabling the Harbour Registry Service Error enabling Harbor Registry Service Oct 4, 2023
@tenthirtyam tenthirtyam added vvs/dri Developer Ready Infrastructure and removed pending-review Pending Review labels Oct 4, 2023
@tenthirtyam tenthirtyam added this to the Backlog milestone Oct 4, 2023
@Ashwini-Ravi
Copy link
Contributor Author

Ashwini-Ravi commented Oct 4, 2023

[10-04-2023_12:14:22] [...] INFO Error at Script Line 6893 Relevant Command: $configStatus = Get-WMRegistry -cluster $cluster | Get-WMRegistryHealth Error Message: A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
[10-04-2023_12:14:22] [...] ERROR System.Management.Automation.CmdletInvocationException: {"majorErrorCode":404,"name":"com.vmware.vapi.rest.httpNotFound","localizableMessages":[{"args":[],"defaultMessage":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}],"type":"com.vmware.vapi.std.errors.not_found","value":{"messages":[{"args":[],"default_message":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}]}}
---> Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
--- End of inner exception stack trace ---
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) {"majorErrorCode":404,"name":"com.vmware.vapi.rest.httpNotFound","localizableMessages":[{"args":[],"defaultMessage":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}],"type":"com.vmware.vapi.std.errors.not_found","value":{"messages":[{"args":[],"default_message":"Not found.","id":"com.vmware.vapi.rest.httpNotFound"}]}} A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'. A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'. System.Management.Automation.CmdletInvocationException: A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
 ---> System.Management.Automation.ParameterBindingException: A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
   at System.Management.Automation.CommandProcessorBase.Complete()
   --- End of inner exception stack trace ---
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) A positional parameter cannot be found that accepts argument 'Microsoft.PowerShell.Commands.HttpResponseException: Response status code does not indicate success: 404 (Not Found).
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)'.
[10-04-2023_12:14:22] [...] NOTE Finished the Process of Enabling the Harbour Regitry on the Cluster

@tenthirtyam tenthirtyam added the ci Related to CI Pipeline with PlatformTools label Oct 4, 2023
@tenthirtyam tenthirtyam modified the milestones: Backlog, v2.7.0 Oct 4, 2023
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 18, 2023
@tenthirtyam tenthirtyam removed the needs-triage Needs Triage label Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Bug ci Related to CI Pipeline with PlatformTools vvs/dri Developer Ready Infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants