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

This is not an RFE, but a regression introduced in 17.1.4. Customers using satellite and `tags_from_label` when preparing images would face the issue.

> Are there any security concerns?

No

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

None

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

Already merged in `17.1-trunk-patches`.

> 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?

There is no automated test coverage for this issue. However it has been manually tested already and one of the customers tested by manually patching.

> Is there potential doc impact?

None

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

No dependant packages have to be bumped.

> What is the support level? Tech Preview or fully supported

Fully supported.

> How invasive is the code? From very invasive, a core change to very isolated, no risk to other components? Example: Minimal impact (only affects the puppet-cinder module).

isolated change.

> What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas?

Impacts deployment with satellite. No upgrade impact.