Bug 519366
Summary: | "rc6: goal changed" after reboot command | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan ONDREJ <ondrejj> | ||||||
Component: | upstart | Assignee: | Petr Lautrbach <plautrba> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 11 | CC: | cdahlin, notting, plautrba | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-10-02 07:58:17 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Jan ONDREJ
2009-08-26 11:10:12 UTC
I am not able to reproduce your problem. Can you reproduce it on another system? Also try to add "--debug" to kernel grub line and follow debug output on console or log via serial Created attachment 363313 [details]
Problematic rc script.
Looks like this was caused by an script, which has "stop" command in "stop)" section. This command does nothing from shell, only displays "missing job name". Curious, that stops shutdown script execution. This bug has been fixed in this script and reboot works well now.
If you consider, this is not a bug, you can close this bug.
Created attachment 363323 [details]
Problematic rc skript (previous one was fixed one)
the problem is that calling initctl command ("stop" is same as "initctl stop") inside running job causes that the command is applied to actual job. in this case stop is called on rc6 job, rc6 is stopped and doesn't continue anymore. This seems more like a configuration error, than anything else. I think we should likely close this. You could argue that its good form to unset the UPSTART_* variables from our rc* job before calling sysv scripts, but I don't think that it causes bugs like this with enough frequency to warrant that. I agree that it's more configuration error, closing as not a bug |