(dry run) Error when updating only name/description for authorization role

Description

Overview: Error when updating only name/description for authorization role

Steps to reproduce:

  1. Login to non-ECS dry run LoC environment

  2. Go to “Settings” → “Authorization roles”

  3. Click on the name of any existing authorization role with capability sets and/or capabilities assigned

  4. Click “Edit” button in third pane

  5. Update name and/or description of a role

  6. Click “Save & close” button

Expected result: Role editing window is closed. A role with updated name and/or description can be found in a list in second pane

Actual result: Role editing window remains opened. Error pop-up appears with following text:

{"name":"HTTPError","response":{}}“

PUT /roles/<role UUID>/capability-sets request returns with 400 status and following response body

Additional information:

  • Also reproducible on ECS dry run LoC environment but in this case, no error pop-up is shown (everything else the same)

  • Also reproducible on dry run FSE/INT environments

  • Also reproducible on non-ECS LoC Phase 2 Sandbox 2 (LoC)

  • Also reproducible on evrk2

  • See screencasts:

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

6

Checklist

hide

Activity

Show:

Yauhen Viazau April 26, 2024 at 5:03 PM

Also not reproducible on LoC phase I pre-validation (LoC account) environment (“ref“ tenant)

Yauhen Viazau April 18, 2024 at 10:42 AM

Re-tested on LoC phase I pre-validation environment (ECS, non-ECS) - works as expected

A role name/description can be updated. See example:

 

Yauhen Viazau April 3, 2024 at 12:41 PM
Edited

Issue is reproducible on LoC phase I pre-validation environment (ECS, non-ECS). Awaiting release and deployment there

Yauhen Viazau April 2, 2024 at 12:06 PM

Tested on evrk2 - works as expected

Authorization role can be successfully saved after only updating name/description, See example:

 

Ryan Berger March 21, 2024 at 2:39 PM

Tried again and was able to reproduce in EVRK2 as well. This is a code defect.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Eureka

Fix versions

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 13, 2024 at 2:53 PM
Updated November 5, 2024 at 2:40 PM
Resolved April 3, 2024 at 12:41 PM
TestRail: Cases
TestRail: Runs