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 1597179 - Wrongly resolved dependencies during upgrade
Summary: Wrongly resolved dependencies during upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1570562
TreeView+ depends on / blocked
 
Reported: 2018-07-02 08:11 UTC by Piotr Kliczewski
Modified: 2021-02-15 07:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-15 07:39:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Piotr Kliczewski 2018-07-02 08:11:39 UTC 
We have 2 services (vdsmd and supervdsm) which require libvirtd. Vdsmd requires supervdsmd. This looks like:

vdsmd -> supervdsmd -> libvirtd
vdsmd -> libvirtd

During yum update all services are updated. After the process is done only two services are up and running and one is dead when all of them were running prior to the update.

For logs please see related BZ #1570562.
Comment 2 Sandro Bonazzola 2018-07-16 13:06:43 UTC 
(In reply to Piotr Kliczewski from comment #0)
> We have 2 services (vdsmd and supervdsm) which require libvirtd. Vdsmd
> requires supervdsmd. This looks like:
> 
> vdsmd -> supervdsmd -> libvirtd
> vdsmd -> libvirtd
> 
> During yum update all services are updated. After the process is done only
> two services are up and running and one is dead when all of them were
> running prior to the update.
> 
> For logs please see related BZ #1570562.

Is this really a systemd bug?
Looking at patches attached to BZ #1570562 looks more like a vdsm services issue.
Also, it this bug really preventing BZ #1570562 to be fixed?
Comment 3 Martin Perina 2018-07-20 09:22:38 UTC 
(In reply to Sandro Bonazzola from comment #2)
> (In reply to Piotr Kliczewski from comment #0)
> > We have 2 services (vdsmd and supervdsm) which require libvirtd. Vdsmd
> > requires supervdsmd. This looks like:
> > 
> > vdsmd -> supervdsmd -> libvirtd
> > vdsmd -> libvirtd
> > 
> > During yum update all services are updated. After the process is done only
> > two services are up and running and one is dead when all of them were
> > running prior to the update.
> > 
> > For logs please see related BZ #1570562.
> 
> Is this really a systemd bug?
> Looking at patches attached to BZ #1570562 looks more like a vdsm services
> issue.
> Also, it this bug really preventing BZ #1570562 to be fixed?

This should be solved on systemd side, patches for BZ1570562 just mitigates the upgrade issue by aligning with current systemd behaviour, but as soon as it's fixed in system, we plan to remove that hack.
Comment 6 RHEL Program Management 2021-02-15 07:39:57 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.