Description of problem:

if policy a has 17 elements dependent one on the other along with one external policy which gets resolved while the chain is being evaluated, the chain keeps thinking that the external policy is not compliant

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

2.13.3

How reproducible:

customer environment

Steps to Reproduce:

1. create a policy with one enforced element
2. create a secondary policy with 17 elements, the first of which depends on the external policy, and every following element depends on the previous one
4. ...

Actual results:

When the enforcement of the secondary policy happens just after the first element, all the following elements continue to get evaluated. This leads to a lot of evaluation where there cannot be compliance since a higher element isn't compliant.

Expected results:

When the first element in the chain of dependency is not compliant, the rest should be automatically marked as not compliant as they require the dependency to be resolved

Additional info:

The existing sample had one policy enforcing a certificate being configured and a policy enforcing a chain of configurationpolicies
The policy generator was used to generate the policy, with `orderManifests` set to true.