Regression #15898
closed
Changes to the ``admins`` user group are not synced to the secondary node
Added by Anonymous over 1 year ago.
Updated about 1 year ago.
Plus Target Version:
24.11
- Project changed from pfSense Plus to pfSense
- Category changed from XMLRPC to XMLRPC
- Status changed from New to Confirmed
- Priority changed from Normal to High
- Target version set to 2.8.0
- Affected Plus Version deleted (
24.11)
- Plus Target Version set to 24.11
I'm seeing this happen as well. Other group changes are synchronized, but not the "admins" group. On the secondary, not even the admin user is shown to be a member of the admins group.
Version: 24.11
I observed this as well on several HA deployments.
Since root is not in the admins group on the secondary. I tried manually adding the root user to admins group on the secondary, but didn't make a difference in syncing the admins group.
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:6ad2d8ff9f7d954f92c1dc0163b38a5cf2fa802b.
- Status changed from Feedback to Resolved
Marcos M wrote in #note-3:
Applied in changeset commit:6ad2d8ff9f7d954f92c1dc0163b38a5cf2fa802b.
Tested. Success. Admin group synced from primary to secondary. No errors.
- Subject changed from Membership of users in group 'admins' is not synced to backup system to Changes to the admins user group are not synced to the secondary node
- Assignee set to Marcos M
- Affected Version set to 2.7.2
- Affected Architecture deleted (
amd64)
- Subject changed from Changes to the admins user group are not synced to the secondary node to Changes to the ``admins`` user group are not synced to the secondary node
Also available in: Atom
PDF