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.
Description of problem:
systemd-resolved.service is changed to enabled after systemd version up.
Version-Release number of selected component (if applicable):
Before systemd version up:
systemd-239-30.el8_2.x86_64
After systemd version up:
systemd-239-31.el8_2.2.x86_64
How reproducible:
100%
Steps to Reproduce:
Before systemd version up:
# rpm -qa | grep systemd
systemd-239-30.el8_2.x86_64
python3-systemd-234-8.el8.x86_64
systemd-pam-239-30.el8_2.x86_64
systemd-udev-239-30.el8_2.x86_64
rpm-plugin-systemd-inhibit-4.14.2-37.el8.x86_64
systemd-libs-239-30.el8_2.x86_64
[root@node-0 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.2 (Ootpa)
[root@node-0 ~]# systemctl is-enabled systemd-resolved.service
disabled
[root@node-0 ~]# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolvedhttps://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managershttps://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
===========================================================
After update systemd version to systemd-239-31.el8_2.2.x86_64,
systemd-resolved.service is changed to enabled
============================================================
# yum update systemd-239-31.el8_2.2.x86_64
# reboot
# rpm -qa | grep systemd
systemd-libs-239-31.el8_2.2.x86_64
python3-systemd-234-8.el8.x86_64
systemd-pam-239-31.el8_2.2.x86_64
systemd-udev-239-31.el8_2.2.x86_64
rpm-plugin-systemd-inhibit-4.14.2-37.el8.x86_64
systemd-239-31.el8_2.2.x86_64
[root@node-0 ~]#
[root@node-0 ~]# systemctl is-enabled systemd-resolved.service
enabled
Actual results:
systemd-resolved.service is changed to enabled after systemd version up.
Expected results:
systemd-resolved.service is still disabled even if systemd version up.
Mengyi
Description of problem: systemd-resolved.service is changed to enabled after systemd version up. Version-Release number of selected component (if applicable): Before systemd version up: systemd-239-30.el8_2.x86_64 After systemd version up: systemd-239-31.el8_2.2.x86_64 How reproducible: 100% Steps to Reproduce: Before systemd version up: # rpm -qa | grep systemd systemd-239-30.el8_2.x86_64 python3-systemd-234-8.el8.x86_64 systemd-pam-239-30.el8_2.x86_64 systemd-udev-239-30.el8_2.x86_64 rpm-plugin-systemd-inhibit-4.14.2-37.el8.x86_64 systemd-libs-239-30.el8_2.x86_64 [root@node-0 ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.2 (Ootpa) [root@node-0 ~]# systemctl is-enabled systemd-resolved.service disabled [root@node-0 ~]# systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients =========================================================== After update systemd version to systemd-239-31.el8_2.2.x86_64, systemd-resolved.service is changed to enabled ============================================================ # yum update systemd-239-31.el8_2.2.x86_64 # reboot # rpm -qa | grep systemd systemd-libs-239-31.el8_2.2.x86_64 python3-systemd-234-8.el8.x86_64 systemd-pam-239-31.el8_2.2.x86_64 systemd-udev-239-31.el8_2.2.x86_64 rpm-plugin-systemd-inhibit-4.14.2-37.el8.x86_64 systemd-239-31.el8_2.2.x86_64 [root@node-0 ~]# [root@node-0 ~]# systemctl is-enabled systemd-resolved.service enabled Actual results: systemd-resolved.service is changed to enabled after systemd version up. Expected results: systemd-resolved.service is still disabled even if systemd version up. Mengyi