report rpm-ostree overrides

[cgwalters]

Today if one e.g. rpm-ostree override replace ./kernel-blah.x86_64.rpm on a node (as our hacking doc mentions), the MCO is totally unaware of this and os upgrades will preserve that override, which people may not always want.

Further, we should at least roll up somewhere into at least the pool status the fact that there are overrides.

(Also tangentially related to this topic, I think MachineConfigPool should have a status flag set if any nodes aren't RHCOS)

[runcom]

(Also tangentially related to this topic, I think MachineConfigPool should have a status flag set if any nodes aren't RHCOS)

super true this, I always oc get nodes -o wide to understand if I'm on RHCOS+RHEL

[cgwalters]

Or, another important question here: should we report or go degraded? Today if one manually overrides the booted deployment entirely via e.g. pivot or rpm-ostree rebase the MCD will go degraded.

[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-robot]

@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.