Description of problem: When debugging installer problems related to storage, it is very useful to have lsblk output as part of the default list of log files. As an example BZ#876789. Please at it to the list of automatically generated list of log files
+1. Presumably the anaconda logs already have that information, but it is in a format that only anaconda developers can read ...
lsblk has a lot of options ... It would be useful to have the file system types and UUIDs, but this does not give the device sizes: $ lsblk -f This gives both in a wide table: $ lsblk -mf Maybe it would be better to have the sizes in bytes: $ lsblk -mbf And since the installer adds and deletes devices, it would be useful to have an lsblk report before installation and after installation ...
python-meh would first need a way to attach program output, I believe.
(In reply to comment #3) > python-meh would first need a way to attach program output, I believe. Well, I've already been thinking about some {item_name: callback, } dictionary, that would be passed to python-meh during the configuration phase and during exception+data dump these callbacks would be called and their return value (a string) would be appended to the main file (e.g. anaconda-tb-XXXXXX) and/or possibly written out to a separate file.
Patches for python-meh and anaconda posted to anaconda-patches. I've tested those changes and the result can be seen in bug #901462 and its attachment 'lsblk_output'.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.