Bug 1396421 - 503 errors raised during api authentication calls against openstack rais "unauthorised user/password " combination rather than report the 503
Summary: 503 errors raised during api authentication calls against openstack rais "una...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Greg Blomquist
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 09:45 UTC by Felix Dewaleyne
Modified: 2021-09-09 12:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-18 09:55:00 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Felix Dewaleyne 2016-11-18 09:45:08 UTC
Description of problem:
503 errors raised during api authentication calls against openstack raise "unauthorised user/password " combination rather than report the 503

Version-Release number of selected component (if applicable):
5.5.5.4

How reproducible:
all the time in customer environment

Steps to Reproduce:
1. openstack must return a 503 error when attempting to uise its API
2. leave cloudforms to collect metering information
3.

Actual results:

[----] D, [2016-11-16T08:39:18.803982 #14112:e01988] DEBUG -- : Role Authorization successful for: userid [admin], role id [3000000000001], feature identifier [ems_cloud_edit]
[----] D, [2016-11-16T08:39:18.808586 #14112:e01988] DEBUG -- : MIQ(Rbac.search) Find options: {:conditions=>"(ext_management_systems.id = '3000000000001')", :include=>{}, :order=>nil, :limit=>nil, :offset=>nil}
[----] I, [2016-11-16T08:39:18.813117 #14112:e01988]  INFO -- : MIQ(ManageIQ::Providers::Openstack::CloudManager#with_provider_connection) Connecting through ManageIQ::Providers::Openstack::CloudManager: [ES_TC1_OpenStack_PR]
[fog][WARNING] Unrecognized arguments: auth_type
[----] E, [2016-11-16T08:39:18.846247 #14112:e01988] ERROR -- : <Fog> excon.error     #<Excon::Error::ServiceUnavailable: Expected([200, 204]) <=> Actual(503 Service Unavailable)
excon.error.response
  :body          => "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  :cookies       => [
  ]
  :headers       => {
    "Cache-Control" => "no-cache"
    "Connection"    => "close"
    "Content-Type"  => "text/html"
  }
  :host          => "thistextwasreplaced"
  :local_address => "10.11.12.13"
  :local_port    => 40872
  :path          => "/v2.0/tokens"
  :port          => 443
  :reason_phrase => "Service Unavailable"
  :remote_ip     => "10.48.14.50"
  :status        => 503
  :status_line   => "HTTP/1.0 503 Service Unavailable\r\n"
>

[----] E, [2016-11-16T08:39:18.846365 #14112:e01988] ERROR -- : MIQ(ManageIQ::Providers::Openstack::CloudManager#verify_api_credentials) Error Class=Excon::Error::ServiceUnavailable, Message=Expected([200, 204]) <=> Actual(503 Service Unavailable)
excon.error.response
  :body          => "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  :cookies       => [
  ]
  :headers       => {
    "Cache-Control" => "no-cache"
    "Connection"    => "close"
    "Content-Type"  => "text/html"
  }
  :host          => "thistextwasreplaced"
  :local_address => "10.11.12.13"
  :local_port    => 40872
  :path          => "/v2.0/tokens"
  :port          => 443
  :reason_phrase => "Service Unavailable"
  :remote_ip     => "10.48.14.50"
  :status        => 503
  :status_line   => "HTTP/1.0 503 Service Unavailable\r\n"

[----] W, [2016-11-16T08:39:18.846412 #14112:e01988]  WARN -- : MIQ(ManageIQ::Providers::Openstack::CloudManager#authentication_check_no_validation) type: ["default"] for [3000000000001] [ES_TC1_OpenStack_PR] Validation failed: invalid, L
ogin failed due to a bad username or password.
[----] W, [2016-11-16T08:39:18.846540 #14112:e01988]  WARN -- : MIQ(AuthUseridPassword#validation_failed) [ExtManagementSystem] [3000000000001], previously valid on: , previous status: [Invalid]
[----] I, [2016-11-16T08:39:18.855569 #14112:e01988]  INFO -- : MIQ(MiqQueue.put) Message id: [3000000076345],  id: [], Zone: [default], Role: [], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqEve
nt.raise_evm_event], Timeout: [600], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: [["ManageIQ::Providers::Openstack::CloudManager", 3000000000001], "ems_auth_invalid", {}]
[----] E, [2016-11-16T08:39:18.855674 #14112:e01988] ERROR -- : MIQ(ems_cloud_controller-update): Credential validation was not successful: Login failed due to a bad username or password.
[----] I, [2016-11-16T08:39:20.288462 #13884:f31998]  INFO -- : MIQ(MiqServer#populate_queue_messages) Fetched 1 miq_queue rows for queue_name=generic, wcount=4, priority=200
[----] I, [2016-11-16T08:39:20.589728 #14109:e6198c]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 2.
[----] I, [2016-11-16T08:39:20.594744 #14109:e6198c]  INFO -- : MIQ(MiqQueue.put) Message id: [3000000076346],  id: [], Zone: [default], Role: [], Server: [70ac2014-a50d-11e6-9a9b-001a4afb3c76], Ident: [generic], Target id: [], Instance i
d: [], Task id: [], Command: [Session.check_session_timeout], Timeout: [600], Priority: [90], State: [ready], Deliver On: [], Data: [], Args: []
[----] I, [2016-11-16T08:39:22.759317 #14091:365998]  INFO -- : MIQ(MiqGenericWorker::Runner#get_message_via_drb) Message id: [3000000076345], MiqWorker id: [3000000000018], Zone: [default], Role: [], Server: [], Ident: [generic], Target
id: [], Instance id: [], Task id: [], Command: [MiqEvent.raise_evm_event], Timeout: [600], Priority: [100], State: [dequeue], Deliver On: [], Data: [], Args: [["ManageIQ::Providers::Openstack::CloudManager", 3000000000001], "ems_auth_inva
lid", {}], Dequeued in: [3.90664837] seconds

Expected results:
a 503 error is raised instead of an authentication error

Additional info:
only debug level info allows to properly diagnose the error


Note You need to log in before you can comment on or make changes to this bug.