-
Notifications
You must be signed in to change notification settings - Fork 413
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
tracker for: Marking Degraded due to: machineconfig.machineconfiguration.openshift.io "rendered-..." not found #2114
Comments
To add more steps: the "day 1" config should exist on the node still, in You can diff the two to see what caused the drift |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
@yuqi-zhang @cgwalters We hit this issue just now while attempting day 1 configuration change with moving to external cloud providers. Have a look at this must gather for more details. https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-cloud-controller-manager-operator/66/pull-ci-openshift-cluster-cloud-controller-manager-operator-master-e2e-aws-ccm-install/1408464686357155840 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen Probably want to keep this around until we resolve the drift in some form |
@yuqi-zhang: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This almost always happens when you're providing some sort of "day 1" configuration that causes the "bootstrap" machineconfig to differ from the "in cluster" rendered configuration.
The MCO has had numerous bugs in this area in the past. Examples:
In order to debug this, we need more information about the cluster configuration - a full must gather, or at least the platform and any specific customizations you're doing.
The text was updated successfully, but these errors were encountered: