Description of problem: When I run foreman-installer --enable-foreman-plugin-openscap it automatically adds upstream isimluk-openscap repo. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. foreman-installer --enable-foreman-plugin-openscap 2. ls /etc/yum.repos.d/isimluk-openscap.repo Actual results: File is present Expected results: File is not present Additional info: Easy workaround is to call foreman-installer --enable-foreman-plugin-openscap --foreman-plugin-openscap-configure-openscap-repo false
Created redmine issue http://projects.theforeman.org/issues/14520 from this bug
Upstream bug assigned to mhulan
Upstream bug component is Installer
Moving to POST since upstream bug http://projects.theforeman.org/issues/14520 has been closed ------------- Marek Hulán Applied in changeset commit:puppet-foreman|361136edfec01f2cba9b1d00c927133e952c7ed9.
Failed QA. Sat 6.2.0 Snap 8.2 the repo is still being created and endabled: # foreman-installer --enable-foreman-plugin-openscap --scenario katello ... # ll | grep isimluk -rw-r--r--. 1 root root 130 Apr 19 04:58 isimluk-openscap.repo # grep openscap_repo foreman-installer/scenarios.d/katello-answers.yaml configure_openscap_repo: true Not sure whether the fix made it to the Snap
Let me work on this bug as the installer options are very confusing and I need to raise couple of bugs related to it.
VERIFIED with sat62-snap9.0 This issue is no longer seen and no such repo isimluk-openscap.repo is now created in /etc/yum.repos.d/
I verified this works as expected with GA snap 12.1, code is in place now, moving to ON_QA to double-check.
satellite-installer --enable-foreman-plugin-openscap ls /etc/yum.repos.d/ | grep isimluk The file is not present, verified with snap 13.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1500