Description of problem:

This is a customer experience improvement is inspired by the situation observed in KATA-4237 / OCPBUGS-63576. The customer tried installing OpenShift sandbox containers. Part of this installation involves the application of a MC to install the `sandboxed-containers` extension.

The customer experienced some issue where the installation seemed to be successful, as the MCP reported Update=True, but none of their nodes had the expected packages installed. The MCO should more accurately report whether an installation is successful by checking that the expected packages are installed on a node and degrading the MCP, as appropriate.

Version-Release number of selected component (if applicable):

It's a current bug (so 4.21), but it's likely in all MCO versions supporting extension installs.

How reproducible:

100%

Steps to Reproduce:

I don't have clear reproduction steps currently, but essentially the following needs to happen:

1. Apply a MC to install a supported extension
2. Internal to the MCO, the install would need to seem successful (no errors from rpm, etc.) but the package must not install on the desired node
3. The MCP will show that it is successful, but debugging into the node will show that the packages do not exist

Actual results:

If a package is not installed on a node, but from the MCO's perspective the installation seemed successful, an MCP reports Update=True.

Expected results:

If a package is not installed on a node, the MCO should degrade and report that to a user.

Additional info:

While this was inspired by the customer's experience in KATA-4237 / OCPBUGS-63576, it does NOT address the root cause of the issue.