| Summary: | [candidate] shinken | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | rverschelde, stormi-mageia, sysadmin-bugs, tmb |
| Version: | 4 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | has_procedure MGA4-32-OK MGA4-64-OK advisory | ||
| Source RPM: | shinken | CVE: | |
| Status comment: | |||
| Attachments: | Output of journalctl -b for shinken-1.4-5.1.mga4 | ||
|
Samuel Verschelde
2014-02-12 19:46:34 CET
CC:
(none) =>
stormi List of packages both archs and including SRPMs *** Arch: i586 *** RPMs from 'core-updates_testing' ======================== shinken-1.4-5.1.mga4.noarch.rpm shinken-arbiter-1.4-5.1.mga4.noarch.rpm shinken-broker-1.4-5.1.mga4.noarch.rpm shinken-poller-1.4-5.1.mga4.noarch.rpm shinken-reactionner-1.4-5.1.mga4.noarch.rpm shinken-receiver-1.4-5.1.mga4.noarch.rpm shinken-scheduler-1.4-5.1.mga4.noarch.rpm SRPMs from 'core-updates_testing' ======================== shinken-1.4-5.1.mga4.src.rpm *** Arch: x86_64 *** RPMs from 'core-updates_testing' ======================== shinken-1.4-5.1.mga4.noarch.rpm shinken-arbiter-1.4-5.1.mga4.noarch.rpm shinken-broker-1.4-5.1.mga4.noarch.rpm shinken-poller-1.4-5.1.mga4.noarch.rpm shinken-reactionner-1.4-5.1.mga4.noarch.rpm shinken-receiver-1.4-5.1.mga4.noarch.rpm shinken-scheduler-1.4-5.1.mga4.noarch.rpm SRPMs from 'core-updates_testing' ======================== shinken-1.4-5.1.mga4.src.rpm Whiteboard:
(none) =>
has_procedure Created attachment 4986 [details] Output of journalctl -b for shinken-1.4-5.1.mga4 Testing on Mageia 4 x86_64, using the procedure in comment 0. The bug can be reproduce, but the update does not fix it. See the output of journalctl -b when trying to start the service after the update. CC:
(none) =>
remi
Rémi Verschelde
2014-02-14 23:12:34 CET
Whiteboard:
has_procedure =>
has_procedure feedback
Rémi Verschelde
2014-02-14 23:19:44 CET
Attachment 4986 is obsolete:
0 =>
1 Actually the update works for most services, one just has to reboot the system after having updated shinken.
I thought there was still one issue because when trying to start shinken-skonf, the service fails with:
Failed to issue method call: Unit mongod.service failed to load: No such file or directory.
But it's simply that (from what I see) there is no shinken-skonf service, Thierry probably made a typo.
Here is a fixed procedure (please correct me if I'm wrong):
New test procedure:
===================
1) install shinken:
urpmi shinken{,-{arbiter,poller,reactionner,scheduler,broker,receiver}}
2) start all the services:
for i in arbiter poller reactionner scheduler broker receiver; do systemctl start shinken-$i.service; done
3) see there's python errors in journalctl -b
4) update
5) reboot
6) restart all the services:
for i in arbiter poller reactionner scheduler broker receiver; do systemctl restart shinken-$i.service; done
7) see there's no more errors
Now I can say the tests are successful for Mageia 4 x86_64. Whiteboard:
has_procedure feedback =>
has_procedure MGA4-64-OK Testing complete Mageia 4 i586. Validating update. Advisory has been uploaded, please push to 4 core/updates. Keywords:
(none) =>
validated_update Update pushed: http://advisories.mageia.org/MGAA-2014-0050.html Status:
NEW =>
RESOLVED |
Advisory: ========= This update fixes shinken not starting due to some python error List of packages: ================== shinken-1.4-5.1.mga4.noarch.rpm shinken-arbiter-1.4-5.1.mga4.noarch.rpm shinken-broker-1.4-5.1.mga4.noarch.rpm shinken-poller-1.4-5.1.mga4.noarch.rpm shinken-reactionner-1.4-5.1.mga4.noarch.rpm shinken-receiver-1.4-5.1.mga4.noarch.rpm shinken-scheduler-1.4-5.1.mga4.noarch.rpm Test procedure: ================ 1) install shinken: urpmi shinken{,-{arbiter,poller,reactionner,scheduler,broker}} 2) start all the services: for i in arbiter poller reactionner scheduler broker skonf; do systemctl start shinken-$i.service; done 3) see there's python errors in journalctl -b 4) update 5) restart all the services: for i in arbiter poller reactionner scheduler broker skonf; do systemctl restart shinken-$i.service; done 6) see there's no more errors Reproducible: Steps to Reproduce: