Project

General

Profile

Actions

Bug #13497

closed

InvalidLogin: Cannot complete login due to an incorrect user" when trying to provision a new host

Added by Amit Yitzhaki over 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources
Target version:
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

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 2 (0 open2 closed)

Related to Foreman - Bug #24545: Compute resource test connection enables password fieldClosedMarek HulánActions
Has duplicate Foreman - Bug #17218: Compute Resource password field reverts to "old" password after pressing Test ConnectionDuplicate11/04/2016Actions
Actions #1

Updated by Dominic Cleal over 8 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.

Actions #2

Updated by Shlomi Zadok over 8 years ago

Weirdly, this is happening on the following sequence for me:
  • 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.

Actions #3

Updated by Ondřej Pražák over 7 years ago

  • Bugzilla link set to 1389810
Actions #4

Updated by Ondřej Pražák over 7 years ago

  • Has duplicate Bug #17218: Compute Resource password field reverts to "old" password after pressing Test Connection added
Actions #5

Updated by Marek Hulán over 6 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.

Actions #6

Updated by Tomer Brisker over 6 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.

Actions #7

Updated by The Foreman Bot over 6 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5163 added
Actions #8

Updated by Anonymous over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Tomer Brisker over 6 years ago

  • translation missing: en.field_release set to 330
Actions #10

Updated by Marek Hulán almost 6 years ago

  • Related to Bug #24545: Compute resource test connection enables password field added
Actions

Also available in: Atom PDF