| Summary: | The /boot and /boot/efi will be put on local disk when choosing a remote disk as boot device on UEFI machine | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Qin Yuan <qiyuan> | ||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 8.1 | CC: | anaconda-maint-list, aoconnor, bugs, cshao, huzhao, jkonecny, leiwang, qiyuan, rvykydal, sbueno, weiwang, yaniwang, ycui | ||||||
| Target Milestone: | alpha | Flags: | jkonecny:
needinfo?
(sbueno) |
||||||
| Target Release: | 8.1 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-12-01 07:27:43 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 1228020 [details]
/var/log*,/tmp/*
Shouldn't this only work with ibft? I test on FC UEFI machine and iSCSI UEFI machine, they both have the same issue as described in the bug. So, I think it may not related to ibft. Radek, could this be the intended behavior? That a local disk is required? Seems like a bug, might be related to https://github.com/rhinstaller/anaconda/issues/800. I'll look into it. Can you point us to the compose we could use to reproduce the issue? From the description logs it is with anaconda 21.48.22.56-6-6 and Blivet 0.61.15.37. Also pointer to your repository with patches added to 7.2 anaconda (21.48.22.56) could be useful. Are you able to reproduce with 7.3 anaconda (21.48.22.93)? Not sure if you are using it anywhere. I'm quite sure that we are still seeing this issue in the build in comment 8. (In reply to Radek Vykydal from comment #7) > Can you point us to the compose we could use to reproduce the issue? From > the description logs it is with anaconda 21.48.22.56-6-6 and Blivet > 0.61.15.37. > Also pointer to your repository with patches added to 7.2 anaconda > (21.48.22.56) could be useful. > Are you able to reproduce with 7.3 anaconda (21.48.22.93)? Not sure if you > are using it anywhere. We forked it here: https://github.com/evol262/anaconda But primarily, this was a couple of backports for iSCSI related issues, and adding an installclass for RHV-H. This is definitely still reproducible on 7.3 this missed 7.4 (and 7.5 and 7.6). Can we have a target release for this to be fixed? 7.6.z? 7.7? missed 7.7, re-trying with 8.1 for RHV 4.4 Not tracking this for RHV 4.4 anymore After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |
Created attachment 1228019 [details] Screenshot of partitioning Description of problem: For UEFI machine having remote disks, like iSCSI or FC, choose a local disk and a remote disk to install RHVH, set the remote disk as boot device, then select "I will configure partitioning" and "click here to create them automatically", the /boot and /boot/efi will be put on the local disk, not on the remote disk. If choose "Automatically configure partitioning", the partitioning result is correct, the /boot and /boot/efi are put on the remote disk. Version-Release number of selected component (if applicable): RHVH-4.0-20161130.1-RHVH-x86_64-dvd1.iso imgbased-0.8.10-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHVH via interactive anaconda on an UEFI machine having remote disks. 2. Go to the INSTALLATION DESTINATION page. 3. Select a local disk and a remote disk. 4. Open "Full disk summary and boot loader.." at the bottom 5. Set the remote disk as boot device. 6. Choose "I will configure partitioning", and click Done. 7. Go to MANUAL PARTITIONING page, select LVM Thin Provisioning 8. Click "Click here to create them automatically" Actual results: After step8, /boot and /boot/efi are put on the local disk. Expected results: After step8, /boot and /boot/efi can be put on the remote disk which is set to be the boot device. Additional info: This issue also occurred on RHVH 4.0.5