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

st2ctl status shows all the st2 components not running on K8 HA Cluster #314

Closed
Bindu-yadav8 opened this issue Jun 6, 2022 · 1 comment · Fixed by StackStorm/st2#5851
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Bindu-yadav8
Copy link

We have migrated some of the Actions & Workflows from Azure VM to Kubernetes HA Cluster via Git. All the yaml files are located in st2client component Pod.

When st2ctl reload --register-all command is executed inside the pod, all the packs, configs, actions will be registered. However, when st2ctl status command is executed, none of the components are running. Is there any way to make this components up and running?

image
image

@arm4b
Copy link
Member

arm4b commented Jun 6, 2022

st2ctl status reports pids of the currently running st2 processes in the local environment.

It's not expected for st2ctl to report the correct status in HA environment as you control the distributed services via K8s/Deployments/Pods.

I think the UX could be improved here by modifying the st2ctl code here:
https://github.com/StackStorm/st2/blob/419b25da9f45a92fb72549d9c4094e4cb7c6d729/st2common/bin/st2ctl#L265-L267
So ideally if it could just report a warning with the instructions to use docker/k8s primitives instead of showing "not running" for the local processes ids.

I'm leaving it as a good first issue if someone is willing to contribute the enhancement here.

@arm4b arm4b added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants