Plugins » Katello

Description of problem:

When a host is first registered with multiple content view environments, all CVECF records get priority: 0. The content_view_environments= setter calls reprioritize_for_content_facet
immediately after super, but for a new (unsaved) content facet, the CVECF join records only exist in memory — not in the database. Since reprioritize_for_content_facet uses find_by (a
database query), it finds nothing and sets no priorities. When content_facet.save! runs later in populate_content_facet, all CVECFs are persisted with the default priority of 0.

Fix: Call reprioritize_for_content_facet again in populate_content_facet after content_facet.save! when the content facet was a new record.

How reproducible:

100%

Is this issue a regression from an earlier version:

no? but not sure how we missed it

Steps to Reproduce:

Create an AK that assigns multiple CVEnvs

register a host

look at myhost.content_view_environment_content_facets

Actual behavior:
All CVECFs have a priority of 0

CVEnvs are displayed in a random order in Web UI

subscription-manager environments --list-enabled shows correct order.

Expected behavior:
Priority should be unique (0, 1, etc)

CVEnvs are displayed in Web UI in the same order as subscription-manager environments --list-enabled