You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The satellite6_group_prefix satellite source vars should replace the default foreman_ prefix with a custom one when creating host groups. This prefix is not being applied to all groups. Namely, it is missing from the groups we create here:
Ansible version: 2.9+ (needed to enable use of inv. plugins)
Operating System: any
Web Browser: any
STEPS TO REPRODUCE
Create a satellite inventory
In inv. source section, set satellite6_group_prefix: newprefix_
Confirm not all groups have new prefix.
EXPECTED RESULTS
All groups use new prefix.
ACTUAL RESULTS
ADDITIONAL INFORMATION
This section, mentioned in the description, is a part of awx's 'compatibility layer' that bridges the differences between foreman's script and plugin. We need to update this section so that it takes the custom prefix into consideration.
The text was updated successfully, but these errors were encountered:
Tested this out manually and it works. Going to work on getting us some regression coverage here, this should be easy to do. Closing as verified will mention issue when I put up PR for tests
ISSUE TYPE
SUMMARY
The
satellite6_group_prefix
satellite source vars should replace the defaultforeman_
prefix with a custom one when creating host groups. This prefix is not being applied to all groups. Namely, it is missing from the groups we create here:https://github.com/ansible/awx/blob/devel/awx/main/models/inventory.py#L2605-L2622
ENVIRONMENT
STEPS TO REPRODUCE
satellite6_group_prefix: newprefix_
EXPECTED RESULTS
All groups use new prefix.
ACTUAL RESULTS
ADDITIONAL INFORMATION
This section, mentioned in the description, is a part of awx's 'compatibility layer' that bridges the differences between foreman's script and plugin. We need to update this section so that it takes the custom prefix into consideration.
The text was updated successfully, but these errors were encountered: