At the moment both swift user and group IDs are not fixed in puppet, this means that their assigned IDs depend on package installation order. This in turn makes it clunky to do a reimage/reinstall while keeping the data disks intact. After reinstall the uid/gid in passwd are not guaranteed to match what's on the data disk filesystem.
The plan is thus to first fix the swift user/group uid/gid before puppet runs, then once the fleet is all at the same uid/gid we can let the admin module create the user/group as needed.
The UID/GID reserved for swift is 902 (previously 130), see also https://gerrit.wikimedia.org/r/c/operations/puppet/+/575217.
UID status as of Dec 2020.
===== NODE GROUP ===== (6) ms-be[2016-2021].codfw.wmnet ----- OUTPUT of 'id swift' ----- uid=111(swift) gid=116(swift) groups=116(swift) ===== NODE GROUP ===== (9) ms-be[2057-2061].codfw.wmnet,ms-be[1060-1063].eqiad.wmnet ----- OUTPUT of 'id swift' ----- uid=902(swift) gid=902(swift) groups=902(swift) ===== NODE GROUP ===== (80) ms-be[2022-2056].codfw.wmnet,ms-be[1022-1026,1028-1059].eqiad.wmnet,ms-fe[2005-2008].codfw.wmnet,ms-fe[1005-1008].eqiad.wmnet ----- OUTPUT of 'id swift' ----- uid=130(swift) gid=130(swift) groups=130(swift) ===== NODE GROUP ===== (3) ms-be[1019-1021].eqiad.wmnet ----- OUTPUT of 'id swift' ----- uid=112(swift) gid=117(swift) groups=117(swift)