Project

General

Profile

Actions

Regression #15898

closed

Changes to the ``admins`` user group are not synced to the secondary node

Added by Dean Chang 5 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
XMLRPC
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:

Description

When I add or remove the group 'admins' for a user via the user manager, the change does not happen on the backup system. Same if I do it via the group management.

The reason might be this change:

https://github.com/pfsense/pfsense/commit/3e0facb20fa46a13bf7b70d6ddb1970b00485eb2

related to this bug ticket:

https://redmine.pfsense.org/issues/15067

The GID of the 'admins' group is 1999, but in xmlrpc.php, groups with GID below 2000 are now exempt from deletion (and probably recreation with the changed members).

Actions #1

Updated by Jim Pingle 5 months ago

  • 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.

Actions #2

Updated by Craig Coonrad about 2 months ago

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.

Actions #3

Updated by Marcos M about 2 months ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Craig Coonrad about 2 months ago

  • Status changed from Feedback to Resolved

Marcos M wrote in #note-3:

Applied in changeset 6ad2d8ff9f7d954f92c1dc0163b38a5cf2fa802b.

Tested. Success. Admin group synced from primary to secondary. No errors.

Actions #5

Updated by Marcos M about 2 months ago

  • 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)
Actions #6

Updated by Marcos M about 2 months ago

  • 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
Actions

Also available in: Atom PDF