mitaka (T + X): haproxy not listening

Bug #1545217 reported by Ryan Beisner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-dashboard (Juju Charms Collection)
Fix Released
Critical
James Page

Bug Description

Trusty-Mitaka + Xenial-Mitaka: haproxy not listening.

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1067/sshd
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 11732/memcached
tcp6 0 0 :::433 :::* LISTEN 14538/apache2
tcp6 0 0 :::22 :::* LISTEN 1067/sshd
tcp6 0 0 :::70 :::* LISTEN 14538/apache2

...

01:08:02.992 2016-02-13 02:33:01,241 test_400_connection DEBUG: Checking dashboard http response...
01:08:02.992
01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka DEBUG : Got exit code: 1
01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka RESULT : FAIL

...

urllib2.URLError: <urlopen error [Errno 111] Connection refused>

Related branches

Ryan Beisner (1chb1n)
description: updated
Revision history for this message
James Page (james-page) wrote : Re: [Bug 1545217] Re: mitaka (T + X): dashboard not listening

haproxy template needs updates for 1.6.x

On Sat, 13 Feb 2016 at 03:11 Ryan Beisner <email address hidden>
wrote:

> ** Description changed:
>
> Trusty-Mitaka + Xenial-Mitaka: horizon not listening.
>
> - tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 1067/sshd
> - tcp 0 0 127.0.0.1:11211 0.0.0.0:*
> LISTEN 11732/memcached
> - tcp6 0 0 :::433 :::*
> LISTEN 14538/apache2
> - tcp6 0 0 :::22 :::*
> LISTEN 1067/sshd
> + tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 1067/sshd
> + tcp 0 0 127.0.0.1:11211 0.0.0.0:*
> LISTEN 11732/memcached
> + tcp6 0 0 :::433 :::*
> LISTEN 14538/apache2
> + tcp6 0 0 :::22 :::*
> LISTEN 1067/sshd
> tcp6 0 0 :::70 :::*
> LISTEN 14538/apache2
> +
> + ...
> +
> + 01:08:02.992 2016-02-13 02:33:01,241 test_400_connection DEBUG: Checking
> dashboard http response...
> + 01:08:02.992
> + 01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka DEBUG : Got
> exit code: 1
> + 01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka RESULT : FAIL
> +
> + ...
> +
> + urllib2.URLError: <urlopen error [Errno 111] Connection refused>
>
> --
> You received this bug notification because you are a member of OpenStack
> Charmers, which is subscribed to openstack-dashboard in Juju Charms
> Collection.
> https://bugs.launchpad.net/bugs/1545217
>
> Title:
> mitaka (T + X): dashboard not listening
>
> Status in openstack-dashboard package in Juju Charms Collection:
> New
>
> Bug description:
> Trusty-Mitaka + Xenial-Mitaka: horizon not listening.
>
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 1067/sshd
> tcp 0 0 127.0.0.1:11211 0.0.0.0:*
> LISTEN 11732/memcached
> tcp6 0 0 :::433 :::*
> LISTEN 14538/apache2
> tcp6 0 0 :::22 :::*
> LISTEN 1067/sshd
> tcp6 0 0 :::70 :::*
> LISTEN 14538/apache2
>
> ...
>
> 01:08:02.992 2016-02-13 02:33:01,241 test_400_connection DEBUG: Checking
> dashboard http response...
> 01:08:02.992
> 01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka DEBUG : Got
> exit code: 1
> 01:08:02.992 juju-test.conductor.019-basic-trusty-mitaka RESULT : FAIL
>
> ...
>
> urllib2.URLError: <urlopen error [Errno 111] Connection refused>
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/openstack-dashboard/+bug/1545217/+subscriptions
>

Ryan Beisner (1chb1n)
summary: - mitaka (T + X): dashboard not listening
+ mitaka (T + X): haproxy not listening
description: updated
James Page (james-page)
Changed in openstack-dashboard (Juju Charms Collection):
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → James Page (james-page)
James Page (james-page)
Changed in openstack-dashboard (Juju Charms Collection):
status: In Progress → Fix Committed
tags: added: openstack
Changed in openstack-dashboard (Juju Charms Collection):
milestone: none → 16.04
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-openstack-dashboard (master)

Fix proposed to branch: master
Review: https://review.openstack.org/289535

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-openstack-dashboard (master)

Reviewed: https://review.openstack.org/289535
Committed: https://git.openstack.org/cgit/openstack/charm-openstack-dashboard/commit/?id=9e9e145b7be104ff9417d475774dc4cff0a5a5c2
Submitter: Jenkins
Branch: master

commit 9e9e145b7be104ff9417d475774dc4cff0a5a5c2
Author: David Ames <email address hidden>
Date: Mon Mar 7 11:40:27 2016 -0800

    Add sleep between stop/start in restart_on_change

    When restart_on_change runs service restart apache is not waiting for
    its threads to terminate particularly due to WSGI being involved for
    openstack-dashboard. When it attempts to restart the ports are already
    in use and unavailable. This change works around this bug adding a sleep
    time between stop and start to allow apache time to terminate its
    threads.

    Closes-Bug: #1545217
    Related-Bug: #1552822

    Change-Id: Ib5d4dee9a001b4554191abfdc7577ef739efd0f2

Changed in openstack-dashboard (Juju Charms Collection):
status: Fix Committed → 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.