manageiq icon indicating copy to clipboard operation
manageiq copied to clipboard

Openstack cloud provider Error::Timeout, Message=connect_write timeout reached

Open cronosy opened this issue 2 years ago • 8 comments

Greetings team. I'm trying add a red hat openstack provider 16.2 in my new manageiq oparin version. However, the addition fail with error Error::Timeout, Message=connect_write timeout reached. Already I check the connectivity from manageiq to horizon, requesting a token using the curl command with the same user, region and domain filled up in manageiq form bellow the curl response:

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 8177 100 7936 100 241 15030 456 --:--:-- --:--:-- --:--:-- 15486 gAAAAABkZ6UkFlgzGQXPbjbFfWBiS2WvkQ7U67zQthtQqNk2OWb9vO03MHJCf9qhoOO.......

thanks for your help.

cronosy avatar May 19 '23 16:05 cronosy

@cronosy When adding the cloud provider using the form, are you able to validate with your keystone credentials?

nasark avatar May 24 '23 18:05 nasark

Hi @nasark, when I adding the provider, I complete the form but when I make click on validate, these operation failed with time out. I add the same user that I use in horizon and curl command. Let me add that I'm using the image for red hat virtualization(qc2). I tried with two different providers, in two different locations with the same issue.

cronosy avatar May 29 '23 20:05 cronosy

@cronosy I am not able to reproduce this on oparin with the openstack 2023.1 Antelope release.

For the following fields, please ensure you are using the port used for your Keystone service as well as the admin user and password (not sure if this is the same as what you are using on horizon). Also please ensure that your Nova (Compute) service is up and running as Keystone is used to check Nova during the validation step for cloud providers. Screenshot 2023-05-30 at 3 22 49 PM

If you could provide a snippet of the logs with a stack trace that would make it easier to debug. Thanks

nasark avatar May 30 '23 19:05 nasark

Greetings. After evaluating the architecture and follow tcpdumps, I could identify a couple situations. First, when I connect to my openstack using a public IP to horizon appear a request to 13774 port. I couldn't identify this port but once opened the validation end successful. Now the second behavior belongs a TCP reassembled when I'm trying add the provider through the VPN connection. Apparently, this reassemble affect the application transfer between manageiq and openstack and the credential validation finish with "login attempt time out" I can't share a complete tcpdump but I would like if anyone could replicate the topology.

kind regards.

cronosy avatar Jun 02 '23 00:06 cronosy

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

miq-bot avatar Sep 04 '23 00:09 miq-bot

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot avatar Dec 11 '23 00:12 miq-bot

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot avatar Mar 18 '24 00:03 miq-bot

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot avatar Jun 24 '24 00:06 miq-bot

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot avatar Sep 30 '24 00:09 miq-bot