Canonical Juju

juju resolve --no-retry behaviour is inverted

Bug #1762979 reported by Ian Booth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Ian Booth
Canonical Juju 2.4-beta1
2.3
Fix Released
High
Ian Booth
Canonical Juju 2.3.6

Bug Description

juju resolve --no-retry behaves the opposite to what is expected.

Using --no-retry incurs a retry and visa versa.

Revision history for this message
Ian Booth (wallyworld) wrote :

develop PR https://github.com/juju/juju/pull/8579
2.3 PR https://github.com/juju/juju/pull/8580

Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
Junien F (axino) wrote :

Hi,

Which version(s) is/are impacted by this bug, if any ?

Thanks

Revision history for this message
Ian Booth (wallyworld) wrote :

From what I could see in the code history, most Juju 2.x versions prior to 2.3.6 was impacted.
The suspect code landed in late 2016.

Anastasia (anastasia-macmood)
Changed in juju:
status: Fix Committed → Fix Released
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.