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

[gpctl] parsing error when running gpctl workspaces describe <instanceID> #9274

Closed
kylos101 opened this issue Apr 13, 2022 · 0 comments · Fixed by #10401
Closed

[gpctl] parsing error when running gpctl workspaces describe <instanceID> #9274

kylos101 opened this issue Apr 13, 2022 · 0 comments · Fixed by #10401
Labels
component: gpctl team: workspace Issue belongs to the Workspace team

Comments

@kylos101
Copy link
Contributor

Description

gpctl workspaces describe <instance-id> returns a parsing error when the instance ID is valid

How to recreate

Scenario 1: a running workspace

kyle@work:~$ gpctl workspaces describe 8ea27a2a-2b6c-4a5d-87ef-31f341a2d1cb
Owner:            4dff9b27-45c2-4bb9-83af-0ae44b46a6b5
Workspace:        4geeksacademy-reacttutor-3e5u57gscjz
Instance:         8ea27a2a-2b6c-4a5d-87ef-31f341a2d1cb
Phase:            RUNNING
Conditions:
FATA[0000] template: prettyprint:9:31: executing "prettyprint" at <.Conditions.ServiceExists>: can't evaluate field ServiceExists in type *api.WorkspaceConditions 

Scenario 2: a stopping workspace

kyle@work:~$ gpctl workspaces describe b3df4c9e-74a1-4317-a34f-42049678f95e
FATA[0000] template: prettyprint:9:31: executing "prettyprint" at <.Conditions.ServiceExists>: can't evaluate field ServiceExists in type *api.WorkspaceConditions 

Expected behavior

No parsing error

Bonus

If possible, return the phase history of the instance, so we can see how long it spent in each phase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: gpctl team: workspace Issue belongs to the Workspace team
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant