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

Implement status command #68

Closed
gbraad opened this issue Apr 18, 2019 · 2 comments
Closed

Implement status command #68

gbraad opened this issue Apr 18, 2019 · 2 comments

Comments

@gbraad
Copy link
Contributor

gbraad commented Apr 18, 2019

No description provided.

@gbraad gbraad mentioned this issue Apr 18, 2019
5 tasks
@gbraad gbraad added this to To do in Sprint 166 via automation Apr 30, 2019
@gbraad gbraad added size/M and removed size/S labels May 15, 2019
@anjannath anjannath added this to To do in Sprint 167 via automation May 17, 2019
@anjannath anjannath removed this from To do in Sprint 166 May 17, 2019
@anjannath
Copy link
Member

What are the things that should be checked to get the status?
We could check if

  • All the cluster operators have reached their expected state.
  • Web-console pods are in running state.

will these be sufficient to infer that the cluster is running or more parameters needs to be checked?

@gbraad gbraad added this to To do in Sprint 168 Jun 17, 2019
@gbraad gbraad moved this from To do to In progress in Sprint 168 Jun 18, 2019
anjannath added a commit to anjannath/crc that referenced this issue Jun 21, 2019
For getting the status, we first check if the vm is running
after that checks if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jun 21, 2019
For getting the status, we first check if the vm is running
after that checks if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 9, 2019
For getting the status, we first check if the vm is running
after that checks if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 15, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 15, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 16, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 17, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running
anjannath added a commit to anjannath/crc that referenced this issue Jul 17, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running, additional information like
disk usage and cache size also shown as part of the output.
anjannath added a commit to anjannath/crc that referenced this issue Jul 19, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running, additional information like
disk usage and cache size also shown as part of the output.
praveenkumar pushed a commit that referenced this issue Jul 22, 2019
For getting the status, we first check if the vm is running
after that we check if all the required clusteroperators are
available, if both this conditions are met then we show
the openshift status as running, additional information like
disk usage and cache size also shown as part of the output.
@anjannath
Copy link
Member

Closed via #256

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Sprint 167
  
To do
Sprint 168
  
In progress
Development

No branches or pull requests

2 participants