Update from 25.1.b19 or b20 to 25.1 -> Breaks authentication, device unmanagable

[mfld-pub]

Had two test instances on development branch. One was 25.1_b19 and the other was b20.

Set branch to community and let it do its thing. Both rebooted after the update and now reject GUI credentials and SSH keys.

Was I supposed to run another update while still on development branch ? What is the recommended process to get from a 25.1 beta revision to 25.1 release ? Simply toggling the branch definitely did not go well :)

Only encountered this on upgrades from beta. 24.7.12_4 -> 25.1 updates are going well, currently I am 5 over 5 successful updates.

Edit: 25.1.r_38 to 25.1 works fine just toggling to from dev to community branch. It's just the earlier betas that die.

Edit2: I simply reset root password in single user mode and found the system running 24.7.12_4. Ran the updater again and both instances came up on 25.1 successfully. Maybe coming from an early beta broke  something that was needed for "The access management was rewritten in MVC"

[julsssark]

This was a known issue in RC1 dev that was fixed in RC2. The default anti-lockout rule was not working correctly.