Bug 1045521

Summary:	Unknown services fail restart during installation via zypper
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Ian Powell <bingmybong>
Component:	Basesystem	Assignee:	Johannes Meixner <jsmeix>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	bruno, dimstar, fbui
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ian Powell 2017-06-22 11:33:42 UTC

Two unknown services with a restart being attempted, all works okay though


(41/90) Installing: systemd-233-1.1.x86_64 ............................................................................................................
[done]
Additional rpm output:
Failed to try-restart systemd-resolved.service: Unit systemd-
Resolved.service
not found.



48/48) Installing: cups-2.2.3-211.1.x86_64 
............................................................................................................
[done]
Additional rpm output:
Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is 
missing the instance name.
See system logs and 'systemctl status cups-lpd@.service' for details.

# systemctl status cups-lpd@.service
Failed to get properties: Unit name cups-lpd@.service is missing the instance 
name.

Comment 1 Dominique Leuenberger 2017-06-22 12:13:29 UTC

zypp is only the messenger - systemd's package is the one trying to restart a servfice it does not ship

Comment 2 Bruno Friedmann 2017-06-22 12:46:39 UTC

Seems a bug in packaging:

Either we provide systemd-resolved.service, either we drop it (but for which reason)

rpm -ql system | grep resolv

/usr/lib/systemd/resolv.conf
/usr/share/man/man1/systemd-resolve.1.gz

Seems also that resolv.conf goes to /usr/lib/systemd/ when all our standard configuration goes to /etc/systemd/

I'm not sure to understand systemd-resolve and nss-resolve

Comment 3 Franck Bui 2017-06-22 15:22:29 UTC

(In reply to Ian Powell from comment #0)
> (41/90) Installing: systemd-233-1.1.x86_64
> .............................................................................
> ...............................
> [done]
> Additional rpm output:
> Failed to try-restart systemd-resolved.service: Unit systemd-
> Resolved.service
> not found.

I'll fix this one and the warning above is harmless.

Comment 4 Ian Powell 2017-06-23 07:34:51 UTC

(In reply to Franck Bui from comment #3)
> (In reply to Ian Powell from comment #0)
> > (41/90) Installing: systemd-233-1.1.x86_64
> > .............................................................................
> > ...............................
> > [done]
> > Additional rpm output:
> > Failed to try-restart systemd-resolved.service: Unit systemd-
> > Resolved.service
> > not found.
> 
> I'll fix this one and the warning above is harmless.

Thanks.  Just thought i'd report it to make the installs look tidier even though it didn't cause any problems.

Comment 5 Franck Bui 2017-06-23 07:39:35 UTC

You did well to report those warnings, thanks.

Comment 8 Ian Powell 2017-07-07 07:37:18 UTC

This one still exists.. install 07 July 2017

( 49/104) Installing: cups-2.2.3-211.3.x86_64 ..........................................................................................................[done]
Additional rpm output:
Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is missing the instance name.
See system logs and 'systemctl status cups-lpd@.service' for details.

Comment 9 Johannes Meixner 2019-11-28 14:23:25 UTC

The cups-lpd@.service issue was fixed via
https://bugzilla.suse.com/show_bug.cgi?id=1050845#c4

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