logging mount assembly and bootloader install, chroot missing?

[Chris Murphy]

The program.log shows mount commands for assembly, followed by
installation itself copying files to a path prefix /mnt/sysimage, and
then bootloader setup. Isn't there a chroot happening before the
bootloader setup? It's not in the log so I'm having some difficulty
exactly replicating an installation environment while troubleshooting
this bug:

So the questions are:
Is there a chroot?
Is there a way to discover the command being used?
And if there is a chroot, is there a way to log this command in the future?


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


Thanks,

[Adam Williamson]

Post by Chris Murphy
The program.log shows mount commands for assembly, followed by
installation itself copying files to a path prefix /mnt/sysimage, and
then bootloader setup. Isn't there a chroot happening before the
bootloader setup? It's not in the log so I'm having some difficulty
exactly replicating an installation environment while troubleshooting
Is there a chroot?
Is there a way to discover the command being used?
And if there is a chroot, is there a way to log this command in the future?
https://bugzilla.redhat.com/show_bug.cgi?id=1289752

Use the source, Luke:

https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/bootloader.py

and then search for 'root='. You'll find that most of the bootloader
installation-related commands run via iutil.execWithRedirect, with root
set to iutil.getSysroot() . Of course, you can look in iutil.py to see
what these do. If you *do* look there, you'll see that indeed the
relevant functions don't *currently* log the root argument. I think a
PR to add this wouldn't be unreasonable.

[Leslie S Satenstein]

Please look at bug 1487892     Anaconda <-->Gnome

My live testing with F27 says that it is a blocker.

Thanks in advance. Regards
 Leslie
Leslie Satenstein
Montréal Québec, Canada



From: Adam Williamson <***@redhat.com>
To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-***@redhat.com>
Sent: Saturday, September 9, 2017 9:48 PM
Subject: Re: logging mount assembly and bootloader install, chroot missing?

Post by Chris Murphy
The program.log shows mount commands for assembly, followed by
installation itself copying files to a path prefix /mnt/sysimage, and
then bootloader setup. Isn't there a chroot happening before the
bootloader setup? It's not in the log so I'm having some difficulty
exactly replicating an installation environment while troubleshooting
Is there a chroot?
Is there a way to discover the command being used?
And if there is a chroot, is there a way to log this command in the future?
https://bugzilla.redhat.com/show_bug.cgi?id=1289752

Use the source, Luke:

https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/bootloader.py

and then search for 'root='. You'll find that most of the bootloader
installation-related commands run via iutil.execWithRedirect, with root
set to iutil.getSysroot() . Of course, you can look in iutil.py to see
what these do. If you *do* look there, you'll see that indeed the
relevant functions don't *currently* log the root argument. I think a
PR to add this wouldn't be unreasonable.

[j***@redhat.com]

Post by Adam Williamson

Post by Chris Murphy
The program.log shows mount commands for assembly, followed by
installation itself copying files to a path prefix /mnt/sysimage, and
then bootloader setup. Isn't there a chroot happening before the
bootloader setup? It's not in the log so I'm having some difficulty
exactly replicating an installation environment while
troubleshooting
Is there a chroot?
Is there a way to discover the command being used?
And if there is a chroot, is there a way to log this command in the future?
https://bugzilla.redhat.com/show_bug.cgi?id=1289752

https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/bootlo
ader.py
and then search for 'root='. You'll find that most of the bootloader
installation-related commands run via iutil.execWithRedirect, with root
set to iutil.getSysroot() . Of course, you can look in iutil.py to see
what these do. If you *do* look there, you'll see that indeed the
relevant functions don't *currently* log the root argument. I think a
PR to add this wouldn't be unreasonable.

I like this idea so I've created PR for that:
https://github.com/rhinstaller/anaconda/pull/1191

Jirka