Details
-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
3.5.2
-
None
Description
The ordering for users to determine which sets of properties will be kept on upgrade relies on ordering the usernames by the date of most recent activity. The current implementation will, when backed by Postgres, count users with null date values as 'most recent'. (This will only affect instances where there are external and local users with the same username)
Attachments
Issue Links
- relates to
-
CONFSERVER-22139 Duplicate Key Violates Unique Constraint 'os_propertyentry_pkey' exception is being thrown on Upgrade to 3.5.x
- Closed