Ocata to Pike upgrade leaves haproxy stopped

Bug #1742004 reported by David Ames on 2018-01-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack keystone charm
Medium
Alex Kavanagh
OpenStack neutron-api charm
Medium
Alex Kavanagh
OpenStack nova-cloud-controller charm
Medium
Alex Kavanagh

Bug Description

Ocata to Pike upgrade using 17.11 charm left haproxy stopped on all units.

The status output:

keystone/1 blocked idle 7/lxd/1 10.245.160.207 5000/tcp Services not running that should be: haproxy; Ports which s
hould be open, but are not: 5000, 35357

David Ames (thedac) on 2018-01-08
Changed in charm-keystone:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 18.02
James Page (james-page) on 2018-01-10
tags: added: upgrade
Changed in charm-neutron-api:
status: New → Triaged
importance: Undecided → High
Changed in charm-nova-cloud-controller:
status: New → Triaged
importance: Undecided → Critical
Changed in charm-neutron-api:
importance: High → Critical
milestone: none → 18.02
Changed in charm-nova-cloud-controller:
milestone: none → 18.02
Ryan Beisner (1chb1n) on 2018-01-10
Changed in charm-keystone:
assignee: nobody → Alex Kavanagh (ajkavanagh)
Changed in charm-neutron-api:
assignee: nobody → Alex Kavanagh (ajkavanagh)
Changed in charm-nova-cloud-controller:
assignee: nobody → Alex Kavanagh (ajkavanagh)
Alex Kavanagh (ajkavanagh) wrote :

I've tried a number of strategies; test setups to try to replicate this, but no luck yet.

David Ames (thedac) wrote :

Lowering priority as we have been unable to reproduce.

Changed in charm-keystone:
importance: Critical → Medium
Changed in charm-neutron-api:
importance: Critical → Medium
Changed in charm-nova-cloud-controller:
importance: Critical → Medium
James Page (james-page) on 2018-01-13
Changed in charm-keystone:
status: Triaged → Incomplete
Changed in charm-neutron-api:
status: Triaged → Incomplete
Changed in charm-nova-cloud-controller:
status: Triaged → Incomplete
David Ames (thedac) wrote :

This bug may reflect Tytus' comment in Bug#1737776:

https://bugs.launchpad.net/charm-designate/+bug/1737776/comments/7

Haproxy and pacemaker are interacting.

Ryan Beisner (1chb1n) on 2018-03-09
Changed in charm-keystone:
milestone: 18.02 → 18.05
Changed in charm-neutron-api:
milestone: 18.02 → 18.05
Changed in charm-nova-cloud-controller:
milestone: 18.02 → 18.05
James Page (james-page) on 2018-06-12
Changed in charm-keystone:
milestone: 18.05 → 18.08
Changed in charm-neutron-api:
milestone: 18.05 → 18.08
Changed in charm-nova-cloud-controller:
milestone: 18.05 → 18.08
James Page (james-page) on 2018-09-12
Changed in charm-keystone:
milestone: 18.08 → 18.11
Changed in charm-neutron-api:
milestone: 18.08 → 18.11
Changed in charm-nova-cloud-controller:
milestone: 18.08 → 18.11
David Ames (thedac) on 2018-11-20
Changed in charm-keystone:
milestone: 18.11 → 19.04
Changed in charm-neutron-api:
milestone: 18.11 → 19.04
Changed in charm-nova-cloud-controller:
milestone: 18.11 → 19.04
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers