Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionChristophe Besson
2020-09-11 10:23:28 UTC
Description of problem:
Version-Release number of selected component (if applicable):
leapp-repository-0.10.0-2.el7_8.noarch
How reproducible:
100% for the customer with an Azure VM.
I didn't succeed to reproduce this issue with a separate /var on my test VM (kVM).
Steps to Reproduce:
1. Install a fresh Azure VM with RHSM
2. Create at least a separate /var partition. On the system where the issue occurred, there was also separate /usr, /boot and /home.
3. Run the leapp upgrade and reboot.
Actual results:
~~~
[ 782.659849] localhost upgrade[660]: //lib/dracut/hooks/upgrade/50-do-upgrade.sh: line 87: /sysroot/var/log/leapp/leapp-upgrade.log: No such file or directory
[ 782.709239] localhost kernel: EXT4-fs (dm-5): re-mounted. Opts: (null)
[ 782.718412] localhost upgrade[660]: /bin/upgrade: line 19: /sysroot/var/tmp/system-upgrade.state: No such file or directory
[ 982.097939] localhost systemd[1]: upgrade.service: Main process exited, code=exited, status=1/FAILURE
~~~
Additional info:
Only the rootfs /sysroot was mounted at this step.
Workaround: adding the parameter rd.upgrade.break=leapp-upgrade, mounting the /var and also /usr and then exiting the shell to continue the upgrade process.
Hello Christophe,
Thanks for the report. Could you please elaborate on "Steps to reproduce" a little bit? "Install a fresh Azure VM with RHSM". Did you mean to create and use a specific image? Do you have such an image at hand to reproduce the issue?
Comment 3Christophe Besson
2020-09-14 14:08:42 UTC
Hello Michal,
I don't have any Azure VM or access to this hypervisor.
Yes, I mean creating a specific image, in this case with the following partition layout:
~~~
sda 8:0 0 256G 0 disk
|-sda1 8:1 0 1G 0 part /boot
|-sda2 8:2 0 63G 0 part
| |-rootvg-tmplv 253:0 0 2G 0 lvm
| |-rootvg-usrlv 253:1 0 10G 0 lvm /usr
| |-rootvg-optlv 253:2 0 25.4G 0 lvm /opt
| |-rootvg-homelv 253:3 0 25.4G 0 lvm /home
| |-rootvg-varlv 253:4 0 25.4G 0 lvm /var
| `-rootvg-rootlv 253:5 0 25.4G 0 lvm /
`-sda3 8:3 0 191G 0 part
|-rootvg-optlv 253:2 0 25.4G 0 lvm /opt
|-rootvg-homelv 253:3 0 25.4G 0 lvm /home
`-rootvg-varlv 253:4 0 25.4G 0 lvm /var
~~~
Separate /var and /usr should be enough.
I am attaching an sosreport taken after leapp upgrade, but before the reboot [private].
Comment 4Christophe Besson
2020-09-14 14:12:36 UTC
Hmm, unfortunately it's too big to be uploaded here.
I can provide a subset of it if needed.
Comment 7Christophe Besson
2020-10-01 08:27:22 UTC
It's also happening on VMware, it's not related to Azure (and I likely made a mistake with my test on kvm).
The upgrade log ends with:
2020-09-29 16:38:39.748 INFO PID: 6344 leapp.workflow: Initiating system reboot due to the restart_after_reboot flag
whereas the system has been rebooted twice