Closed eehret closed 1 year ago
The command used is something like Systemctl list-units --type=service --no-legend --all --no-pager rhnsd.service
@gaelcolas Thanks! Interestingly if I manually stop the service manually and then run systemctl list-units --type=service --no-legend --all --no-pager rhnsd.service
then no output is returned and exit code is zero.
If I start the service manually and run same command then I get rhnsd.service loaded active running LSB: Starts the Spacewalk Daemon
and exit code 0.
Not sure if this helps or not, just putting it out there :)
@jodi-boone I suspect this may have gotten fixed via https://github.com/Azure/nxtools/pull/35 Retesting now to confirm.
Confirmed, this seems to have been fixed via https://github.com/Azure/nxtools/pull/35 I am no longer able to reproduce this specific issue.
Details of the scenario you tried and the problem that is occurring
I have a RHEL virtual machine on which I'm attempting to ensure that the 'rhnsd' service is stopped. The service does exist on the target VM, but the nxService component is erroneously reporting that it does not and crashes. I believe this problem is similar but distinct from the one I reported in https://github.com/Azure/nxtools/issues/30 , which is why I've opened a separate issue.
Verbose logs showing the problem
Suggested solution to the issue
I can't suggest a specific solution other than to change the code that's trying to locate the service, since apparently it isn't functioning as it should. The below command executed on the target VM shows that the service in question does, in fact, exist:
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
RHEL 7.9
Version and build of PowerShell the target node is running
7.3.6
Version of the DSC module that was used
1.2.0