Namex API: Invalid state transition

[severinbeauvais]

Describe the bug in current situation
The Namerequest UI reported a HTTP 500 error in which the Namex API experienced "Invalid state transition [REJECTED] -> [INPROGRESS], valid states are [DRAFT, INPROGRESS]".

See Sentry log: https://sentry.io/organizations/registries/issues/2138028243/events/40c5fe935b874f8ab5f89a15c4345d52/?project=5433955

The call that failed was: PATCH https://namex.apps.silver.devops.gov.bc.ca/api/v1/namerequests/2124356/checkout

The subject NR id is: NR 5198093

Link bug to the User Story
None

Impact of this bug
The user was unable to do something.

Chance of Occurring (high/medium/low/very low)
This seems to occur 0 up to a few times a day for at least the last 30 days in Production.

Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Unknown

Steps to Reproduce
According to the Sentry breadcrumbs, the user was attempting to edit their existing NR.

Actual/ observed behavior/ results
See Sentry log.

Expected behavior
User can edit a NR without errors.

Screenshots/ Visual Reference/ Source
N/A

[jdyck-fw]

This potentially might be addressed with the edit work that SRE team will be doing after NRO decommission.

[severinbeauvais]

Note: I'm not sure whether this is an API or UI issue. Because it's in Sentry, it means the error was generated in Namerequest UI. It appears the UI is trying to change a Rejected NR to In Progress !?!?

[vysakh-menon-aot]

@severinbeauvais API tries to change the state to INPROGRESS only from checkout API call. At the same time the UI trigger the checkout API call only when the NR in DRAFT or INPROGRESS. Not sure how to reproduce it.

[severinbeauvais]

Thanks for the investigation.

According to Sentry, this error was last seen in release Name Reques v2.2.4 on July 8.

Therefore, if there is no additional information on this, I suggest we close this ticket. @lmcclung , do you agree?

[sienna-oldaccountdontuse]

Blocked by 8442, which will fix sentry. We will keep this open until we can use sentry to investigate further.
FYI @kialj876 @Kaineatthelab

[ozamani9gh]

Closing old ticket as per Severin's suggestion