UI fails to load with a "400 Bad Request" error

Bug #1628484 reported by Julie Pichon on 2016-09-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Honza Pokorny

Bug Description

The TripleO UI is installed via packages by default on new undercloud installs. Although the httpd configuration files appear to be set up properly, trying to access the UI results in a "400 Bad Request - Your browser sent a request that this server could not understand" error.

The error looks to be from Apache, there is nothing looking particularly useful in the console logs or Apache logs.

Browser console: "Failed to load resource: the server responded with a status of 400 (Bad Request) -"

tripleo-ui_access.log: - - [28/Sep/2016:12:56:25 +0100] "GET / HTTP/1.1" 400 226 "-" "Mozilla/5.0"

The error logs are empty.

I know there are some transient issues at the moment while we're waiting for dependent packages to get picked up, but I believe this is failing before even loading any Javascript.

Julie Pichon (jpichon) wrote :

I installed the undercloud with export DIB_INSTALLTYPE_puppet_modules=source, in case that turns out to be relevant.

Honza Pokorny (hpokorny) wrote :

A few more observations:

* changing the loglevel to debug still doesn't produce anything useful in the logs
* accessing the tripleo-ui vhost is results in a 400 both from the undercloud itself, and from outside via port forwarding.

Julie Pichon (jpichon) wrote :
Changed in tripleo:
milestone: none → newton-rc2
importance: High → Critical
assignee: nobody → Honza Pokorny (hpokorny)
Julie Pichon (jpichon) on 2016-09-28
Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: newton-rc2 → ocata-1
tags: added: newton-backport-potential
Changed in tripleo:
milestone: ocata-1 → newton-rc3
Julie Pichon (jpichon) wrote :

Newton backport proposed at https://review.openstack.org/#/c/381276/

Julie Pichon (jpichon) wrote :

Backport merged.

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/puppet-tripleo 5.3.0 release.

This issue was fixed in the openstack/puppet-tripleo 6.0.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers