Request 593305 (accepted)

2018-03-30 07:52:15 <1> susetest(5068) [Ruby] modules/Service.rb:140 Starting service 'rpcbind'
2018-03-30 07:52:15 <1> susetest(5068) [Ruby] yast2/systemctl.rb:32 systemctl show rpcbind.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath 
2018-03-30 07:52:15 <1> susetest(5068) [Ruby] yast2/systemctl.rb:32 systemctl start rpcbind.service 
2018-03-30 07:52:15 <3> susetest(5068) [bash] ShellCommand.cc(shellcommand):78 Failed to start rpcbind.service: Unit rpcbind.service is not loaded properly: Invalid argument.
2018-03-30 07:52:15 <3> susetest(5068) [bash] ShellCommand.cc(shellcommand):78 See system logs and 'systemctl status rpcbind.service' for details.
2018-03-30 07:52:15 <1> susetest(5068) [Ruby] yast2/systemctl.rb:32 systemctl show rpcbind.service  --property=Id  --property=MainPID  --property=Description  --property=LoadState  --property=ActiveState  --property=SubState  --property=UnitFileState  --property=FragmentPath 
2018-03-30 07:52:15 <3> susetest(5068) [Ruby] modules/Service.rb:443 Attempt to `start` service 'rpcbind' failed.

Dominique Leuenberger (dimstar) - over 6 years ago

reviewer

let alone that the changelog is subpar:

+- Update to 0.2.4

And what's special about this version? (except that it does not work?)

Dominique Leuenberger (dimstar) - over 6 years ago

reviewer

The .service file inside the rpm is corrupt, as patch 0001* ADDS a definition to a previously non-existing file, which now exists by upstream.

sr 593203 supposedly fixes it (untested, but can't be worse than what we have here)