Bug #13497
InvalidLogin: Cannot complete login due to an incorrect user" when trying to provision a new host
Description
We are having for some time this problem and it is not even consistent. We can work for few days without any issue and all of the sudden, "InvalidLogin: Cannot complete login due to an incorrect user" when trying to provision a new host.
Logging into vsphere manually works fine.
this is the error message
016-01-31 05:06:18 [I] Rendered text template (0.0ms)
2016-01-31 05:06:18 [I] Completed 200 OK in 170ms (Views: 0.6ms | ActiveRecord: 14.7ms)
2016-01-31 05:06:18 [W] Failed to destroy a compute tlvvc01 (VMware) instance testvm : InvalidLogin: Cannot complete login due to an incorrect user name or password./opt/rh/ruby193/root/usr/share/gems/gems/fog-1.29.0/lib/fog/vsphere/compute.rb:443:in `rescue in authenticate'
/opt/rh/ruby193/root/usr/share/gems/gems/fog-1.29.0/lib/fog/vsphere/compute.rb:439:in `authenticate'
1. Did any of you encounter this in foreman?
2. Does foreman connect to the LDAP or locally for VMWARE?
Thanks,
Amit
Related issues
Associated revisions
History
#1
Updated by Dominic Cleal about 7 years ago
Updated by - Category changed from VM management to Compute resources - VMware
- Assignee deleted (
Shlomi Zadok) - Priority changed from High to Normal
Foreman only connects to vSphere for authentication, sounds like the error is raised from it, not Foreman.
#2
Updated by Shlomi Zadok about 7 years ago
Updated by - Edit vmware compute resource, Change the username and / or password.
- Click on "Load datacenters"
- Save
On save, the new credentials (password specifically) are not sent.
Workaround (until fixed):- Edit
- Set new username / password.
- Do not click on "load datacenters"
- Save
new credentials are saved.
#3
Updated by Ondřej Pražák over 6 years ago
Updated by - Bugzilla link set to 1389810
#4
Updated by Ondřej Pražák over 6 years ago
- Has duplicate Bug #17218: Compute Resource password field reverts to "old" password after pressing Test Connection added
#5
Updated by Marek Hulán over 5 years ago
Updated by - Status changed from New to Resolved
I can no longer reproduce on 1.17 develop branch. Please reopen if you still encounter the issue.
#6
Updated by Tomer Brisker about 5 years ago
Updated by - Assignee set to Tomer Brisker
- Status changed from Resolved to Assigned
- Category changed from Compute resources - VMware to Compute resources
This is still an issue in all compute resources that have a password field. When pressing test connection, the password field becomes disabled, leading to previous password being preserved in the database.
#7
Updated by The Foreman Bot about 5 years ago
Updated by - Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5163 added
#8
Updated by Anonymous about 5 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 10b2c0f684c309c181190c7a752529bda4359876.
#9
Updated by Tomer Brisker about 5 years ago
- Legacy Backlogs Release (now unused) set to 330
#10
Updated by Marek Hulán over 4 years ago
- Related to Bug #24545: Compute resource test connection enables password field added
Fixes #13497 - Enable password field after test connection in CR (#5163)
When clicking test connection button (or load datacenters) on an
existing compute resource, the password field is disabled. If the
password was changed prior to testing the connection and then the form
is saved, this will cause the new password to not be transmitted to the
server, leading to the previous password remaining in the database.