Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1438099 - horizon gets deconfigued in step3 of updates
horizon gets deconfigued in step3 of updates
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: Upstream M2
: 12.0 (Pike)
Assigned To: Alex Schultz
Udi
: Triaged
Depends On:
Blocks: 1421883 1438602 1438886
  Show dependency treegraph
 
Reported: 2017-03-31 19:34 EDT by Alex Schultz
Modified: 2018-02-05 14:07 EST (History)
5 users (show)

See Also:
Fixed In Version: puppet-tripleo-7.1.1-0.20170615141731.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1438602 (view as bug list)
Environment:
Last Closed: 2017-12-13 16:22:29 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1678338 None None None 2017-03-31 19:34 EDT
OpenStack gerrit 452349 None None None 2017-03-31 19:42 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Alex Schultz 2017-03-31 19:34:56 EDT
horizon gets deconfigured during update runs on an deployed cloud.

Steps to reproduce:
1) deploy overcloud
2) run deploy overcloud again
3) look at logs and notice that the horizon configuration is removed (in step3) and reapplied (in step4) of the subsequent run.

Logs:
step3 logs http://paste.openstack.org/show/605110/
step4 logs http://paste.openstack.org/show/605111/
Comment 6 errata-xmlrpc 2017-12-13 16:22:29 EST
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

Note You need to log in before you can comment on or make changes to this bug.