#7207 Rawhide composes are breaking due to missing pyanaconda?
Closed: Upstream Opened by ferdnyc.

Hopefully this is the right place to report this: I noticed (while watching for a dependency to hit rawhide, so I could build against it) that the latest-Fedora-Rawhide tree was still on 2018-08-27, with composes since having failed.

That happens, of course, but the reason for the failure seemed odd: Fairly early in the process,lorax is blowing up when it fails to find pyanaconda.

See buildinstall-Everything-x86_64.log for the most recent attempt:

COMMAND: koji --profile=compose_koji runroot --use-shell --task-id --channel-override=compose --package=lorax --mount=/mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1 f30-build x86_64 'rm -f /var/lib/rpm/__db*; rm -rf /var/cache/yum/*; set -x; rm -rf /mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/buildinstall/Everything && lorax --product=Fedora --version=Rawhide --release=Rawhide --source=file:///mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/repo --source=http://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/comps_repo_Everything --variant=Everything --noupgrade --buildarch=x86_64 --volid=Fedora-E-dvd-x86_64-rawh --logfile=/mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/logs/x86_64/buildinstall-Everything-logs/lorax.log /mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/buildinstall/Everything && chmod -R a+r /mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/buildinstall/Everything'
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
29375394
+ rm -rf /mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/buildinstall/Everything
+ lorax --product=Fedora --version=Rawhide --release=Rawhide --source=file:///mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/repo --source=http://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/comps_repo_Everything --variant=Everything --noupgrade --buildarch=x86_64 --volid=Fedora-E-dvd-x86_64-rawh --logfile=/mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/logs/x86_64/buildinstall-Everything-logs/lorax.log /mnt/koji/compose/rawhide/Fedora-Rawhide-20180830.n.1/work/x86_64/buildinstall/Everything
/usr/lib64/python3.7/site-packages/markupsafe/__init__.py:13: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import Mapping
Traceback (most recent call last):
  File "/usr/sbin/lorax", line 38, in <module>
    from pylorax.simpleconfig import SimpleConfigFile
  File "/usr/lib/python3.7/site-packages/pylorax/simpleconfig.py", line 24, in <module>
    from pyanaconda.core.util import upperASCII
ModuleNotFoundError: No module named 'pyanaconda'

Actually you will want to watch:

https://pagure.io/dusty/failed-composes/issues

issues are auto filed there for compose failures.

For this one:

https://pagure.io/dusty/failed-composes/issue/716

See discussion there. :)

Thanks for noticing and tracking this down!

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

Great, thanks!

Actually you will want to watch:
https://pagure.io/dusty/failed-composes/issues
issues are auto filed there for compose failures.

yep. i'd like to get that moved over into releng org, but for now that's where it is. @kevin, where should I open a ticket? maybe we can get someone like @mkonecny to move it over

Metadata