Closed mildas closed 3 years ago
That's really strange. If the profile does not select the rule it should exclude these packages from the installation.
One exaggerated potential cause can be that you selected the STIG profile first, then packages are added to the exclude list and then selected STIG GUI profile and the list of excluded packages is not restored to the initial state.
@ggbecker good point! I've started new installation and selected STIG with GUI first and only these conflicts appear:
Problem: package libvirt-daemon-driver-storage-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires libvirt-daemon-driver-storage-core = 6.0.0-34.module+el8.4.0+9758+5c420eed, but none of the providers can be installed
- package libvirt-daemon-kvm-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires libvirt-daemon-driver-storage = 6.0.0-34.module+el8.4.0+9758+5c420eed, but none of the providers can be installed
- package libvirt-daemon-driver-storage-core-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires nfs-utils, but none of the providers can be installed
- package gnome-boxes-3.36.5-8.el8.x86_64 requires libvirt-daemon-kvm, but none of the providers can be installed
- package nfs-utils-1:2.3.3-41.el8.x86_64 requires gssproxy >= 0.7.0-3, but none of the providers can be installed
- conflicting requests
- package gssproxy-0.8.0-19.el8.x86_64 is filtered out by exclude filtering
Then I have selected STIG (the one without GUI), after that I've selected STIG with GUI again and xorg-x11-*
conflicts are there.
@ggbecker good point! I've started new installation and selected STIG with GUI first and only these conflicts appear:
Problem: package libvirt-daemon-driver-storage-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires libvirt-daemon-driver-storage-core = 6.0.0-34.module+el8.4.0+9758+5c420eed, but none of the providers can be installed - package libvirt-daemon-kvm-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires libvirt-daemon-driver-storage = 6.0.0-34.module+el8.4.0+9758+5c420eed, but none of the providers can be installed - package libvirt-daemon-driver-storage-core-6.0.0-34.module+el8.4.0+9758+5c420eed.x86_64 requires nfs-utils, but none of the providers can be installed - package gnome-boxes-3.36.5-8.el8.x86_64 requires libvirt-daemon-kvm, but none of the providers can be installed - package nfs-utils-1:2.3.3-41.el8.x86_64 requires gssproxy >= 0.7.0-3, but none of the providers can be installed - conflicting requests - package gssproxy-0.8.0-19.el8.x86_64 is filtered out by exclude filtering
Then I have selected STIG (the one without GUI), after that I've selected STIG with GUI again and
xorg-x11-*
conflicts are there.
So, there's definitely a bug in the oscap-anaconda-addon where it doesn't reset the packages list to its initial state when switching between profiles in the profile selection screen.
Regarding gssproxy, I remember seeing something related to nfs-utils and that is part of some specific group of packages. Are you installing this machine using beaker? otherwise we may have to remove this rule from the profile.
Regarding gssproxy, I remember seeing something related to nfs-utils and that is part of some specific group of packages.
About nfs-utils, I found this - https://github.com/OpenSCAP/oscap-anaconda-addon/pull/121 - but this should be handled within the "Security Policy". However, the gssproxy conflict shows as an error in the "Package Selection".
Are you installing this machine using beaker? otherwise we may have to remove this rule from the profile.
Nope, I'm installing it on my VM. Btw, I've used RHEL-8.4.0-20210216 compose
Regarding gssproxy, I remember seeing something related to nfs-utils and that is part of some specific group of packages.
About nfs-utils, I found this - OpenSCAP/oscap-anaconda-addon#121 - but this should be handled within the "Security Policy". However, the gssproxy conflict shows as an error in the "Package Selection".
I guess the fact that nfs-utils
will be removed due to gssproxy
is only established later down the road when it's removing the packages. During the Security Policy
page it only knows that gssproxy
package will be removed. We probably need to remove this rule from the stig_gui
profile.
Description of problem:
I'm not able to install RHEL 8.4 with Server with GUI package selection and with the STIG security policy - "DISA STIG with GUI for Red Hat Enterprise Linux 8".
I have built rhel8 datastream and inserted it to the installation via network (Security Policy -> Change content)
SCAP Security Guide Version:
c43f689153c
Operating System Version:
RHEL 8.4
Steps to Reproduce:
Actual Results:
Not possible to begin the installation because of software selection error:
Error checking software selection
Expected Results:
Successful installation
Additional Information/Debugging Steps:
Most of the conflicts are about
xorg-x11-*
even though it is being unselected in thestig_gui.profile
. However,gssproxy
package conflict seems valid to me because the profile contains thepackage_gssproxy_removed
rule.Software selection details: