This article discusses the scenario where a commit error regarding UID mismatch when deleting a local user. 

When deleting a local user,  a warning and an error is generated:

[MASTER][edit]
user_demo@router-re0# commit and-quit
re0:
configuration check succeeds
re1:
[edit system login user test1 uid]
  'uid 2000'
    warning: statement does not match patch: '2000' != '2001'
error: remote load-configuration failed on re1

When a local user is created without specifying the UID, the first available UID is used on the system for the new account.  Under normal operation with commit synchronization turned on, the UID should be the same on both the primary and backup RE.

Scenario:

RE0 is the only router in the system OR commit synchronization is not turned on. 

• A local account called test is created and a UID assigned automatically on commit.

• After commit, RE0 /var/home directory contents.

• RE1 /var/home directory does not have the new test folder.  

• The test user is then deleted off of RE0.  The third column in file list /var/home detail changes from the username to the UID of the account.  

• Now, commit synchronize is turned on for RE0 and RE1.  RE0 still has the old test UID of 2000 on it, but that does not get synced to RE1 as test user was already deleted form the config.

• New account called test1 is created.  This gets synced to both routing-engines.  Because of the extra account on RE0 from the start, a different UID is put on RE0 and RE1, leading to the warning when you attempt to delete it later.

• RE0 UID is 2001 (one more than the 2000 that is still reserved for the old test account that was deleted). 

• RE1 UID is 2000 .

• If you attempt to delete the user test1, you get the warning and error that there is a UID mismatch.

When creating new users, manually specify the UID. 

1. Disable commit synchronization. 

2. Identify the user account folder in /var/home that is not the same on both routing-engines.  In this case, user test folder is only on RE0.   Delete it from the system.  

   user_demo@router-re0> start shell user root
   Password:
   % ls -l /var/home
   total 24
   drwxr-xr-x  3 user_demo  20  512 Aug 17 12:06 user_demo
   drwxr-xr-x  2 2000        20  512 Aug 26 11:17 test
   drwxr-xr-x  2 test1      20  512 Aug 26 11:26 test1
   % rm -rf test

3. On RE0 and RE1, delete user test1 we tried to delete before and commit.  

   RE0 - user_demo@router-re0# delete system login user test1
         user_demo@router-re0# commit
   RE1 - user_demo@router-re1# delete system login user test1
         user_demo@router-re1# commit

4. Delete test1 folder from /var/home on both RE0 and RE1 

   user_demo@router-re0> start shell user root 
   Password:
   root@router-re0:/var/home/user_demo # rm -rf /var/home/test1
   
   user_demo@router-re1> start shell user root 
   Password:
   root@router-re1:/var/home/user_demo # rm -rf /var/home/test1

5. Enable commit synchronization again.

   set system commit synchronize

6. Add new user test1 again, and now UID should be the same on both devices. 

   set system login user test1 class super-user authentication plain-text-password

7. UID now matches on both routing-engines. 

   user_demo@router-re0> show configuration system login user test1 | match uid 
   uid 2000 ;
    
   user_demo@router-re1> show configuration system login user test1 | match uid 
   uid 2000 ;

2021-03-24: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives