Bug #3788
closedReboot proxy command does not work on oVirt image
Description
It just does not reboot :-) As simple as that.
Updated by Lukas Zapletal about 11 years ago
- Status changed from Assigned to Ready For Testing
Updated by Lukas Zapletal about 11 years ago
- Status changed from Ready For Testing to Assigned
Damn scratch that
Updated by Dominic Cleal about 11 years ago
- Target version changed from 1.10.0 to 1.9.3
Updated by Lukas Zapletal about 11 years ago
- Status changed from Assigned to Ready For Testing
Updated by Greg Sutcliffe about 11 years ago
Works great, apart from a tiny error in the foreman logs:
ForemanDiscovery: Rebooting 5254008fae8f.sapphire.elysium.emeraldreverie.org as its being discovered and assigned
Failed to reboot: 500 Internal Server Error
Nothing seems broken, the host correctly reboots and provisions - I suspect the format of the result of the API call to the proxy on the discovered node for reboot isn't what Foreman is expecting.
Updated by Lukas Zapletal almost 11 years ago
Hmmm and do we expect a response? Because now it is systemd driven (maybe faster). I am under impression that the moment the shutdown command is executed, proxy service can be starting down. Requests that are being processed may be reporting 500 error.
I am doing some tests to confirm this is the behavior of Sinatra/webrick and if so, we would like to put 500 into the list of expected results :-D
Updated by Lukas Zapletal almost 11 years ago
Ok the error is: Permission denied - /dev/tty1
In lib/proxy/log.rb on this line
@@logger = Logger.new(SETTINGS.log_file, 6, 1024*1024*10)
It's because I configured proxy log to /dev/tty1.
The fix is to either chmod 777 /dev/tty1
or to put "foreman" into tty group
[root@localhost ~]# ll /dev/tty1* crw--w---- 1 root tty 4, 1 Jan 6 14:51 /dev/tty1
Updated by Anonymous almost 11 years ago
- Target version changed from 1.9.3 to 1.9.2
Updated by Lukas Zapletal almost 11 years ago
- Status changed from Ready For Testing to Resolved