Working with support to suggest that customer change the puma configuration settings to see if it resolves the connection refused error.

Created attachment 1200554 [details]
bz_1375308_pr_10445 hot fix

We believe the customer issue is caused by setting
the root object ecloud_client attribute(object) in the authenticate
method.

root value:
ecloud_client: #<Fog::Compute::Ecloud::Real:0x000000012ce4e8>

Each automate method runs in its own process, so the ecloud_client
object should be set in the method where it's used.

The customer is currently using 3 states in the provisioning state machine:
1. authenticate (customizerequest)
2. object_walker (registerAD)
3. get_vm(provision)

The authenticate method sets this root object attribute which is
causing the error:
 $evm.root['ecloud_client'] = Fog::Compute::Ecloud.new ecloud_options

We see this code in the get_vm method:
 #client = Fog::Compute::Ecloud.new ecloud_options
  ecloud_client = $evm.root['ecloud_client']

Can you ask the customer to remove the setting of root ecloud_client
attribute in the authenticate method and instead set it in the get_vm
method?

My understanding is that the customer issue has been resolved with the changes described above.

Hi Josh,

Can we close this ticket?

Thanks,
Tina