Hide Forgot
Description of problem: If the user in provision is authenticated with ssh_key, then use "reset password" feature to add a new user that is authenticated with password, I cannot use the new user to access to the VM from other hosts because of "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." If I execute "service sshd reload" on the VM, then I can use the new user to access to the VM from other hosts with password. Version-Release number of selected component (if applicable): WALinuxAgent-2.0.18-rc4(upstream) WALinuxAgent-2.0.16-1 How reproducible: Always Steps to Reproduce: 1. Prepare a VM with WALinuxAgent installed. The new user must be authenticated with ssh_key while provisioning. 2. On portal, use "reset password" to add a new user which is authenticated with password. 3. Try to use the new user to access to the VM from other hosts. 4. Execute "service sshd reload" on the VM, then rerun step 3. Actual results: In step 3, we cannot use the new user to access to the VM from other hosts because of "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." In step 4, we can use the new user to access to the VM from other hosts. Expected results: Without executing "service sshd reload" manually, we can use the new user to access to the VM from other hosts. Additional info: It seems that "PasswordAuthentication" in /etc/ssh/sshd_config is changed from "no" to "yes", but the sshd service is not reloaded.
This bug reported in VMAccessForLinux-1.4.0.0. Still exists in VMAccessForLinux-1.4.1.0.
(In reply to yuxisun from comment #3) > This bug reported in VMAccessForLinux-1.4.0.0. > Still exists in VMAccessForLinux-1.4.1.0. Does that mean that it still exists in the 2.1.5 rebase?
Setting Devel Conditional NAK: Patch for rhel-6.9
(In reply to Dave Anderson from comment #4) > (In reply to yuxisun from comment #3) > > This bug reported in VMAccessForLinux-1.4.0.0. > > Still exists in VMAccessForLinux-1.4.1.0. > > Does that mean that it still exists in the 2.1.5 rebase? Actually, I think it is not related to WALinuxAgent, but only an issue of an extension named "VMAccessForLinux". This is an independent tool which is only called by WALA. This issue is not fixed now so I haven't closed it. But I think the WALA team don't need to do anything for that.
Version: WALinuxAgent-2.1.6 Steps: 1. Prepare a VM with WALinuxAgent installed. The new user must be authenticated with ssh_key while provisioning. 2. On portal, use "reset password" to add a new user which is authenticated with password. 3. Try to use the new user to access to the VM from other hosts. Results: We can use the new user to access to the VM from other hosts. So verified.
*** This bug has been marked as a duplicate of bug 1360493 ***