Description of problem: on each controller node 9c1ce52febf0 192.168.24.1:8787/rhosp12/openstack-horizon-docker:20171115.1 "kolla_start" 11 hours ago Restarting (1) 3 hours ago horizon docker logs for container http://pastebin.test.redhat.com/533321 Version-Release number of selected component (if applicable): puddle 2017-11-16.2 How reproducible: always Steps to Reproduce: 1.Deploy OSP12 with 3controller and 2 compute nodes 2. Check docker containers on each controller node Actual results: Horizon container has restarting state Expected results: Horizon container has running state Additional info: openstack-nova-common-16.0.2-2.el7ost.noarch openstack-swift-account-2.15.1-3.el7ost.noarch python-openstackclient-lang-3.12.0-1.el7ost.noarch openstack-neutron-openvswitch-11.0.1-4.el7ost.noarch openstack-heat-api-cfn-9.0.1-3.el7ost.noarch python-openstacksdk-0.9.17-1.el7ost.noarch openstack-tripleo-heat-templates-7.0.3-7.el7ost.noarch openstack-ironic-conductor-9.1.3-0.20171106091155.fceb40f.el7ost.noarch openstack-tempest-17.1.0-1.el7ost.noarch openstack-mistral-executor-5.1.1-0.20171104083011.5372770.el7ost.noarch openstack-nova-scheduler-16.0.2-2.el7ost.noarch openstack-ironic-inspector-6.0.1-0.20171107185219.bad2e1c.el7ost.noarch openstack-mistral-common-5.1.1-0.20171104083011.5372770.el7ost.noarch openstack-tripleo-validations-7.4.2-1.el7ost.noarch openstack-zaqar-5.0.0-3.el7ost.noarch openstack-tripleo-puppet-elements-7.0.1-0.20171103211052.82d7e6c.el7ost.noarch openstack-neutron-common-11.0.1-4.el7ost.noarch openstack-neutron-ml2-11.0.1-4.el7ost.noarch python-openstackclient-3.12.0-1.el7ost.noarch puppet-openstacklib-11.3.1-0.20171030021712.00a9d9b.el7ost.noarch openstack-puppet-modules-11.0.0-0.20170828113154.el7ost.noarch openstack-tripleo-image-elements-7.0.1-0.20171103210122.2e61e31.el7ost.noarch openstack-swift-container-2.15.1-3.el7ost.noarch openstack-swift-proxy-2.15.1-3.el7ost.noarch openstack-heat-api-9.0.1-3.el7ost.noarch openstack-ironic-common-9.1.3-0.20171106091155.fceb40f.el7ost.noarch openstack-mistral-api-5.1.1-0.20171104083011.5372770.el7ost.noarch openstack-selinux-0.8.11-1.el7ost.noarch openstack-nova-placement-api-16.0.2-2.el7ost.noarch openstack-keystone-12.0.0-3.el7ost.noarch openstack-neutron-11.0.1-4.el7ost.noarch openstack-ironic-api-9.1.3-0.20171106091155.fceb40f.el7ost.noarch openstack-mistral-engine-5.1.1-0.20171104083011.5372770.el7ost.noarch openstack-nova-api-16.0.2-2.el7ost.noarch openstack-nova-conductor-16.0.2-2.el7ost.noarch openstack-tripleo-common-containers-7.6.3-3.el7ost.noarch openstack-nova-compute-16.0.2-2.el7ost.noarch openstack-heat-engine-9.0.1-3.el7ost.noarch openstack-tripleo-common-7.6.3-3.el7ost.noarch openstack-glance-15.0.0-3.el7ost.noarch openstack-swift-object-2.15.1-3.el7ost.noarch openstack-heat-common-9.0.1-3.el7ost.noarch puppet-openstack_extras-11.3.1-0.20171031014207.6
This is related to https://github.com/openstack/kolla/commit/7d7005e412f59028b00369ec7ab4997aa5d177f9 and us explicitly setting ENABLE_FWAAS to true in t-h-t, I'm not sure what is supposed to package neutron_fwaas_dashboard. I've looked at the tripleomaster/centos-binary-horizon:tripleo-current image and it doesn't have neutron_fwaas_dashboard either. Two possibilities here: - get the missing package in the image - stop enabling the dashboard for neutron fwaas in tripleo-heat-templates Moving this bug to the UI DFG.
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. https://access.redhat.com/errata/RHEA-2017:3462