Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-8010

Groups config rolled back after deleting a user in web UI



    • Bug
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Fixed
    • 1.10.12, Meridian-2015.1.1, 17.0.0
    • 17.1.1, Meridian-2016.1.0
    • Web UI - Admin
    • Security Level: Default (Default Security Scheme)
    • New install


      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.




            jeffg Jeff Gehlbach
            jeffg Jeff Gehlbach
            0 Vote for this issue
            2 Start watching this issue