juju-core

Juju-deployer incorrectly reporting errors in juju 1.24.0 environment

Bug #1470220 reported by Darryl Weaver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned
juju-deployer
New
Undecided
Unassigned
juju-gui
New
Undecided
Unassigned

Bug Description

Using juju 1.24.0 from bootstrapping to deploying an openstack bundle.
Initially errors were reported and juju-deployer -r 1 was used to resolve errors.
Juju-deployer reported numerous errors that were still not resolved.
However, juju status reports no errors.

I would assume this is a result of the new status reporting in juju 1.24.0.

I also checked with "juju resolved -r unit" to make sure and juju reported that the unit was not in error.

This is also related to false error reporting in Juju-gui as well.

Revision history for this message
Darryl Weaver (dweaver) wrote :

juju-gui version is deployed from the charmstore: cs:trusty/juju-gui-32
juju-deployer version is 0.4.3-0ubuntu1

Revision history for this message
Darryl Weaver (dweaver) wrote :

redeploying the juju-gui to another node still reports false errors.

Revision history for this message
Richard Harding (rharding) wrote :

We had another report of this from a user. In inspecting the frames over the websocket connection Juju was reporting that a relation was in error even though it had been resolved and status no longer showed the error.

The user had to leave before filing a bug or debugging further but said they'd be back so we didn't get it moved forward at all. If the deployer is reporting the issue I'm going to guess it's getting the same information over the juju api/websocket that the GUI is and Juju is conflicting itself.

Do you have a simple test case that we can demonstrate with that's more light weight than the openstack bundle? e.g. can we add two services, make a relation into error somehow, and then resolve it in the juju end having other clients still showing the error?

Revision history for this message
Darryl Weaver (dweaver) wrote :

Looks like the issue is to do with a difference between error reporting from juju CLI and the API.
It also looks like this is fixed in 1.24.2 which is proposed and should be released in about a week.

So, for production environments the advice should be to wait until 1.24.2 is out and upgrade afterwards as this has the fix.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.