[opensuse-factory] Latest update via zypper dup
Hi Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about? Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm-last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm-grow- continue@.service is not valid. Regards Ian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2016-05-12 at 14:07 +0100, ianseeks wrote:
Hi
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm- last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm- grow- continue@.service is not valid.
I'd not start worrying - but you should file a bug for it. Anything with @.service is 'special' and the standard macros should not try to touch them. They can't be activated without further parameters anyway. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 12 May 2016 16:51:35 BST Dominique Leuenberger / DimStar wrote:
On Thu, 2016-05-12 at 14:07 +0100, ianseeks wrote:
Hi
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm- last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm- grow- continue@.service is not valid.
I'd not start worrying - but you should file a bug for it.
Done. Logged it against libzypp as i couldn't find zypper in the list: Bug 979749
Anything with @.service is 'special' and the standard macros should not try to touch them. They can't be activated without further parameters anyway.
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
12.05.2016 19:08, ianseeks пишет:
On Thursday, 12 May 2016 16:51:35 BST Dominique Leuenberger / DimStar wrote:
On Thu, 2016-05-12 at 14:07 +0100, ianseeks wrote:
Hi
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm- last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm- grow- continue@.service is not valid.
I'd not start worrying - but you should file a bug for it.
Done. Logged it against libzypp as i couldn't find zypper in the list: Bug 979749
It has nothing to do with zypper. Bug is either in mdadm package or in systemd macros. Either mdadm should not list templates, or systemd macros should not attempt to restart them. I tend to think it is mdadm bug. Although it opens up interesting question - how to reliably restart templated services when template changed ...
Anything with @.service is 'special' and the standard macros should not try to touch them. They can't be activated without further parameters anyway.
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016.05.12 19:46, Andrei Borzenkov rašė:
Although it opens up interesting question - how to reliably restart templated services when template changed ...
Maybe in *.spec file for RPM building, you can write script in %post, %posttrans and/or %postun section -- Regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 12 May 2016 19:46:08 BST Andrei Borzenkov wrote:
12.05.2016 19:08, ianseeks пишет:
On Thursday, 12 May 2016 16:51:35 BST Dominique Leuenberger / DimStar wrote:
On Thu, 2016-05-12 at 14:07 +0100, ianseeks wrote:
Hi
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm- last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm- grow- continue@.service is not valid.
I'd not start worrying - but you should file a bug for it.
Done. Logged it against libzypp as i couldn't find zypper in the list: Bug 979749
It has nothing to do with zypper. Bug is either in mdadm package or in systemd macros. Either mdadm should not list templates, or systemd macros should not attempt to restart them. I tend to think it is mdadm bug.
Thanks. I went the bug in bugzilla to change it from libzypp to mdadm but its not in the components list - any ideas?
Although it opens up interesting question - how to reliably restart templated services when template changed ...
Anything with @.service is 'special' and the standard macros should not try to touch them. They can't be activated without further parameters anyway.
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Donnerstag, 12. Mai 2016, 19:12:29 CEST schrieb ianseeks:
On Thursday, 12 May 2016 19:46:08 BST Andrei Borzenkov wrote:
12.05.2016 19:08, ianseeks пишет:
On Thursday, 12 May 2016 16:51:35 BST Dominique Leuenberger / DimStar
Done. Logged it against libzypp as i couldn't find zypper in the list: Bug 979749
It has nothing to do with zypper. Bug is either in mdadm package or in systemd macros. Either mdadm should not list templates, or systemd macros should not attempt to restart them. I tend to think it is mdadm bug. Thanks. I went the bug in bugzilla to change it from libzypp to mdadm but its not in the components list - any ideas?
Not every package has its own component - that would make the list *very* long [1] ;-) Instead, choose something that looks like a close match (for mdadm, I'd take "Basesystem"). Bonus points if you assign the bug to the package bugowner - which you can find out with osc: # osc maintainer -e mdadm Defined in package: Base:System/mdadm bugowner of mdadm : neilb AT suse.com <---- here we are ;-) maintainer of mdadm : [...] Regards, Christian Boltz [1] says the maintainer of a package which has its own component *g* --
Ist doch laut Deinen Schilderungen von den Hardwareanforderungen her eine perfekte Konkurrenz zu Vista *renn* ;-) Da hast du recht ! Aber warum rennen :-) es wird dir kaum jemand hinterherlaufen weil alle vor der Kiste sitzen um auf die Katalogupdates zu warten ... [> Benjamin Zeller und Helmut Zengerling in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 13 May 2016 21:25:20 BST Christian Boltz wrote:
Hello,
Am Donnerstag, 12. Mai 2016, 19:12:29 CEST schrieb ianseeks:
On Thursday, 12 May 2016 19:46:08 BST Andrei Borzenkov wrote:
12.05.2016 19:08, ianseeks пишет:
On Thursday, 12 May 2016 16:51:35 BST Dominique Leuenberger / DimStar
Done. Logged it against libzypp as i couldn't find zypper in the list: Bug 979749
It has nothing to do with zypper. Bug is either in mdadm package or in systemd macros. Either mdadm should not list templates, or systemd macros should not attempt to restart them. I tend to think it is mdadm bug.
Thanks. I went the bug in bugzilla to change it from libzypp to mdadm but its not in the components list - any ideas?
Not every package has its own component - that would make the list *very* long [1] ;-) Instead, choose something that looks like a close match (for mdadm, I'd take "Basesystem").
Bonus points if you assign the bug to the package bugowner - which you can find out with osc:
# osc maintainer -e mdadm Defined in package: Base:System/mdadm bugowner of mdadm : neilb AT suse.com <---- here we are ;-)
maintainer of mdadm : [...]
Thanks. I went to update the bug report but someone else has already done it and assigned it to Neil.
Regards,
Christian Boltz
[1] says the maintainer of a package which has its own component *g*
Ist doch laut Deinen Schilderungen von den Hardwareanforderungen her eine perfekte Konkurrenz zu Vista *renn* ;-)
Da hast du recht ! Aber warum rennen :-) es wird dir kaum jemand hinterherlaufen weil alle vor der Kiste sitzen um auf die Katalogupdates zu warten ... [> Benjamin Zeller und Helmut Zengerling in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2016-05-12 15:07, ianseeks wrote:
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm-last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm-grow- continue@.service is not valid.
No; in the meantime, it has also been fixed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2016-05-12 15:07, ianseeks wrote:
Just got this error during the install on openSUSE Tumbleweed (20160511) (x86_64) - is it anything to worry about?
Updating /etc/sysconfig/mdadm ... Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid. Failed to try-restart mdadm-last-resort@.service: Unit name mdadm-last- resort@.service is not valid. Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm-grow- continue@.service is not valid.
No; in the meantime, it has also been fixed.
On Tuesday, 24 May 2016 19:01:29 BST Jan Engelhardt wrote: thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Christian Boltz -
Dominique Leuenberger / DimStar -
ianseeks -
Jan Engelhardt -
opensuse.lietuviu.kalba