Supported architectures and kickstart scenarios in Satellite 6
Environment
- Red Hat Satellite 6
Issue
Red Hat Satellite 6 provides flexibility when it comes to provisioning, however Red Hat provides documentation and support for selected provisioning workflows. This article describes level of support for provisioning with Red Hat Satellite 6.
Resolution
The following table describes the supported Kickstart workflows for a specific Satellite 6 version. Dash (-) characters indicate that the workflow is either unavailable, not implemented, or unsupported. TP stands for Technology Preview, and the feature can be removed from any future version of the product. Bold means it is supported and tested, italic means it is supported. See remarks below for more information.
Kickstart scenarios are tested and supported over the HTTP protocol. Other protocols, such as HTTPS or NFS, are known to work, but are untested and undocumented, and provisioning templates have no options. This also applies to UEFI HTTPS boot scenarios, when only the bootloader is downloaded over HTTPS.
This article does not cover image-based provisioning for virtualization or cloud compute resources. These workflows are fully supported as long as Satellite provides options to set the source image or snapshot, and either cloud-init is installed on the image or Satellite has DHCP or DNS control to execute the finish script over SSH and customize the instance.
Satellite 6 is based on the open-source project Content from theforeman.org is not included.Foreman, which is known to provision and manage many operating systems, including CentOS, Fedora, Debian, OpenSUSE, Solaris, and FreeBSD. This, however, is undocumented and not supported by Red Hat's support channels.
Satellite 6.8+ has been tested and is supported with vSphere 7.0 UC1
| x86_64 | PPC64 | ARM64 | S390x | RHEV | libvirt | VMWare ESX(i) | Hyper-V | |
|---|---|---|---|---|---|---|---|---|
| Netboot PXE (BIOS) 1 | 6.0+ | - | - | - | 6.0+ | 6.0+ | 6.0+ | 6.0+ |
| Netboot PXE (UEFI) 2 | 6.3+ | - | - | - | 6.3+ | 6.3+ | 6.3+ | 6.3+ |
| Netboot BOOTP 3 | - | TP | - | - | - | - | - | - |
| HTTP Boot (UEFI) IPv4 4 | 6.7+ | - | - | - | 6.7+ | 6.8+ | 6.7+ | 6.7+ |
| HTTP Boot (UEFI) IPv6 4 | 6.8+ | - | - | - | 6.8+ | 6.8+ | 6.8+ | 6.8+ |
| Netboot iPXE (BIOS) 5 | - | - | - | - | - | - | - | - |
| Netboot iPXE (UEFI) 6 | - | - | - | - | - | - | - | - |
| Discovery PXE (BIOS) 7 | 6.0+ | - | - | - | 6.0+ | 6.0+ | 6.0+ | 6.0+ |
| Discovery PXE (UEFI) 8 | 6.3+ | - | - | - | 6.3+ | 6.3+ | 6.3+ | 6.3+ |
| Bootdisk Subnet Disk (BIOS/EFI) | 6.0+ | - | - | - | 6.0+ | 6.0+ | 6.0+ | |
| Bootdisk Full Host Disk (BIOS/EFI) | 6.0+ | - | - | - | 6.0+ | 6.0+ | 6.0+ | 6.0+ |
| Secure Boot 9 | 6.17+ | - | - | - | - | 6.17+ | 6.17+ | - |
| VLAN 10 | - | - | - | - | - | - | - | - |
| IPv6 11 | - | - | - | - | - | - | - | - |
| Bond/Team 12 | 6.16+ | - | - | - | - | 6.16+ | 6.16+ | 6.16+ |
| NPAR 13 | - | - | - | - | - | - | - | - |
| SR-IOV 14 | - | - | - | - | - | - | - | - |
Remarks
PXELinux network boot, supported RHEL node versions are 7, 8, 9, and 10. Hyper-V 1st gen VMs are no longer supported in RHEL8, 2nd gen VM (UEFI) must be used.
2: PXEGrub2 network boot, supported RHEL node versions are 7, 8, 9, and 10.
[3]: The BOOTP network boot protocol is currently unsupported. A hook plug-ins workaround is reported to work.
4: HTTP UEFI Boot feature is done via Grub2 and fully supported on IPv4 with or without managed DHCP. It is the only supported workflow for IPv6 provisioning networks with limitations: DHCP must be unmanaged. There are known issues on some hardware with grub2 from RHEL7, with Satellite 7.0 upgrade the Capsule to EL8 or download and extract grubx64.efi from CentOS 9 Stream This content is not included.as a workaround
5: Chainbooting iPXE from PXELinux only with Content from ipxe.org is not included.limited hardware support, UEFI was reported to work however this is untested and unsupported.
6: Chainbooting iPXE from PXEGrub2 in UEFI or via HTTP UEFI Boot was reported to work however this is untested and unsupported.
7: Discovery PXE workflow, supported RHEL node versions 7, 8, and 9, both in BIOS mode.
8: Discovery PXE workflow, supported RHEL node versions: 7, 8, and 9, both in UEFI mode.
9: UEFI Secure Boot is tested and supported for the x84_64 architecture on RHEL 7 and newer. Network boot provisioning only. Discovery and boot disk provisioning are not implemented.
10: Tagged VLAN is not implemented yet for any workflow, including discovery. It's known to work, Satellite 6.8+ ships with VLAN-ready kickstart/PXE templates.
11: Provisioning NIC with IPv6 is not implemented, except UEFI HTTP Boot.
12: Bonded interface can be used during the installation process, such as for downloading installation content, and for the provisioned system to be used after the provisioning process is finished. This content is not included.#SAT-23034
13: NPAR provisioning NIC is untested and might fail, not supported at this point.
14: SR-IOV provisioning NIC is untested and might fail, not supported at this point.
For more information about supported Red Hat Enterprise Linux versions visit client systems page.
For more KB articles/solutions related to Red Hat Satellite 6.x Provisioning Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Provisioning related Issues
Root Cause
System or architecture is not supported by Satellite 6 for provisioning.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.