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 1375882 - [SPEC] dbus-org.freedesktop.network1.service should go to systemd-networkd
Summary: [SPEC] dbus-org.freedesktop.network1.service should go to systemd-networkd
Keywords:
Status: CLOSED DUPLICATE of bug 1404444
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
: 1385522 (view as bug list)
Depends On:
Blocks: 74systemd
TreeView+ depends on / blocked
 
Reported: 2016-09-14 07:24 UTC by Petr Sklenar
Modified: 2017-02-20 12:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-20 12:49:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Sklenar 2016-09-14 07:24:28 UTC 
Description of problem:
rpm -ql systemd shows many strange stuff
please investigate

Version-Release number of selected component (if applicable):
systemd-219-29.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1./usr/lib/systemd/system/dbus-org.freedesktop.network1.service is broken symlink

2.
rpm -qf /etc/systemd/system/runlevel5.target
systemd-219-29.el7.x86_64
ll /etc/systemd/system/runlevel5.target
ls: cannot access /etc/systemd/system/runlevel5.target: No such file or directory

and more:
/etc/machine-info: cannot open (No such file or directory)
/etc/systemd/system/runlevel2.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel3.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel4.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel5.target: cannot open (No such file or directory)
/var/lib/systemd/backlight: cannot open (No such file or directory)
/var/lib/systemd/clock: cannot open (No such file or directory)
/var/lib/systemd/rfkill: cannot open (No such file or directory)
/var/log/journal: cannot open (No such file or directory)


Actual results:
broken symlink
there are files in the list but not on disk

Expected results:


Additional info:

for i in `rpm -ql systemd`; do file $i;done

search for broken/cannot ^
Comment 1 Lukáš Nykrýn 2016-09-14 08:48:11 UTC 
Besides the dbus-org.freedesktop.network1.service symlink everything else is fine. Those files are marked as %ghost so it means that they are not packed inside the rpm, but they can exist on the machine. For example /var/log/journal will be created when user enables persistent logging.
Comment 2 Lukáš Nykrýn 2016-10-17 09:13:05 UTC 
*** Bug 1385522 has been marked as a duplicate of this bug. ***
Comment 3 Lukáš Nykrýn 2017-02-20 12:49:40 UTC 

*** This bug has been marked as a duplicate of bug 1404444 ***
Note You need to log in before you can comment on or make changes to this bug.