This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2142007 - osbuild-worker gets killed and is kept stopped on package upgrade
Summary: osbuild-worker@1.service gets killed and is kept stopped on package upgrade
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: osbuild-composer
Version: 8.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Image Builder team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-11 11:47 UTC by Tomáš Hozza
Modified: 2023-09-18 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 13:19:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4610 0 None Migrated None 2023-09-18 13:19:46 UTC
Red Hat Issue Tracker RHELPLAN-139162 0 None None None 2022-11-11 11:50:03 UTC

Description Tomáš Hozza 2022-11-11 11:47:20 UTC 
Description of problem:
When osbuild-composer package is updated on a RHEL system where osbuild-composer is already running, the upgrade process results in the local worker to be killed and not started again. The result is that while osbuild-composer is running and responds to API requests, none of the jobs are ever picked by a worker, because there is none running.

Version-Release number of selected component (if applicable):
osbuild-composer-62-3.el8_7

How reproducible:
always

Steps to Reproduce:
1. dnf install -y osbuild-composer composer-cli  <-- e.g. on RHEL-8.6
2. systemctl enable --now osbuild-composer.socket
3. composer-cli status show
4. systemctl status osbuild-worker
5. enable the latest RHEL-8 repos
6. dnf upgrade -y osbuild-composer  <-- scriptlets take long time and it seems that systemd times out and kills processes
7. composer-cli status show
8. systemctl status osbuild-composer.service
9. systemctl status osbuild-worker  <-- inactive (code=killed, signal=TERM)

Actual results:
osbuild-worker is inactive after RPM package upgrade

Expected results:
osbuild-worker should be running after RPM package upgrade, if it was running before the upgrade

Additional info:
Workaround is to start the worker service manually using:
systemctl start osbuild-worker
Comment 2 RHEL Program Management 2023-09-18 13:19:17 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3 RHEL Program Management 2023-09-18 13:19:50 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.