Connection Failed - Qase/RobotFramework

[erickcmachado]

Hi, Team!

Can you help me with this warn, please?

I have been getting this message after start tests.

[ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x79788a5607f0>: Failed to establish a new connection: [Errno 110] Operation timed out')': /v1/environment/GSA

Environment:
qase-python-commons==3.4.1
qase-robotframework==3.4.1
robotframework==7.2.2
OperatingSystem==Linux kernel v6.1.100

[gibiw]

@erickcmachado Hi! Do you get this warning every time? The error is very similar to network problems.

[erickcmachado]

@gibiw Yes! I always get this message for 3 times and after this, the test run with PASS status, but don't list the run on the qase and show the error on the terminal:

[Qase][18:17:07][error] Exception when calling EnvironmentsApi->get_environments: HTTPSConnectionPool(host='api.qase.io', port=443): Max retries exceeded with url: /v1/environment/GSA (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x79788a500430>: Failed to establish a new connection: [Errno 110] Operation timed out'))
[Qase][18:17:07][info] Failed to initialize TestOps reporter. Using fallback.
[Qase][18:17:07][error] HTTPSConnectionPool(host='api.qase.io', port=443): Max retries exceeded with url: /v1/environment/GSA (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x79788a500430>: Failed to establish a new connection: [Errno 110] Operation timed out'))

[gibiw]

@erickcmachado Yes, it's a network issue. Check that host api.qase.io is accessible from your network.

[erickcmachado]

Ok. Thanks.!

[erickcmachado]

Hi, Team!

I reopened this thread because I have some news about this issue.

After adjusting the network proxy settings in my code, I still have the same issue.

But when I use an old version of qase-robotframework =<2.0.1 (using the .ini config file), sending results to the qase dashboard works.

On versions >=3.0.0 (using the .json config file), I get the issue indicated above.

Do you have any ideas that could help solve this problem?

[gibiw]

@erickcmachado Can you explain in more detail how you’re setting the proxy and what server address you’re specifying in the config?

[erickcmachado]

@gibiw

Yes. Here is the proxy configuration, to run alongside the browser.

*** Variables ***

${browserOptions_chrome}        add_argument("--headless");
...                             add_argument("--no-sandbox");
...                             add_argument("--disable-dev-shm-usage");
...                             add_argument("window-size=1920,1080");
...                             add_argument("--proxy-server=url_proxy:port_proxy")

[gibiw]

@erickcmachado Do you specify it in execution command? Like this:
robot --proxy-server=url_proxy:port_proxy --listener qase.robotframework.Listener .

[erickcmachado]

@gibiw

I tested with this command, but the proxy option is not recognized

[ ERROR ] option --proxyserver not recognized

Anyway, I checked the proxy configuration in my environment, with the env command, and it returned correctly.

$ env
HTTP_PROXY=http://proxy_url:proxy_port
HTTPS_PROXY=http://proxy_url:proxy_port

And finally, I ran a test (without using the listener), doing a get command on the url that is receiving timeout (api.qase.io/v1/environment/GSA) and it worked correctly, with status 200.

{
  "status": true,
  "result": {
    "total": 0,
    "filtered": 0,
    "count": 0,
    "entities": []
  }
}

But if run with --listener it returns timeout error again.

In qase.config.json, the environment value is:

"environment": "local"

[gibiw]

I think I got it. You specify a proxy server in the environment variables and after that when using the listener it stops working for you. I will try to reproduce this problem and get back to you with an answer.

[gibiw]

@erickcmachado Hi! I tested it with a random proxy server from the internet, and everything works on my side.
Can you check which address your requests are going to when using the proxy server?

[erickcmachado]

Hi @gibiw ..

The first step executed after the robot command was a get command on the url: https://api.qase.io/v1/project/GSA

Returning the error:

[ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7e5b15d606a0>: Failed to establish a new connection: [Errno 110] Operation timed out')': /v1/project/GSA

However, if you test the get without using --listener, the request works. See the code I used.

REQUEST

import requests

url = "https://api.qase.io/v1/project/GSA"

headers = {
    "accept": "application/json",
    "Token": "My_Token"
}

response = requests.get(url, headers=headers)

print(response.text)

RESPONSE

{
  "status": true,
  "result": {
    "title": "Project - Smart App",
    "code": "GSA",
    "counts": {
      "cases": 5515,
      "suites": 862,
      "milestones": 7,
      "runs": {
        "total": 200,
        "active": 0
      },
      "defects": {
        "total": 0,
        "open": 0
      }

An important point: In this same environment, sending reports works using version <=2.0.1 of the qase-robotframework.

So I think it might not be a network or proxy issue exactly, since it is working in an old version of the library, but it might be a problem in the listener after changing the configuration in .ini to .json.

Is there any way to disable this check in https://api.qase.io/v1/project/GSA after running the robot via configuration?

Because after three attempts, with timeout, the tests are executed and the report in .json is generated. It is just not sent to the dashboard due to the get and post timeout.

[erickcmachado]

Additional information: The tests are being executed in a pipeline in gitlab.

Is it mandatory to use qase-cli-tool? I saw in the documentation that it is recommended for CI/CD cases. https://developers.qase.io/docs/qase-cli