What is the business rationale for this exception? Is there a specific customer that needs this RFE?

This affects all updates to 17.1.4. Assert condition was wrong and CI had double failure causing us to miss this. Correct state of mysql is being blocked.

Are there any security concerns?

No.

What other functions, teams, or DFGs are impacted by this feature?

No.

What is the estimated time to have the upstream work complete and approved?

Review sent with first pass of testing. We need to recheck the CI to catch correct state this time.

What is the time and resources required to test this issue? On what date will automated tests be written and ready to run and report results in Polarion?

CI jobs are there, it's not yet fully understood how it managed to pass.

Is there potential doc impact?

No.

Are there new packages needed that are not packaged in OSP or RHEL? Does it require newer versions of existing dependencies (dependency bumps)?

No new packages or dependencies.

What is the support level?

Fully supported

How invasive is the code? From very invasive, a core change to very isolated, no risk to other components?

Minimal impact we just modify the check and the assert condition.

What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas? Without fix the updates are blocked with manual code change needed to pass. Requesting async.