Bug #1676
closed
Trying to disable or delete a PI after creation is not taken into account
Added by François ARMAND about 13 years ago.
Updated over 12 years ago.
Category:
Web - Config management
Description
If one creates a policy instance, update its form and save, close the success pop-up and then try to disable or delete it, there is a success pop-up but the action is not taken into account.
If the newly created PI is loaded back with a click on it from the tree, delete/disable work again.
- Target version changed from 20 to 19
- Target version changed from 19 to 21
- Target version changed from 21 to 23
- Category set to 9
- Priority changed from 2 to 4
This is a rare case, with a simple workaround, downgrading priority
- Target version changed from 23 to 2.3.0
- Assignee set to François ARMAND
- Target version changed from 2.3.0 to 18
- Target version changed from 18 to 2.4.0~alpha1
- Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2
- Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
- Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
- Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
- Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6
- Status changed from New to 2
- Priority changed from 4 to 3
- Target version changed from 2.4.0~alpha6 to 2.4.0~beta1
- Target version changed from 2.4.0~beta1 to 2.4.0~beta2
- Status changed from 2 to Discussion
This bug does not seems to be here anymore, perhaps due to #2632 correction.
Moreover, #2529 is also corrected, and an event log is done on disable.
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
- Status changed from Discussion to In progress
- Assignee changed from François ARMAND to Jean VILVER
- Status changed from In progress to Pending technical review
François ARMAND wrote:
This bug does not seems to be here anymore, perhaps due to #2632 correction.
Yeah I just tried, it's not. But If we reload the page we lost the directive selection in the tree. I'm creating a ticket for this behavior.
- Status changed from Pending technical review to Released
Also available in: Atom
PDF