Bug 1563633

Summary: RFE - Systemctl is-enabled command showing status of rpcbind as indirect instead of enabled/disabled
Product: Red Hat Enterprise Linux 7 Reporter: Yogita <ysoni>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: systemd-maint-list, xzhou, yoyang, ysoni
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-24 06:32:33 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:

Description Yogita 2018-04-04 11:21:04 UTC
Description of problem:
Systemctl is-enabled command showing status of rpcbind as indirect instead of enabled/disabled

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

# rpm -qa | grep rpcbind
rpcbind-0.2.0-42.el7.x86_64

# rpm -qa | grep systemd
systemd-219-42.el7.x86_64
systemd-sysv-219-42.el7.x86_64
systemd-libs-219-42.el7.x86_64
systemd-python-219-42.el7.x86_64

How reproducible:

Steps to Reproduce:
# systemctl status rpcbind
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: inactive (dead)
# systemctl enable rpcbind
# systemctl is-enabled rpcbind
indirect                     <--- indirect was not expected here, ideally should be enabled/disabled

# systemctl status rpcbind
● rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
   Active: inactive (dead)


Actual results:
# systemctl is-enabled rpcbind
indirect                     <--- indirect was not expected here, ideally should be enabled/disabled

Expected results:
# systemctl is-enabled rpcbind
enabled


Additional info:
From automation point of view (using tools like puppet,ansible,chef), customer requires that the indirect output should something that should be more precise.

Comment 5 Yongcheng Yang 2018-05-15 02:21:21 UTC
(In reply to Yogita from comment #0)
Hi Yogita,

Looks to me like this issue has been resolved in rpcbind-0.2.0-43.el7
(via Bug 1425663).  If so, maybe we can duplicate this to bz1425663
(change back to rpcbind).  Apologies didn't remember it before.

Please help to have another test with the latest rpcbind package.

> Description of problem:
> Systemctl is-enabled command showing status of rpcbind as indirect instead
> of enabled/disabled
> 
> Version-Release number of selected component (if applicable):
> 
> # rpm -qa | grep rpcbind
> rpcbind-0.2.0-42.el7.x86_64
> 

[root@~]# rpm -q rpcbind
rpcbind-0.2.0-42.el7.x86_64
[root@~]# systemctl restart rpcbind
[root@~]# systemctl disable rpcbind && systemctl is-enabled rpcbind
Removed symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket.
indirect
^^^^^^^^
[root@~]# systemctl enable rpcbind && systemctl is-enabled rpcbind
Created symlink from /etc/systemd/system/sockets.target.wants/rpcbind.socket to /usr/lib/systemd/system/rpcbind.socket.
indirect
^^^^^^^^
[root@~]# 
[root@~]# rpm -Uvh rpcbind-0.2.0-43.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:rpcbind-0.2.0-43.el7             ################################# [ 50%]
Cleaning up / removing...
   2:rpcbind-0.2.0-42.el7             ################################# [100%]
[root@~]# rpm -q rpcbind
rpcbind-0.2.0-43.el7.x86_64
[root@~]# systemctl restart rpcbind
[root@~]# systemctl disable rpcbind && systemctl is-enabled rpcbind
disabled
^^^^^^^^
[root@~]# systemctl enable rpcbind && systemctl is-enabled rpcbind
Created symlink from /etc/systemd/system/multi-user.target.wants/rpcbind.service to /usr/lib/systemd/system/rpcbind.service.
enabled
^^^^^^^^
[root@~]#

Comment 6 Yogita 2019-10-24 06:32:33 UTC
Hi Yongcheng,

Apologise for late response. I have informed this to the customer, but the customer have not shared any update on this.

I tired this on my test server and it was working as expected. Thanks alot, I'm closing this bugzilla case as there no further action needed.

*** This bug has been marked as a duplicate of bug 1425663 ***