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:
According to the release notes of rhel9beta https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html-single/9.0_release_notes/index#BZ-2020529 should the systemd-resolved service be available as a Technology Preview. Even the systemd-249-7.el9_b.x86_64 package provides systemd-resolved, but in the package there is a broken link to /usr/bin/resolvectl

Version-Release number of selected component (if applicable):
systemd-249-7.el9_b.x86_64

How reproducible:
Install rhel9 beta with systemd-249-7.el9_b.x86_64 package. 

Steps to Reproduce:
1. 
# rpm -qa systemd
systemd-249-7.el9_b.x86_64

2. 
# yum provides resolvectl
Updating Subscription Management repositories.
Last metadata expiration check: 3:28:29 ago on Thu 02 Dec 2021 05:05:04 PM UTC.
Error: No Matches found

3. 
# ll /usr/sbin/resolvconf 
lrwxrwxrwx. 1 root root 17 Oct  2 10:28 /usr/sbin/resolvconf -> ../bin/resolvectl

# ll /usr/bin/resolvectl
ls: cannot access '/usr/bin/resolvectl': No such file or directory

# man resolvconf
man: can't open /usr/share/man/man1/resolvectl.1: No such file or directory
No manual entry for resolvconf

Actual results:
The tool resolvectl is not available

Expected results:
The tool resolvectl should be available

Additional info:

Hi,
today I saw that a newer version of systemd package, systemd-249-9.el9.x86_64.rpm, is available, and it looks a bit different now:

# yum provides resolvectl
Updating Subscription Management repositories.
Last metadata expiration check: 2:04:42 ago on Wed 08 Dec 2021 12:33:37 PM CET.
systemd-resolved-249-9.el9.x86_64 : System daemon that provides network name resolution to local applications
Repo        : rhel-9-for-x86_64-baseos-beta-rpms
Matched from:
Filename    : /usr/bin/resolvectl

# ll /usr/sbin/resolvconf 
lrwxrwxrwx. 1 root root 17 Nov 18 15:01 /usr/sbin/resolvconf -> ../bin/resolvectl

# ll /usr/bin/resolvectl
ls: cannot access '/usr/bin/resolvectl': No such file or directory

# man resolvconf
man: can't open /usr/share/man/man1/resolvectl.1: No such file or directory
No manual entry for resolvconf

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 (new packages: systemd), 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-2022:3979