Bug #13497
closedInvalidLogin: 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
Updated by Dominic Cleal almost 9 years ago
- 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.
Updated by Shlomi Zadok almost 9 years ago
- 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.
Updated by Ondřej Pražák about 8 years ago
- Has duplicate Bug #17218: Compute Resource password field reverts to "old" password after pressing Test Connection added
Updated by Marek Hulán over 7 years ago
- Status changed from New to Resolved
I can no longer reproduce on 1.17 develop branch. Please reopen if you still encounter the issue.
Updated by Tomer Brisker about 7 years ago
- Category changed from Compute resources - VMware to Compute resources
- Status changed from Resolved to Assigned
- Assignee set to Tomer Brisker
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.
Updated by The Foreman Bot about 7 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5163 added
Updated by Anonymous about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 10b2c0f684c309c181190c7a752529bda4359876.
Updated by Tomer Brisker about 7 years ago
- Translation missing: en.field_release set to 330
Updated by Marek Hulán over 6 years ago
- Related to Bug #24545: Compute resource test connection enables password field added