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.

Description of problem:
The daemon should be restarted after package upgrade. Although the daemon end after inactivity period, so it will be updated after a while, this is not a good practice.
Not to mention that it may result in testing the old release of the package.

Version-Release number of selected component (if applicable):
realmd-0.16.1-5.el7

How reproducible:
always

Steps to Reproduce:
1. Start realmd , e.g. by
# realmd list
2. Quickly upgrade the package
# yum update reamlmd
3. Do whatever action what supposed to be fixed in the new release to see if it is ok.

Actual results:


Expected results:


Additional info:

This is a bug.

It is however a bug that is someone mitigated for real world use by the fact that realmd exits when not in use. It should timeout after a few minutes and exit.

Created attachment 1173498 [details]
Make DBus aware of systemd

Hi Stef,

I plan to add the attached patch to the RHEL build to allow systemd to restart a running realmd. It basically adds a 'SystemdService=realmd.service' to the org.freedesktop.realmd.service DBus service file to make sure DBus will use systemd to start realmd so that later on systemctl can find the running realmd process.

It would be nice if you can check if the patch makes sense and if this is something you might want in upstream as well

bye,
Sumit

Comment on attachment 1173498 [details]
Make DBus aware of systemd

Patch looks good.

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, 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://rhn.redhat.com/errata/RHBA-2016-2511.html