Created attachment 916172 [details] production.log from the staypuft host. Rubygem-Staypuft: Unable to assign hosts to deployment when installation media wasn't configured during execution of rhel-osp-installer. Environment: rhel-osp-installer-0.1.0-2.el6ost.noarch Steps to reproduce: 1. Install rhel-osp-installer. 2. Execute rhel-osp-istaller and configure it normally-per your requirements until you reach the "installation media" menu . 3. When you get to "Now you should configure installation media which will be used for provisioning." Click on '3' to skip this step. 4. Skip the subscription manager. 5. Once the installation is finished - create a deployment of 2 hosts (nova controller + compute). 6. Attempt to assign hosts to the deployment. Result: The host doesn't get assigned, while I get a yellow notification in the right top corner saying "Unassigned hosts: <hostname>". Expected result: the host should become assigned.
We can't assign hosts if the installation was not done. There's a notice on installer's media page: 'Note that if you don't configure it properly, host provisioning won't work until you configure installation media manually.' Should we change it so it's more clear? E.g. 'Note that if you don't configure it properly or skip this step, deployment won't work until you configure installation media manually.'
Well, no matter what is done during the installation, the UI should notify accordingly or disallow assigning hosts until the installation media is set.
So the expected result is to display the reason why the host can't be assigned?
Yes. Thinking about scenario when one admin installed the rhel-osp-installer and didn't have the right installation media to configure. Then another tries to create a deployment. The message he'll get in the current situation is not clear. Thanks.
OK, this is an error-reporting issue. It should be fixed but I don't think it's a blocker.
I think https://github.com/theforeman/staypuft/pull/234 solves this.
Verified: rhel-osp-installer-0.1.9-1.el6ost.noarch Note the user gets this message: Unassigned hosts: maca25400702875 Medium can't be blank
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html