Bug 846483
| Summary: | systemd error message is incomplete, wrong | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | R P Herrold <herrold> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | johannbg, lnykryn, lpoetter, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-05 18:23:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
R P Herrold
2012-08-07 22:04:16 UTC
It would be better if you could fill separated bugs for all of this issues. So back to the original problem. What is the output of systemctl status network.service after start fails? 1) I think the reason network fails yet network is up and running is because a) he did not disable NetworkManager or b) set "NM_CONTROLLED=no" in /etc/sysconfig/network-scripts/ifcfg-$INTERFACE or c) virt magic is controlling the network interfaces. ( not a systemd bug ) 2) "secondary matter: the 'help' message offered is simply incomplete, and once supplemented, not a pointer to help" He will need to file a separated bug as you suggested with specific info on how he would like to see that error msg improved 3) "service network status" Here he is confusing service network status as in what is actually being done in the legacy sysv init script and systemctl status network.service and somehow expecting it being the same which it is not. ( not a systemd bug ) 4) "systemctl status network Failed to issue method call: Unit name network is not valid. and yet the parent initscript is named: network:" here he somehow expects the .service being omitted failing to understand we also have .targets ( like network.target ) and other unit endings so the unit ending cant be omitted when systemctl is run. ( not a systemd bug ) 5. The rest has been taken care of with the Documentation= for migrated units So this is bug winds up being essential potential man pages fixes and or improved help message which he as you suggested needs to be filed separately and of course with suggestion on how these should be improved... Trying to disect the issues raised here: 1. systemd only reports back if a service returned an unclean error code. It is not responsible to rollback any changes a service did. If you think that the network should have been shut down again on failure, or if the network shouldn't have returned an unclean exit code, then please file a bug against the initscripts package. 2. systemd in git (and soon F18) will now explicitly mention the failed service when it suggests to run "systemctl status xxx.service". This should fix the complaint about the misleading help text. This is also tracked in https://bugzilla.redhat.com/show_bug.cgi?id=845028 3. On F18 "systemctl status network" is now implicitly equivalent to "systemctl status network.service". This should fix the respective complaint, too. 4. "systemctl show" is supposed to be a tool for scripts and such like. It's output is not supposed to be read by humans as primary interface. That's what "systemctl status" is for. 5. I changed the warning messages to refer to "journalctl" rather than the "system journal", also for F18. This should fix this issue. 6. I've also added the reference to journalctl to the SEE ALSO section of the systemd man page. I think this resolves all issues. Next time, please file individual bugs, so that we can process them individually. systemd-190-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-190-1.fc18 Package systemd-191-2.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-191-2.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-191-2.fc18 then log in and leave karma (feedback). Package glibc-2.16-17.fc18, systemd-192-1.fc18, selinux-policy-3.11.1-23.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 systemd-192-1.fc18 selinux-policy-3.11.1-23.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/selinux-policy-3.11.1-23.fc18,rtkit-0.11-3.fc18,systemd-192-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). Package glibc-2.16-17.fc18, rtkit-0.11-3.fc18, systemd-193-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 rtkit-0.11-3.fc18 systemd-193-1.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-193-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). Thank you for the responses and changes |