Bug #38190
Updated by Jeremy Lenz about 2 months ago
When you remove a CV version from a lifecycle environment via web UI, you may have one or more hosts using this CV version. For these affected hosts, the wizard lets you choose a new content view and lifecycle environment to assign. If the affected host's content source does not sync the lifecycle environment, the entire removal task fails with an error like <pre> Validation failed: Host rhel9.fedora.example.com: Cannot add content view environment to content facet. The host's content source 'centos9-stream.fedora.example.com' does not sync lifecycle environment 'Library'.Validation failed: Host rhel9.fedora.example.com: Cannot add content view environment to content facet. The host's content source 'centos9-stream.fedora.example.com' does not sync lifecycle environment 'Library'.Validation failed: Host rhel9.fedora.example.com: Cannot add content view environment to content facet. The host's content source 'centos9-stream.fedora.example.com' does not sync lifecycle environment 'Library'. </pre> In other places in the UI (e.g. the Change content view environments modal in host details) we do a pre-check and don't allow you to save your selection, if it would cause this error. Ideally we should also do this for the 'remove from environment' wizard.