overcloud controller os-refresh-config abort because haproxy horizon failed to bind socket

Bug #1409583 reported by Zhenzan Zhou on 2015-01-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Undecided
Unassigned

Bug Description

Some detail log:

Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: dib-run-parts Mon Jan 12 16:37:52 UTC 2015 Running /usr/libexec/os-refresh-config/configure.d/21-haproxy
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: + os-svc-enable -n haproxy
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: System start/stop links for /etc/init.d/haproxy already exist.
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: + service haproxy status
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: haproxy is running.
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: + service haproxy reload
Jan 12 16:37:52 demo-controller0-fbug7z57tsp6 os-collect-config: * Reloading haproxy haproxy
......
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: [ALERT] 011/163752 (33014) : Starting proxy horizon: cannot bind socket
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: [ALERT] 011/163752 (33014) : Starting proxy horizon: cannot bind socket
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: ...fail!
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: [2015-01-12 16:37:54,182] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 2]
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config:
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: [2015-01-12 16:37:54,182] (os-refresh-config) [ERROR] Aborting...
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: 2015-01-12 16:37:54.190 2257 ERROR os-collect-config [-] Command failed, will not cache new data. Command 'os-refresh-config' returned non-zero exit status 1
Jan 12 16:37:54 demo-controller0-fbug7z57tsp6 os-collect-config: 2015-01-12 16:37:54.191 2257 WARNING os-collect-config [-] Sleeping 30.00 seconds before re-exec.

The reason is that apache2 was started and occupied port 80 before 21-haproxy. We manually stopped apache2 and then os-refresh-config can complete all of its tasks successfully.

Ben Nemec (bnemec) wrote :

Which distro is this happening on?

Changed in tripleo:
status: New → Incomplete
Zhenzan Zhou (zhenzan-zhou) wrote :

It's Ubuntu 14.04.1.

Changed in tripleo:
status: Incomplete → New
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
Changed in tripleo:
assignee: nobody → Zhenzan Zhou (zhenzan-zhou)
status: Triaged → In Progress
Zhenzan Zhou (zhenzan-zhou) wrote :

By default, apache2 is enabled and listening on 0.0.0.0:80. Horizon itself doesn't care because it will apply its own configs and then enable apache2 and restart apache2 in post-configure stage. But with haproxy, we want apache2 to listen on specified interface and haproxy itself will listen on other interfaces for port 80. So we should stop apache2 in horizon pre-configure stage and let horizon to restart it again in its post-configure stage.

Change abandoned by James Slagle (<email address hidden>) on branch: master
Review: https://review.openstack.org/162549

Emilien Macchi (emilienm) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in tripleo:
status: In Progress → Triaged
assignee: Zhenzan Zhou (zhenzan-zhou) → nobody

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, NEWTON, OCATA, PIKE, QUEENS, QUEENS).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers