Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 2181920: Disable Secure Boot for UEFI Boot mode #1236

Conversation

hstastna
Copy link

@hstastna hstastna commented Apr 5, 2023

📝 Description

Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2181920

Disable secure boot when choosing "UEFI" option in the VM Details page for "Boot mode" field. Fix the yaml when choosing this option in the UI.

How to reproduce the bug:

  1. choose/create some VM with Fedora OS (or any other OS, but easier to reproduce with Fedora, because it has bootctl already installed - to easily get the status for secure boot)
  2. go to VM's Details page and check Boot mode field:
  • if there is "UEFI" already chosen, continue to the next step
  • if there is something else, choose "UEFI" in the modal and restart the VM to apply the change
  1. go to VM's console:
    click on Open web console in VM Overview tab or also you can go to VM Console tab
  2. log in to (running!) VM, open Guest login credentials up left in the page to get the credentials
    (or you also can look to the VM's Scripts tab - Cloud-init section, where you also can change the password if you are allowed to do so)
  3. after logging to the VM, check secure boot status, in the VM console:
    sudo bootctl status | grep "Secure Boot"
    => it was enabled even if it shouldn't be!

🎥 Screenshots

Choosing "UEFI" option in the VM Details page for "Boot mode" field:
uefi

Before:
Secure boot enabled, when checking the status after logging to the VM:
uefi_before
VM's yaml:
uefi_before2

After:
Secure boot disabled as expected, when checking the status after logging to the VM:
uefi_after
VM's yaml:
uefi_after2

Disable secure boot when choosing "UEFI" option in the VM Details page
for "Boot mode" field. Fix the yaml when choosing this option.

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 5, 2023

@hstastna: This pull request references Bugzilla bug 2181920, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.14.0) matches configured target release for branch (4.14.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2181920: Disable Secure Boot for UEFI Boot mode

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label Apr 5, 2023
@openshift-ci openshift-ci bot requested a review from gouyang April 5, 2023 15:19
@hstastna
Copy link
Author

hstastna commented Apr 5, 2023

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 5, 2023

@hstastna: This pull request references Bugzilla bug 2181920, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.14.0) matches configured target release for branch (4.14.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2181920: Disable Secure Boot for UEFI Boot mode

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@pcbailey
Copy link
Member

pcbailey commented Apr 5, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Apr 5, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hstastna, pcbailey

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit f07fb31 into kubevirt-ui:main Apr 5, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 5, 2023

@hstastna: All pull requests linked via external trackers have merged:

Bugzilla bug 2181920 has been moved to the MODIFIED state.

In response to this:

Bug 2181920: Disable Secure Boot for UEFI Boot mode

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 2, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 3, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 3, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 8, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 8, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 8, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
hstastna pushed a commit to hstastna/kubevirt-plugin that referenced this pull request May 8, 2023
This is a followup of kubevirt-ui#1236
introducing the change that "efi: { secureBoot: false }" was written to
VM's yaml when changing Boot mode field value to "UEFI", because that
was correct representation of "UEFI" boot mode (secure boot disabled).

In this commit, the following remaining issues are fixed:

- for existing VM:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section

- in Create VM wizard:
-- it shows "UEFI" for Boot mode field in Review and create
VirtualMachine screen for "efi: {}" in the yaml's bootloader section

- for existing template:
-- it shows "UEFI" for Boot mode field in Details for "efi: {}" in the
yaml's bootloader section
-- after changing Boot mode field to "UEFI", "efi: {}" occurs in the
yaml (this doesn't happen for existing VMs or when creating a VM)

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2181920
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix bugzilla/severity-unspecified bugzilla/valid-bug lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants