Description of problem: The Glance installation fails when setting Ceph as the back end. As I understand it, the Staypuft waits till the Ceph installation is done in order to install the Glance on the controllers. After the installation of the Ceph node was done, the Glance installation failed to start. Version-Release number of selected component (if applicable): ruby193-rubygem-staypuft-0.5.21-1.el7ost.noarch How reproducible: Unknown Steps to Reproduce: 1. Set a new deployment with Ceph as the Glance's back end 2. Deploy OSP 6 with Staypuft 3. Install the Ceph manually. 4. Run the Puppet on the controller in order to trigger the Glanc installation. Actual results: The trigger for the Glance installation is unknown, thus neither Staypuft or the user knows how to start its installation after the Ceph cluster is up and running. Expected results: Either there's a manual trigger that will install the Glance or the UI should clarify the automatic trigger for the Glance installation. Additional info:
Did you go back a and set 'include glance' to true after the controller and ceph cluster was configured? That is a known requirement for this to work.
per comment 5 -- this is not a bug.
The include glance parameter has the value: <%= @host.deployment.glance.ceph_backend? ? "false" : "true" %> how will the Staypuft will get the value "true" automatically? cause the Ceph node is installed - this is a bug.
(In reply to Yogev Rabl from comment #7) > The include glance parameter has the value: <%= > @host.deployment.glance.ceph_backend? ? "false" : "true" %> > > how will the Staypuft will get the value "true" automatically? cause the > Ceph node is installed - this is a bug. It's not automatic intentionally. It's manual. The Ceph deployment is completely outside our control, so there is no way for us to automatically update that setting. The user needs to manually update it
This is a bug, the bug is in the flow and the GUI. (1) There is not message/notification that the Glance will not be installed in this flow in the staypuft's GUI (2) The GUI should provide the user an easy way to install the Glance automatically instead of set it as one of the parameters in the advanced configuration. (3) The default setting of the "include Glance" parameter in the advanced configuration is "<%= @host.deployment.glance.ceph_backend? ? "false" : "true" %>" this configuration indicates that Staypuft is waiting for a signal. If this is not so, as you say, then the parameter is wrong and should be changed. From my POV the installation process is not clear, unfriendly and there's no indication for the user when and how he should act.
(In reply to Yogev Rabl from comment #9) > This is a bug, the bug is in the flow and the GUI. > > (1) There is not message/notification that the Glance will not be installed > in this flow in the staypuft's GUI At most a docs bug, IMO. We don't have any other cases like this in the UI so implementing something like this is an open question and we're unlikely to spend the time on it at this point. > (2) The GUI should provide the user an easy way to install the Glance > automatically instead of set it as one of the parameters in the advanced > configuration. This is a case for Glance on Ceph only. We can't (and won't) deploy a ceph cluster with the Installer and Glance fails to deploy if the ceph cluster is not there. If you use anything else, Glance is installed automatically. Adding some button or link to do the deployment after the manual ceph deployment is complete would be an RFE (which is unlikely to be implemented) > (3) The default setting of the "include Glance" parameter in the advanced > configuration is "<%= @host.deployment.glance.ceph_backend? ? "false" : > "true" %>" this configuration indicates that Staypuft is waiting for a > signal. > If this is not so, as you say, then the parameter is wrong and should be > changed. The parameter is correct. If you are deploying Ceph, we need the parameter to be false otherwise deployments will fail since the ceph cluster does not exist. If you choose anything other than ceph, we want to include the glance setup in the first run. > > From my POV the installation process is not clear, unfriendly and there's no > indication for the user when and how he should act. I agree it's not an ideal flow, but given the requirement for ceph to be deployed before doing the glance setup, there is not much else we can do without spending significant engineering effort which is not possible currently.
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open. For new deployments, please, use RHOSP director (starting with version 7). -- Jaromir Coufal -- Sr. Product Manager -- Red Hat OpenStack Platform [0] https://access.redhat.com/support/policy/updates/openstack/platform