Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1. Proposed title of this feature request
In Satellite, The compute resource\profile configuration for VMware should have additional options to enable\disable secureboot when a VM is expected to be created using the same.
2. What is the nature and description of the request?
We already have a BZ filed to provide full support on SecureBoot :
1791608 ? [RFE] Satellite should provide a feature to provision systems with UEFI Secure Boot enabled
https://bugzilla.redhat.com/show_bug.cgi?id=1791608
Now, The users can make use of VMware compute resource and profile to deploy a EFI based VM in vCenter and build it but there is no way to enable SecureBoot during the creation of the VM. To do so, The user needs to power off the VM manually, Go inside VMware , enable the SecureBoot and then power it up again but that is breaking the entire automated-deployment.
So the additional request here is, While creating a VM, if someone select Automatic or EFI as the firmware, then there should be an additional sub-option displayed to allow enabling SecureBoot or a 4th option should be there as the choice of Firmware i.e. "EFI-Secure" to serve the same purpose.
3. Why does the customer need this? (List the business requirements here)
* The customer has the requirement from his legal department to provision new hardware and VMware systems with UEFI Secure Boot enabled.
* CIS conform deployment is not possible because there is no Secure-Boot-EFI deployment option, although the VMWare API offers this option ("firmware": "efi-secure")
4. How would the customer like to achieve this? (List the functional requirements here)
* Same as the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1791608
* And then to be able to deploy a fully-functional Efi-Secureboot enabled VM from Satellite, without needing to access vCenter manually and with both Boot Disk based and Network Based deployments.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Same as the steps in 4 i.e.
* Have a satellite build and configured to perform PXE based system deployments.
* Create a VMware compute Resource and compute profile.
* Create a VM using VMware compute Resource and compute profile, to perform an unattended UEFI-SecureBoot Enabled VM deployment in the vCenter.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Related/Parent BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1791608
7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 6.11.z or as soon as feasible
8. Is the sales team involved in this request and do they have any additional input?
Not exactly sales but Red Hat Consulting is involved on the support case and they agree to have this feature in the satellite as soon as possible
9. List any affected packages or components.
foreman
tfm-rubygem-fog-vsphere/rubygem-fog-vsphere
10. Would the customer be able to assist in testing this functionality if implemented?
Yes, They are eager to test it out once made available
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.