Project

General

Profile

Actions
Copy link

Defect #1809

closed

Failed/Blocked provisionings are ignored when doing another provisioning

Added by Alena Peterová over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
High
Assignee:
Vít Švanda
Category:
Provisioning
Target version:
Rhyolite (9.7.5)
Start date:
08/21/2019
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

Version 9.7.4
(the bug was introduced after upgrading to 9.7.0 from 9.7.0-SNAPSHOT b01ad57e5e80aae2c13f2629e0b8efee5bf0cd84)

When there are some failed provisionings in the queue and another provisioning is created, it's attempted. But it shouldn't be attempted, it should be waiting in the state "Not executed - another provisioning is already in the queue".

Steps to reproduce locally:
  • create a virtual system
  • create an account on the system
  • block Update operations
  • change e.g. the first name of the identity -> the operation is Blocked
  • unblock Update operations
  • change e.g. the last name of the identity -> the operation is executed

Files

Download all files
provisioning_archive.png (24.3 KB) provisioning_archive.png Alena Peterová, 08/21/2019 09:15 PM
blocked_active_operation.png (20.5 KB) blocked_active_operation.png Alena Peterová, 08/21/2019 09:15 PM

Related issues

Related to IdStory Identity Manager - Task #1736: State of request on a systems (+ propagation to the VS)ClosedVít Švanda07/01/2019

Actions
Actions
Copy link
 #1

Updated by Radek Tomiška over 4 years ago

  • Assignee changed from Vít Švanda to Radek Tomiška
Actions
Copy link
 #2

Updated by Vít Švanda over 4 years ago

  • Assignee changed from Radek Tomiška to Vít Švanda
Actions
Copy link
 #3

Updated by Vít Švanda over 4 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by Vít Švanda over 4 years ago

  • Target version set to Rhyolite (9.7.5)

I simulated this bug. I created this bug during implementation of request system state. There I needed persist provisioning-operation in created state (because transaction). This is primary cause this problem. I fixed problem with no creation NOT_EXECUTED operations, but this caused next problems (for example in case when multiple provisioning are executed during one transaction, then second operation is marked as NOT_EXECUTED).

I didn't found correct solution yet (more precisely some tests do not passing now).

Actions
Copy link
 #5

Updated by Vít Švanda over 4 years ago

  • % Done changed from 0 to 50
Actions
Copy link
 #6

Updated by Vít Švanda over 4 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Vít Švanda to Radek Tomiška
  • % Done changed from 50 to 90
Actions
Copy link
 #7

Updated by Radek Tomiška over 4 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 90 to 100

I did test (brake, readonly, inactive, merge exclueded contracts) and operation is not executed, when some operation for the same entity is in queue, thx! Code is nice too.

Actions
Copy link
 #8

Updated by Vít Švanda over 4 years ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #9

Updated by Radek Tomiška over 4 years ago

  • Related to Task #1736: State of request on a systems (+ propagation to the VS) added
Actions
Copy link

Also available in: Atom PDF