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.
DescriptionBruno Goncalves
2020-06-16 09:11:30 UTC
Description of problem:
For recent lorax builds the test gets stuck waiting for compose to finish
Version-Release number of selected component (if applicable):
lorax-28.14.46-1.el8
How reproducible:
100%
Steps to Reproduce:
1.run lorax dist-git test on rhle-8.3.0 compose (an scratch build using rhel-8.3.0-candidate build target should be enough)
2.
3.
Actual results:
test runs for several hours repeating:
:: [ 16:44:49 ] :: [ INFO ] :: Waiting for compose to finish ...
2020-06-02 16:44:49,074: /run/weldr/api.socket does not exist
:: [ 16:45:09 ] :: [ INFO ] :: Waiting for compose to finish ...
2020-06-02 16:45:09,154: /run/weldr/api.socket does not exist
Expected results:
test should complete
Additional info:
Not sure if it is related, but I see error like:
Make sure that compose with a bad repo returns an error ... Directory walk started
Directory walk done - 1 packages
Temporary output repo path: /tmp/lorax-test-repo/.repodata/
Preparing sqlite DBs
Pool started (with 5 workers)
Pool finished
Process Process-1:
Traceback (most recent call last):
File "/usr/lib64/python3.6/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/usr/lib64/python3.6/multiprocessing/process.py", line 93, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3.6/site-packages/pylorax/api/queue.py", line 124, in monitor
uuids = sorted(os.listdir(joinpaths(cfg.composer_dir, "queue/new")), key=queue_sort)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/lorax.test.repo.ek9vlbji/var/lib/lorax/composer/queue/new'
ok
Ensure that metadata expire settings pick up changes to the repo immediately ... Directory walk started
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (lorax bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4662
Description of problem: For recent lorax builds the test gets stuck waiting for compose to finish Version-Release number of selected component (if applicable): lorax-28.14.46-1.el8 How reproducible: 100% Steps to Reproduce: 1.run lorax dist-git test on rhle-8.3.0 compose (an scratch build using rhel-8.3.0-candidate build target should be enough) 2. 3. Actual results: test runs for several hours repeating: :: [ 16:44:49 ] :: [ INFO ] :: Waiting for compose to finish ... 2020-06-02 16:44:49,074: /run/weldr/api.socket does not exist :: [ 16:45:09 ] :: [ INFO ] :: Waiting for compose to finish ... 2020-06-02 16:45:09,154: /run/weldr/api.socket does not exist Expected results: test should complete Additional info: Not sure if it is related, but I see error like: Make sure that compose with a bad repo returns an error ... Directory walk started Directory walk done - 1 packages Temporary output repo path: /tmp/lorax-test-repo/.repodata/ Preparing sqlite DBs Pool started (with 5 workers) Pool finished Process Process-1: Traceback (most recent call last): File "/usr/lib64/python3.6/multiprocessing/process.py", line 258, in _bootstrap self.run() File "/usr/lib64/python3.6/multiprocessing/process.py", line 93, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3.6/site-packages/pylorax/api/queue.py", line 124, in monitor uuids = sorted(os.listdir(joinpaths(cfg.composer_dir, "queue/new")), key=queue_sort) FileNotFoundError: [Errno 2] No such file or directory: '/tmp/lorax.test.repo.ek9vlbji/var/lib/lorax/composer/queue/new' ok Ensure that metadata expire settings pick up changes to the repo immediately ... Directory walk started