[WIP] [release-4.17] OCPBUGS-61190: MCO report "failed to list *v1alpha1.MachineOSConfig" when enable TechPreview after upgrading from 4.16 to 4.17 with one mcp paused

[dkhater-redhat]

- What I did
Removed optr.moscListerSynced from the cacheSynced list to prevent the operator from blocking startup when the MachineOSConfig CRD doesn't exist yet. The MOSC informer still runs in the background and will sync once CVO installs the CRD.
- How to verify it

1. Upgrade a cluster from 4.16 to 4.17 with one MCP paused
2. After upgrade completes, enable TechPreview feature set
3. Verify machine-config-operator pod doesn't get stuck with "failed to list *v1alpha1.MachineOSConfig" errors
4. Verify nodes remain Ready and don't enter NotReady state
5. Check logs show MOSC informer starts but doesn't block operator startup
6. Once CVO installs the MachineOSConfig CRD, verify the informer successfully syncs
   - Description for the changelog

[openshift-ci-robot]

@dkhater-redhat: This pull request references Jira Issue OCPBUGS-61190, which is invalid:

• expected the bug to target the "4.17.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-61190 to depend on a bug targeting a version in 4.18.0, 4.18.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

- What I did
Removed optr.moscListerSynced from the cacheSynced list to prevent the operator from blocking startup when the MachineOSConfig CRD doesn't exist yet. The MOSC informer still runs in the background and will sync once CVO installs the CRD.
- How to verify it

1. Upgrade a cluster from 4.16 to 4.17 with one MCP paused
2. After upgrade completes, enable TechPreview feature set
3. Verify machine-config-operator pod doesn't get stuck with "failed to list *v1alpha1.MachineOSConfig" errors
4. Verify nodes remain Ready and don't enter NotReady state
5. Check logs show MOSC informer starts but doesn't block operator startup
6. Once CVO installs the MachineOSConfig CRD, verify the informer successfully syncs
   - Description for the changelog

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 openshift-eng/jira-lifecycle-plugin repository.

[umohnani8]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkhater-redhat, umohnani8

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dkhater-redhat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@dkhater-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.