After upgrade M->N horizon doesn't work

Bug #1598114 reported by Vitaliy Nogin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Unassigned

Bug Description

Detailed bug description:
After upgrade M->N horizon doesn't work

Error message from horizon-error.log:

[:error] [pid 3086:tid 140688128423680] Invalid HTTP_HOST header: u'infra1_horizon_container-2a61be7d:80'. The domain name provided is not valid according to RFC 1034/1035.

From my point of view we should use ip-addresses here instead of container name.

Steps to reproduce:
Upgrade OSAD from M to N

Expected results:
Ability to open dashboard

Actual result:
503 Service Unavailable error

Reproducibility:
100%

Workaround:
Change ServerName value in /etc/apache2/sites-available/openstack-dashboard.conf file from container name to container ip-address and restart apache2 service.

Impact:
-

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

FYI, this was done from a 13.0.1 instead of a latest M (13.1.3) to latest N.

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

As a reminder, the mitaka branch was the location of a major change in OSA: hostnames changes (RFC1035 support).

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

M->N is still heavily WIP. Please see the blueprint here: https://blueprints.launchpad.net/openstack-ansible/+spec/upgrade-mitaka-newton

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

This should be fixed. Please have a look at the following review:
https://review.openstack.org/#/c/350955/

Changed in openstack-ansible:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.