Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:

In case of upgrade strategy as "Manual", client operator required approval explicitly. Even though the ODF operator had already been approved.

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):

Fusion HCI

The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):

Provider

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):

OCP - 4.17

ODF 4.17

Does this issue impact your ability to continue to work with the product?

Is there any workaround available to the best of your knowledge?

Can this issue be reproduced? If so, please provide the hit rate

Can this issue be reproduced from the UI?

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

1. Install Data Foundation 4.16 in provider mode with Manual Strategy.

2. Upgrade OCP to 4.17.

3. Approve the installplan for odf-operator while not approving for client explicity.

The exact date and time when the issue was observed, including timezone details:

May 19, 2025, 17:00 IST (UTC+05:30)

Actual results:

Upgrade for Client operator had to approved manually.

Expected results:

Client operator should be approved when approval for odf-operator was provided.

Logs collected and log location:

Additional info: