Description of problem: Cannot update a deployed overcloud that was done using the UI like scaling-up/down, changing settings, etc. If it's possible, then we have a documentation bug here. If it's not possible, we should warn the customers that this feature is under development and that it should only be used by POC or provide documentation to actually export the plans and put them in /home/stack/templates/etc. We also have to let customer know that the "openstack overcloud deploy" command should use "-p" instead of "-e" but that they still require --templates. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy an overcloud using the UI 2. Try to update a setting and deploy ? 3. Actual results: We can only "Delete the overcloud" Expected results: We should be able to add more nodes, changing settings, etc Additional info:
This is requested for backporting to OSP12.
This should be easy to implement, and it was tested by using a combination of GUI + CLI: 1) Deploy a default plan (1 controller + 1 compute without SSL or network isolation or any other configurations) from the GUI 2) After deployment, increment the compute count to 2 and save changes 3) From the CLI, run: openstack overcloud plan deploy overcloud => Update succeeds! Problems encountered: 1) During the update, the plan deployment page is not populated (with the counters and plan configuration etc'). An error pops up: Stack Resources could not be loaded Cannot read property 'message' of undefined 2) It would be nice to see a progress bar in the GUI, as we have in the initial plan deployment 3) Also hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1599039
Oh , so no need to export the templates like I did then. Still, this should be documented if it's not. I didn't find it but it doesn't mean it doesn't exist.
*** Bug 1585450 has been marked as a duplicate of this bug. ***
Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1465574
Upstream master patch: https://review.openstack.org/#/c/607931/
Upstream stable/rocky backport: https://review.openstack.org/#/c/618586/
tripleo-ui has been removed from OSP15
This was fixed upstream, so if necessary, a future bug can refer to this, but otherwise I'm closing EOL as TripleO-UI has been deprecated upstream.