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

Kubernetes Object Status does not display status of child steps #8219

Closed
johnsimons opened this issue Jun 23, 2023 · 2 comments · Fixed by OctopusDeploy/Calamari#1076
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@johnsimons
Copy link

johnsimons commented Jun 23, 2023

Severity

A few customers so far

Version

2023.2.0

Latest Version

None

What happened?

When a process defines child steps, only Kubernetes resources from the first child are displayed in the Kubernetes Object Status tab.

Reproduction

Create a process with kubernetes child steps.

Screenshot 2023-06-23 at 4 40 45 PM Screenshot 2023-06-23 at 4 41 39 PM

Note there are 2 configmaps defined (cm-1 and cm-2), in separate actions of the same step. The KOS tab only shows the first.

Error and Stacktrace

No response

More Information

No response

Workaround

None

@johnsimons johnsimons added the kind/bug This issue represents a verified problem we are committed to solving label Jun 23, 2023
johnsimons pushed a commit to OctopusDeploy/Calamari that referenced this issue Jun 28, 2023
johnsimons pushed a commit to OctopusDeploy/Calamari that referenced this issue Jul 3, 2023
@octoreleasebot
Copy link

Release Note: Fixed issue with Kubernetes Object Status tab not displaying status of objects in Kubernetes that were being updated from child steps

@Octobob
Copy link
Member

Octobob commented Aug 22, 2023

🎉 The fix for this issue has been released in:

Release stream Release
2023.2 2023.2.12835
2023.3 2023.3.6194
2023.4+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants