Closed agrare closed 8 months ago
When verifying an openstack provider the task which gets queued has no zone parameter and thus is not reliably run by the proper appliance
INFO -- evm: MIQ(MiqQueue.put) Message id: [5573], Zone: [], Role: [ems_operations], Server: [], MiqTask id: [31], Handler id: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [ManageIQ::Providers::Openstack::CloudManager.verify_credentials?], Timeout: [600], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: [{"endpoints"=>{"default"=>{"security_protocol"=>"ssl-no-validation", "hostname"=>"openstack.rb.nj.grare.com", "port"=>"5000"}}, "authentications"=>{"default"=>{"userid"=>"admin", "password"=>"********"}}, "event_stream_selection"=>"none", "name"=>"microstack", "type"=>"ManageIQ::Providers::Openstack::CloudManager", "api_version"=>"v3", "uid_ems"=>"default", :task_id=>31}]
Specifically you can see Zone: []
Zone: []
The API payload does not have a zone_id either so I suspect this is an issue at some level with either the UI or the provider params_for_create
params_for_create
[----] I, [2024-01-19T15:46:03.110093#109922:63bf0] INFO -- api: MIQ(Api::ProvidersController.log_request) Parameters: {"action"=>"update", "controller"=>"api/providers", "format"=>"json", "body"=>{"action"=>"verify_credentials", "resource"=>{"endpoints"=>{"default"=>{"security_protocol"=>"ssl-no-validation", "hostname"=>"openstack.rb.nj.grare.com", "port"=>"5000"}}, "authentications"=>{"default"=>{"userid"=>"admin", "password"=>"[FILTERED]"}}, "event_stream_selection"=>"none", "name"=>"microstack", "type"=>"ManageIQ::Providers::Openstack::CloudManager", "api_version"=>"v3", "uid_ems"=>"default"}}, "request_id"=>"f6e07997-0b5e-411b-8009-5f1dea87cf31", "session_id"=>"dc6d1a2a829118eaf4dc5b3fda8905eb"}
NOTE I tried the same with a VMware provide and do not see this issue.
Duplicate of https://github.com/ManageIQ/manageiq/issues/22845
When verifying an openstack provider the task which gets queued has no zone parameter and thus is not reliably run by the proper appliance
Specifically you can see
Zone: []
The API payload does not have a zone_id either so I suspect this is an issue at some level with either the UI or the provider
params_for_create
NOTE I tried the same with a VMware provide and do not see this issue.