juju resolve --no-retry behaviour is inverted

Bug #1762979 reported by Ian Booth on 2018-04-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Ian Booth
2.3
High
Ian Booth

Bug Description

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

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

Ian Booth (wallyworld) on 2018-04-12
Changed in juju:
status: In Progress → Fix Committed
Junien Fridrick (axino) wrote :

Hi,

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

Thanks

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.

Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers