Issues

Select view

Select search mode

 
17 of 17

Groups config rolled back after deleting a user in web UI

Fixed

Description

Steps to reproduce:

  1. Log in to web UI as an admin user

  2. Navigate to Configure OpenNMS / Configure Users, Groups, and On-Call Roles

  3. Add a new user user.a. No need to fill out details, just do the minimum.

  4. Add a new group group.a

  5. Add user user.a to group group.a

  6. Navigate back to User List

  7. Click the trash can beside user user.a and confirm intent to delete this user

Expected results:

  • User user.a is deleted

    • From the user list

    • From group group.a

  • Group group.a exists but is empty

Actual results:

  • Group group.a is also deleted

Further poking leads me to think that a stale copy of the groups configuration gets stored around the time of adding the user to the group and re-marshaled. For instance, if I also rename the built-in Remoting Users group along the way, that group's name reverts to its old value after deleting user.a.

Logging out and back in before deleting the user does not change the outcome. Restarting OpenNMS before deleting the user does.

Environment

New install

Acceptance / Success Criteria

None

Lucidchart Diagrams

Details

Assignee

Reporter

Labels

Components

Priority

PagerDuty

Created December 1, 2015 at 4:20 PM
Updated March 4, 2016 at 4:26 PM
Resolved March 4, 2016 at 11:28 AM

Activity

Show:

Jesse WhiteMarch 4, 2016 at 11:28 AM

Fixed with commit 7a983458067b36a87b7129461afde7712eea7fb2 in foundation-2016, cherry-picked to release-17.1.1.

Jeff GehlbachMarch 4, 2016 at 11:07 AM

Bamboo is green.

Jeff GehlbachMarch 3, 2016 at 2:05 PM

Jeff GehlbachFebruary 18, 2016 at 12:04 PM

Workaround, tested in Horizon 17.0.0:

Use the users ReST service to delete the unwanted user(s). The problem will not manifest. Example:

Jeff GehlbachFebruary 18, 2016 at 11:42 AM

Reported by a separate customer on Ticket 4365