[astute] Check cobbler system getks before deployment

[Matthew Mosesohn]

We could prevent bugs #1264515 from happening if we checked the exit code from cobbler system getks --name=node-XX for each host before rebooting nodes. If there is a server error, it will return 1. The output is quite useless in all the cases I can produce an error, so we should simply fail deployment with "Check Cobbler logs for details".

[Vladimir Sharshov (vsharshov)]

Hi, Matt.

Can you help me and find XML-RPC call which do same as 'cobbler system getks --name=node-XX'. Is it http://fossies.org/dox/cobbler-cobbler-2.4.0-1/classcobbler_1_1remote_1_1CobblerXMLRPCInterface.html#a7d8b60e18aa4c481c479668e02e54af5 ?

[Matthew Mosesohn (raytrac3r)]

Vladimir,
You don't need XMLRPC to download KS. It's available via HTTP. Log into Cobbler Web, and hit view kickstart for the host you are interested in. That URL will work and you can substitute the host name for each host you need. The page will return 500 internal server error if you have problems rendering the file.

[Matthew Mosesohn (raytrac3r)]

We still need this because Ubuntu preseed rendering failures result in cryptic errors.

[Matthew Mosesohn (raytrac3r)]

Also, bugs should still always have an owner (even if it's a team)

[Dmitry Pyzhov (dpyzhov)]

We are going to switch to ironic

[Matthew Mosesohn (raytrac3r)]

We should consider this fix for 5.1 (we won't see ironic till Fuel 6)

[Dima Shulyak (dshulyak)]

How this is related to neutron?

[Dmitry Pyzhov (dpyzhov)]

Will be absoleted by https://blueprints.launchpad.net/fuel/+spec/volume-manager-refactoring