haproxy charm is stuck in an executing state preventing relation changes

Bug #1504602 reported by Tim Kuhlman
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Invalid
High
Unassigned

Bug Description

I run 'juju remove-relation landscape-client haproxy' in my environment successfully and then attempt to update the landscape-client charm and get this error 'ERROR cannot upgrade service "landscape-client" to charm "local:trusty/landscape-client-21": would break relation "landscape-client:juju-info haproxy:juju-info"'

After looking at juju status I can see that indeed the relation still exists. Also all of the haproxy units show they are in an executing state. The date in the since: field corresponded to a juju upgrade from a month ago. I logged onto the 3 haproxy units and restarted juju-unit-haproxy* and this resulted in the date being updated to today but no other change.

Revision history for this message
Tim Kuhlman (timkuhlman) wrote :

The current juju version is 1.24.5 the previous version was 1.24-beta2.1

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Cheryl Jennings (cherylj) wrote :

Can you attach the unit logs for landscape-client and haproxy, as well as all-machines.log?

Revision history for this message
Michael Nelson (michael.nelson) wrote :

This sounds like it could be a duplicate of bug 1494542.

That is, the initial 'juju remove-relation landscape-client haproxy' was queued, but not yet run, because the one of the services is still "executing".

This "executing" state can be triggered with juju (prior to 1.24.7 or 1.25 beta 1), if a `juju run` command is run after a hook fails (basically, juju doesn't set the state back to the error state).

Revision history for this message
Tim Kuhlman (timkuhlman) wrote :

Sorry for the slow response, somehow I didn't get an email on your comments. I've attached the logs.

Revision history for this message
Tim Kuhlman (timkuhlman) wrote :
Changed in juju-core:
status: Triaged → Invalid
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.