Bug 1312971

Summary: "Init Processes" doesn't list symlinked services
Product: Red Hat CloudForms Management Engine Reporter: Vadim Rutkovsky <vrutkovs>
Component: SmartState AnalysisAssignee: Hui Song <hsong>
Status: CLOSED ERRATA QA Contact: Pavol Kotvan <pakotvan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: dajohnso, jhardy, jprause, obarenbo, roliveri, vrutkovs
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:smartstate
Fixed In Version: 5.6.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1314389 (view as bug list) Environment:
Last Closed: 2016-06-29 15:40:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1314389    

Description Vadim Rutkovsky 2016-02-29 16:34:29 UTC
Description of problem:
"Init processes" doesn't list some services after SSA is performed on the instance

Version-Release number of selected component (if applicable):
5.5.2.4

How reproducible:
Always

Steps to Reproduce:
1. Prepare the appliance for fleecing (smartstate role, vddk etc.)
2. Spin up any fedora-based VM (I used F22)
3. Compare 'Init Processes' list with systemctl output on the VM

Actual results:
Init Processes doesn't list services which are put in /usr/lib/systemd/system via symlinking, e.g. dracut-* and dbus-* services are not listed, while those are present in 'systemctl list-unit-files --type service' output:

# ls -la /usr/lib/systemd/system/dracut-cmdline.service 
lrwxrwxrwx. 1 root root 55 Jun 16  2015 /usr/lib/systemd/system/dracut-cmdline.service -> ../../dracut/modules.d/98systemd/dracut-cmdline.service

Expected results:
All services which can be started are listed

Additional info:

Comment 5 errata-xmlrpc 2016-06-29 15:40:02 UTC
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://access.redhat.com/errata/RHBA-2016:1348