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.

Sign up for GitHub

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

Jump to bottom

Cluster reports to be in error state / operators are running in degraded state #741

Closed
gbraad opened this issue Oct 18, 2019 · 1 comment · Fixed by #744
Closed

Cluster reports to be in error state / operators are running in degraded state #741

gbraad opened this issue Oct 18, 2019 · 1 comment · Fixed by #744
Assignees
@gbraad
Labels
kind/task Workable task priority/critical size/S
Projects
Sprint 174

Comments

@gbraad
Copy link
Contributor

gbraad commented Oct 18, 2019

Due to recent changes to OpenShift 4.2, the "Cluster Health" will be reported on the Dashboard / console. And looks as follows:

image

and reads: "Red Hat OpenShift Container Platform is in an error state". This message is incorrectly reported for CRC usage. We purposely disable the monitoring and machine-config operators to preserve resources, however OpenShift itself will therefore conclude the cluster is in a degraded or unhealthy state.

Although we have added documentation around this, a user, newcomer or familiar to CRC, might believe the server is unusable. It is therefore adviced to add a message to the end of the crc start output.
@gbraad gbraad self-assigned this Oct 18, 2019
@gbraad gbraad added this to In progress in Sprint 174 Oct 18, 2019
@gbraad gbraad changed the title Cluster reports to be in error state / operators a running in degraded state Cluster reports to be in error state / operators are running in degraded state Oct 18, 2019
gbraad added a commit to gbraad-redhat/crc that referenced this issue Oct 18, 2019
@gbraad
Issue crc-org#741 add message about degraded state
c737366
@gbraad gbraad mentioned this issue Oct 18, 2019
Merged
gbraad added a commit to gbraad-redhat/crc that referenced this issue Oct 19, 2019
@gbraad
Issue crc-org#741 add message about degraded state
3a00871
gbraad added a commit to gbraad-redhat/crc that referenced this issue Oct 19, 2019
@gbraad
Issue crc-org#741 add message about degraded state
88118f0
praveenkumar pushed a commit that referenced this issue Oct 19, 2019
@gbraad @praveenkumar
Issue #741 add message about degraded state
4f3f19d
praveenkumar pushed a commit that referenced this issue Oct 19, 2019
@gbraad @praveenkumar
Issue #741 add message about degraded state
e07b0f3
gbraad added a commit that referenced this issue Oct 21, 2019
@gbraad
Issue #741 past tense needs to be used; 'disabled' (typo)
12384bb
praveenkumar pushed a commit that referenced this issue Oct 21, 2019
@gbraad @praveenkumar
Issue #741 past tense needs to be used; 'disabled' (typo)
42991df
@gbraad gbraad moved this from In progress to Done in Sprint 174 Nov 6, 2019
@bingws
Copy link

bingws commented Jul 6, 2020

So, how add a message to the end of the crc start output?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gbraad gbraad

Labels
kind/task Workable task priority/critical size/S
Projects
No open projects
Sprint 174
  
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue #741 add message about degraded state gbraad-redhat/crc
2 participants
@gbraad @bingws