Bug 1731069
| Summary: | After reboot during system installation， the system can not find the boot option wrote into the disk [Power8] | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ping Zhang <pizhang> | ||||||||||||||||||
| Component: | grub2 | Assignee: | Bootloader engineering team <bootloader-eng-team> | ||||||||||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||||||||||
| Priority: | urgent | ||||||||||||||||||||
| Version: | 7.7 | CC: | bugproxy, didoming, fmartine, fnovak, hannsj_uhl, iranna.ankad, jkachuck, kzhang, pizhang | ||||||||||||||||||
| Target Milestone: | rc | ||||||||||||||||||||
| Target Release: | 7.7 | ||||||||||||||||||||
| Hardware: | ppc64le | ||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2020-04-14 13:48:52 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: | |||||||||||||||||||
| Embargoed: | |||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||
| Bug Blocks: | 1689150, 1689420, 1776446 | ||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
Ping Zhang
2019-07-18 09:33:43 UTC
Created attachment 1591735 [details]
successful console.log
Can you please share the /boot/grub2/grub.cfg and /boot/grub2/grubenv files for the successful and failing cases? Also, I noticed that you are using a different Petitboot version: - Petitboot (v1.4.4-91eed07) in the successful case. - Petitboot (v1.4.4-e1658ec) in the failing case. Could you please test with the same machine and Petitboot version just to make sure that the problem is not in the OPAL firmware? Since the grub.cfg and grubenv files are parsed by Petitboot and not grub2 for ppc64le PowerNV (Non-Virtualized). It still could be though that the grub tools are not generating a correct grub config file in the failing case. ------- Comment From diegodo.com 2019-08-01 16:13 EDT------- Hi, please, could you provide the files asked in the previous comment? Thanks ------- Comment From mbringm.com 2019-08-14 14:39 EDT------- RedHat: We need more information here. We do not have access to the beaker environment for replication or debugging. * Can you generate a sosreport for the platform? * Firmware versions * PowerNV or PowerVM configuration * Adapter configuration Also, there was no response to Frank's question/request regarding the 2 different versions of petitboot that were observed. ------- Comment From mbringm.com 2019-08-14 14:40 EDT------- RedHat: Since RHEL 7.7 has gone to GA, is this still an issue? Created attachment 1604322 [details]
Successful_Petitboot-v1.4.4-91eed07_grub.cfg
Created attachment 1604324 [details]
Successful-Petitboot-v1.4.4-91eed07.grub.cfg
(In reply to Javier Martinez Canillas from comment #3) > Can you please share the /boot/grub2/grub.cfg and /boot/grub2/grubenv files > for the successful and failing cases? > > Also, I noticed that you are using a different Petitboot version: > > - Petitboot (v1.4.4-91eed07) in the successful case. > - Petitboot (v1.4.4-e1658ec) in the failing case. > > Could you please test with the same machine and Petitboot version just to > make sure that the problem is not in the OPAL firmware? Since the grub.cfg > and grubenv files are parsed by Petitboot and not grub2 for ppc64le PowerNV > (Non-Virtualized). It still could be though that the grub tools are not > generating a correct grub config file in the failing case. for the successful cases, i uploaded two grub.cfg, and the grubenv is as below: cat /boot/grub2/grubenv # GRUB Environment Block saved_entry=Red Hat Enterprise Linux Server (3.10.0-1062.el7.ppc64le) 7.7 (Maipo) ##################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################### for the failed cases, I can not found the /boot directory, so that there are no grub.cfg or grubenv file. (In reply to IBM Bug Proxy from comment #5) > ------- Comment From mbringm.com 2019-08-14 14:39 EDT------- > RedHat: > We need more information here. We do not have access to the beaker > environment > for replication or debugging. > > * Can you generate a sosreport for the platform? > * Firmware versions > * PowerNV or PowerVM configuration > * Adapter configuration > > Also, there was no response to Frank's question/request regarding the 2 > different versions of petitboot > that were observed. I generate the sosreport for this two systems, but can not upload to bugzilla, I did not found some good method to share these file with you. ------- Comment From chavez.com 2019-08-16 10:45 EDT------- Hello, Please try https://testcase.software.ibm.com and login with anonymous and no password. Navigate to the /toibm/linux directory and upload the files there. Once done, please add a comment here with the name of the file(s) uploaded. (In reply to IBM Bug Proxy from comment #11) > ------- Comment From chavez.com 2019-08-16 10:45 EDT------- > Hello, > > Please try https://testcase.software.ibm.com and login with anonymous and no > password. Navigate to the /toibm/linux directory and upload the files there. > Once done, please add a comment here with the name of the file(s) uploaded. I create a tar file named RH-Bug1731069.tar which includes two sosreports of these two systems. And I think i uploaded it two the /toibm/linux directory, but i am not sure, because i can not read that directory. ------- Comment From mbringm.com 2019-08-20 11:35 EDT------- (In reply to comment #16) > (In reply to IBM Bug Proxy from comment #11) > > Hello, > > > > Please try https://testcase.software.ibm.com and login with anonymous and no > > password. Navigate to the /toibm/linux directory and upload the files there. > > Once done, please add a comment here with the name of the file(s) uploaded. > I create a tar file named RH-Bug1731069.tar which includes two sosreports of > these two systems. And I think i uploaded it two the /toibm/linux directory, > but i am not sure, because i can not read that directory. I just checked that directory, but do not see any file with the name RH-Bug1731069.tar. Did you select the file locally on your system with 'Browse' before using the 'Upload (binary)' button? (In reply to IBM Bug Proxy from comment #13) > ------- Comment From mbringm.com 2019-08-20 11:35 EDT------- > (In reply to comment #16) > > (In reply to IBM Bug Proxy from comment #11) > > > Hello, > > > > > > Please try https://testcase.software.ibm.com and login with anonymous and no > > > password. Navigate to the /toibm/linux directory and upload the files there. > > > Once done, please add a comment here with the name of the file(s) uploaded. > > I create a tar file named RH-Bug1731069.tar which includes two sosreports of > > these two systems. And I think i uploaded it two the /toibm/linux directory, > > but i am not sure, because i can not read that directory. > > I just checked that directory, but do not see any file with the name > RH-Bug1731069.tar. > Did you select the file locally on your system with 'Browse' before using > the 'Upload (binary)' button? Maybe the file is too large, I try to upload the compressed version of it, it seems successful at first, without the Error 403. Maybe you can found the file named RH-Bug1731069.zip or RH-Bug1731069.tar.gz in this directory. ------- Comment From mbringm.com 2019-08-21 10:15 EDT-------
> Maybe the file is too large, I try to upload the compressed version of it,
> it seems successful at first, without the Error 403.
> Maybe you can found the file named RH-Bug1731069.zip or RH-Bug1731069.tar.gz
> in this directory.
Don't see either file. Investigating problem.
------- Comment From chavez.com 2019-08-21 12:26 EDT------- While we figure out what is going on with testcase, if it is just sosreports you want to provide and they exceed the attachment size limit, consider using the split command, e.g. split -b 4M sosreport.tar.xz and let us know the order of the pieces and we can re-assemble them with cat part1 part2 part3 > sosreport.tar.xz Created attachment 1609811 [details] Part1 of RH-Bug1731069.tar.gz Created attachment 1609812 [details] Part2 of RH-Bug1731069.tar.gz Created attachment 1609813 [details] Part3 of RH-Bug1731069.tar.gz Created attachment 1609815 [details] Part4 of RH-Bug1731069.tar.gz ------- Comment From diegodo.com 2019-09-09 15:50 EDT------- Hi RedHat I think we should put some RHEL installer maintainer in CC of this bug. Per the previous messages, we don't have the /boot dir in the failing cases which suggests that it could be a result of a failure during the installation and possibly due some grub issue. Is it possible to have the complete log of Anaconda Installer of the failing case? Maybe we could get some hint about what is getting wrong in this step. THanks ------- Comment From diegodo.com 2019-09-23 09:28 EDT------- Hi, what are the next steps here? I think we should consider to put the installer maintainers here, so we can try to understand why we dont have the /boot dir after the installation.. Thanks (In reply to Javier Martinez Canillas from comment #3) [snip] > > - Petitboot (v1.4.4-91eed07) in the successful case. > - Petitboot (v1.4.4-e1658ec) in the failing case. > > Could you please test with the same machine and Petitboot version just to > make sure that the problem is not in the OPAL firmware? Since the grub.cfg > and grubenv files are parsed by Petitboot and not grub2 for ppc64le PowerNV > (Non-Virtualized). It still could be though that the grub tools are not > generating a correct grub config file in the failing case. There was never an answer to this question as far as I can tell. Since the bootloader is not controlled by the OS for ppc64le OPAL, it would be good to test using the same Petitboot version to make sure that the problem is not in the bootloader. By the /boot directory not found, do you mean that the directory does not exist at all or that the boot partition can't be mounted on that directory (do you have a boot partition or only a root partition with a /boot directory)? ------- Comment From mbringm.com 2019-11-18 10:56 EDT------- RedHat: Any update on this one? ------- Comment From diegodo.com 2019-11-20 14:00 EDT------- (In reply to comment #28) > (In reply to Javier Martinez Canillas from comment #3) > [snip] > > > > - Petitboot (v1.4.4-91eed07) in the successful case. > > - Petitboot (v1.4.4-e1658ec) in the failing case. > > > > Could you please test with the same machine and Petitboot version just to > > make sure that the problem is not in the OPAL firmware? Since the grub.cfg > > and grubenv files are parsed by Petitboot and not grub2 for ppc64le PowerNV > > (Non-Virtualized). It still could be though that the grub tools are not > > generating a correct grub config file in the failing case. > There was never an answer to this question as far as I can tell. Since the > bootloader is not controlled by the OS for ppc64le OPAL, it would be good to > test using the same Petitboot version to make sure that the problem is not > in the bootloader. > By the /boot directory not found, do you mean that the directory does not > exist at all or that the boot partition can't be mounted on that directory > (do you have a boot partition or only a root partition with a /boot > directory)? I'm assuming the partition can't be mounted, but it would be better to wait the answer from Ping. @Ping could you please confirm which is the scenario we do have here? Thanks! (In reply to IBM Bug Proxy from comment #25) > ------- Comment From diegodo.com 2019-11-20 14:00 EDT------- > (In reply to comment #28) > > (In reply to Javier Martinez Canillas from comment #3) > > [snip] > > > > > > - Petitboot (v1.4.4-91eed07) in the successful case. > > > - Petitboot (v1.4.4-e1658ec) in the failing case. > > > > > > Could you please test with the same machine and Petitboot version just to > > > make sure that the problem is not in the OPAL firmware? Since the grub.cfg > > > and grubenv files are parsed by Petitboot and not grub2 for ppc64le PowerNV > > > (Non-Virtualized). It still could be though that the grub tools are not > > > generating a correct grub config file in the failing case. > > There was never an answer to this question as far as I can tell. Since the > > bootloader is not controlled by the OS for ppc64le OPAL, it would be good to > > test using the same Petitboot version to make sure that the problem is not > > in the bootloader. > > By the /boot directory not found, do you mean that the directory does not > > exist at all or that the boot partition can't be mounted on that directory > > (do you have a boot partition or only a root partition with a /boot > > directory)? > > I'm assuming the partition can't be mounted, but it would be better to wait > the answer from Ping. > > @Ping could you please confirm which is the scenario we do have here? > > Thanks! When i caught this problem, I am sorry about that for the Petitboot version of these system, I do not have the time to change it. for the scenario, I only have a root partition with a /boot directory, when i encountered this problem. ------- Comment From diegodo.com 2020-01-13 13:52 EDT------- Hi Ping, is the problem still occurring? Could you please check if it works on Petitboot (v1.4.4-91eed07)? Thank you ------- Comment From mbringm.com 2020-03-10 12:21 EDT------- (In reply to comment #35) > Hi Ping, is the problem still occurring? Could you please check if it works > on Petitboot (v1.4.4-91eed07)? > Thank you Hello, Ping: Are you still observing this issue? (In reply to IBM Bug Proxy from comment #28) > ------- Comment From mbringm.com 2020-03-10 12:21 EDT------- > (In reply to comment #35) > > Hi Ping, is the problem still occurring? Could you please check if it works > > on Petitboot (v1.4.4-91eed07)? > > Thank you > > Hello, Ping: Are you still observing this issue? It did not occur recently, I think it is a good news. ------- Comment From mbringm.com 2020-04-03 10:48 EDT------- (In reply to comment #37) > (In reply to IBM Bug Proxy from comment #28) > > (In reply to comment #35) > > > Hi Ping, is the problem still occurring? Could you please check if it works > > > on Petitboot (v1.4.4-91eed07)? > > > Thank you > > Hello, Ping: Are you still observing this issue? > It did not occur recently, I think it is a good news. Great. Do you think that there is more to do? Can we close this bug then? It's also reported to grub2 but the system uses OPAL/Petiboot. ------- Comment From mbringm.com 2020-04-09 11:27 EDT------- (In reply to comment #39) > Can we close this bug then? It's also reported to grub2 but the system uses > OPAL/Petiboot. Frank: What do you think? ------- Comment From fnovak.com 2020-04-13 09:54 EDT------- Looks like this is working now.. Seems like RH doesn't have the time to go back.. I say, let's close this.. ------- Comment From mbringm.com 2020-04-13 10:34 EDT------- Closing per above comments. (In reply to IBM Bug Proxy from comment #34) > ------- Comment From mbringm.com 2020-04-13 10:34 EDT------- > Closing per above comments. Ok, I'm closing this bug then. |