Description of problem: As per the release notes of Satellite 6.10: Generic and Host Bootdisks -------------------------- Generic and host bootdisks were deprecated in Satellite 6.9. They have been removed in this version of Satellite and are disabled in both UI and CLI. Use Full Host Bootdisk, which is based on SYSLINUX/Grub2 bootloaders and works on all RHEL certified hardware. The VMWare auto bootdisk attaching feature now also uses Full Host Disk. The same fact was true for Satellite 6.10 and for Snap 9.0 of Satellite 7.0 as far as I can tell. But for Snap 10 version of Satellite 7.0, it seems, we again have started offering the options for Downloading "Host Image" as well as "Full Host Image" for any systems being attempted to build via Satellite. The option is visible for both new and legacy view of hosts page. Version-Release number of selected component (if applicable): foreman-3.1.1.6-1.el7sat.noarch satellite-7.0.0-0.5.beta.el7sat.noarch -- foreman-3.1.1.6-1.el8sat.noarch satellite-7.0.0-0.5.beta.el8sat.noarch How reproducible: 100% Steps to Reproduce: 1. Install Snap 10 of Satellite 7.0 and set it up for system deployments 2. Create a baremetal host for PXE deployment and submit for build. 3. For the submitted Host, * In the Legacy view, Click on "Boot Disk" dropdown * In the new view, Click on kebab dropdown at the right side of the Edit button and see the Boot Disk part. Actual results: In both cases, we see an option to download both Host image and Full Host image for the said host. Not only that but also, we can actually download the Host image using the same which of 5 MB in size and an iPXE based image. Expected results: We should only have the option to download "Full Host Image" for any host from Satellite UI but not the "Host Image". Additional info: This was not reproducible in Satellite 6.10 or snap 9 of Satellite 7.0 . Hence this could very well be a regression.
Well if this isn't our wonderful setting framework: irb(main):001:0> Setting.find_by_name("bootdisk_allowed_types") => #<Setting::Bootdisk id: 56, name: "bootdisk_allowed_types", value: nil, description: "List of allowed bootdisk types, remove type to dis...", category: "Setting::Bootdisk", settings_type: "array", default: "---\n- subnet\n- full_host", created_at: "2022-02-16 11:50:42", updated_at: "2022-02-16 11:50:42", full_name: "Allowed bootdisk types", encrypted: false> irb(main):002:0> Setting.find_by_name("bootdisk_allowed_types").default => ["subnet", "full_host"] irb(main):003:0> Setting["bootdisk_allowed_types"] => ["generic", "host", "full_host", "subnet"] I tried to flush Rails cache without luck, I do not understand why this is misbehaving.
VERIFIED on sat7.11.0-17.0 only the full host boot disk is visible by default
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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498