tracker for: Marking Degraded due to: machineconfig.machineconfiguration.openshift.io "rendered-..." not found

[cgwalters]

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:

• Bug 1881057: ignore the IPv6DualStack feature gate for the kubelet config #2108

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.

[yuqi-zhang]

To add more steps:

the "day 1" config should exist on the node still, in /etc/mcs-machine-config-content.json
the "day 2" config should be fetch-able via oc get mc -> oc describe mc/rendered-xxx (or `oc get mc/rendered-xxx -o json to match formats)

You can diff the two to see what caused the drift

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[yuqi-zhang]

/remove-lifecycle rotten
Still a relevant issue

[Danil-Grigorev]

@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

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

[yuqi-zhang]

/reopen
/lifecycle frozen

Probably want to keep this around until we resolve the drift in some form

[openshift-ci]

@yuqi-zhang: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

Probably want to keep this around until we resolve the drift in some form

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.