AIO-Duplex: Cont-1 does not get synced to new password changed after STX force to change password but cont-0 can be logged in

Bug #1883691 reported by Yatindra Shashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Won't Fix
Low
Unassigned

Bug Description

Brief Description
-----------------
Changed the password in the cont-0 after STX force to change it and had to lock/unlock the as cont-1 was of config out of date state. But now I am unable to login with old or new password in cont-1 but successfully able to login cont-0 with a new password.

Severity
--------

Major:

Steps to Reproduce
------------------
change the password in one controller and lock/unlock another controller(cont-0) from dashboard without login another controller(cont-1)

Expected Behavior
------------------
Should be able to login both the controller with new password.

Actual Behavior
----------------
Not able to login cont-1 after new password change.

Reproducibility
---------------

System Configuration
--------------------

AIO-Duplex, STX 3.0

Timestamp/Logs
--------------

[sysadmin@controller-0 ~(keystone_admin)]$ collect controller-1
[sudo] password for sysadmin:
collecting data from 1 host(s): controller-1
collecting controller-1_20200615.085124 ... failed to collect from controller-1 (reason:36:permission error)

.......................
Workaround:
[‎16/‎06/‎2020 11:13]
controller-0:~$ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PreferredAuthentications=password -o PubkeyAuthentication=no sysadmin@controller-1

Ghada Khalil (gkhalil)
tags: added: stx.3.0 stx.security
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Closing as stx.3.0 is EOL as of Dec 2020

Changed in starlingx:
importance: Undecided → Low
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.