Hide Forgot
Description of problem: I installed OSP 9 using https://github.com/flofuchs/tripleo-ui-playbooks to have the GUI on it also. The file ~/rhci-tripleo-api/tripleo.conf contained the default keystone url (to 192.0.2.1) although on my system all the endpoints are on 172.16.0.1. The service didn't work as a result, and I believe it also caused the default plan to not be loaded. How reproducible: 100% Steps to Reproduce: 1. Call rhos9-pre-undercloud-install.sh 2. Edit your ~/undercloud.conf and change all 192.0.2.1 to 172.16.0.1 3. Install the undercloud with "openstack undercloud install" 4. Run the post-installation: "ansible-playbook -i hosts rhos9-post-install.yaml" Actual results: If you look in the resulting ~/rhci-tripleo-api/tripleo.conf, it still thinks that keystone is on 192.0.2.1 Expected results: The configuration from undercloud.conf should be considered
tripleo-ui on OSP 9 is not supported. Issues with that script should be opened as either tripleo/tripleo-ui bugs in launchpad or perhaps github issues on that repo. Bugzillas are not really relevant.
(In reply to Mike Burns from comment #2) > tripleo-ui on OSP 9 is not supported. Issues with that script should be > opened as either tripleo/tripleo-ui bugs in launchpad or perhaps github > issues on that repo. Bugzillas are not really relevant. Hi Mike, rhel-osp-director-ui will be internally supported as POC. The ansible script is specifically for setup and configuration of the UI on top of RHOS9, not RDO. I've submitted an internal bugzilla to create a new rhel-osp-director-ui component in Bugzilla so all the downstream related bugs will be assigned to the correct component. @apannu Please advise
Addressed by this change: https://github.com/rdo-management/tripleo-ui-playbooks/commit/f2500df65def9ebba32942a73fabc3aa5bb4b616
Btw, I created a new Issue for this bug on github. That seems the more appropriate location for bugs related to the osp9 ui installer: https://github.com/rdo-management/tripleo-ui-playbooks/issues/3
This has been fixed, and it worked for me in the last OSP9 deploy.
This is closed - writing this to clear needinfo