Skip to content

[6.18.z] Fix host_conf to resolve post_configs from content_host settings#22078

Open
Gauravtalreja1 wants to merge 1 commit into
SatelliteQE:6.18.zfrom
Gauravtalreja1:fix-broker-post-config-618z
Open

[6.18.z] Fix host_conf to resolve post_configs from content_host settings#22078
Gauravtalreja1 wants to merge 1 commit into
SatelliteQE:6.18.zfrom
Gauravtalreja1:fix-broker-post-config-618z

Conversation

@Gauravtalreja1

Copy link
Copy Markdown
Member

Failed Autocherrypick of #22065
Fixes #22072

Problem Statement

Currently, host_conf() reads post_configs from request.param, which fixture_markers never populates. This means post_configs defined in conf/content_host.yaml (e.g., post_configs: [fips] for rhel7_fips) are silently ignored, the enable-fips workflow never runs for FIPS content hosts that rely on it.

Additionally, host_conf() has a dict aliasing bug (conf = params = {}) that mutates request.param as a side effect, and two fixtures (rhel_contenthost_with_repos, module_flatpak_contenthost) bypass contenthost_factory, so they would never handle post-configs even if host_conf returned them correctly.

Solution

  • Fix host_conf() to read post_configs from the version's settings dict (settings.content_host..post_configs) instead of request.param
  • Fix the dict aliasing bug by constructing conf as a new dict
  • Migrate rhel_contenthost_with_repos and module_flatpak_contenthost to use contenthost_factory so all content host fixtures consistently handle post-configs
  • Track applied post-configs on the host object via host._post_deploy_config (a set) in host_post_config(), so with host object we can check what was applied

Related Issues

Follow-up of #16981

…elliteQE#22065)

host_conf() was reading post_configs from request.param (never set by fixture_markers), instead of the version's YAML config,
so FIPS variants like rhel7_fips never ran their enable-fips post-deploy action.

Track applied post-configs on host object via _post_deploy_config attribute

Also fixes a dict aliasing issue (conf = params = {}), and migrates rhel_contenthost_with_repos and module_flatpak_contenthost to use
contenthost_factory so all content host fixtures consistently handle post_configs.

Signed-off-by: Gaurav Talreja <gtalreja@redhat.com>
(cherry picked from commit 497bf6b)
@Gauravtalreja1 Gauravtalreja1 self-assigned this Jul 7, 2026
@Gauravtalreja1 Gauravtalreja1 added No-CherryPick PR doesnt need CherryPick to previous branches Failed_AutoCherryPick Issue for failed/conflicted auto cherry pick of PRs 6.18.z Introduced in or relating directly to Satellite 6.18 labels Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.18.z Introduced in or relating directly to Satellite 6.18 Failed_AutoCherryPick Issue for failed/conflicted auto cherry pick of PRs No-CherryPick PR doesnt need CherryPick to previous branches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant