Connection refused during creation openstack_tennant

Bug #1518952 reported by Vasily Gorin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Andrey Sledzinskiy

Bug Description

CI: https://product-ci.infra.mirantis.net/job/8.0.system_test.ubuntu.thread_3/50/testReport/(root)/check_openstack_stat/check_openstack_stat/

Scenario:
            1. Create cluster
            2. Add 3 nodes with controller and ceph OSD roles
            3. Add 1 node with ceph OSD roles
            4. Add 2 nodes with compute and ceph OSD roles
            5. Deploy the cluster
             6. create instance
             7. create flavor
             8. create volume
             9. create image
             10. create tenant and user

All steps was executed by systets.
Tenant is created using 'tenant = os_conn.create_tenant("openstack_tenant")'

Actual result:

      Error Message : ConnectionRefused: Unable to establish connection to http://10.109.17.2:35357/v2.0/tenants

tags: added: swarm-blocker
Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
status: New → Confirmed
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Fuel Library Team (fuel-library)
tags: added: area-library
removed: area-python
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

ISO number? Did you retry again after 2 minutes? Did you run OSTF?

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Vasily Gorin (vgorin) wrote :

ISO number is 195. I didn't try to do it after 2 minutes. This bug was reproduced on CI.

Revision history for this message
Vasily Gorin (vgorin) wrote :

In other runs it reproduced with following message in exception:
 ConnectionRefused: Unable to establish connection to http://10.109.17.2:35357/v2.0/tenants

Changed in fuel:
status: Incomplete → Confirmed
Revision history for this message
Vasily Gorin (vgorin) wrote :
Revision history for this message
Vasily Gorin (vgorin) wrote :
Revision history for this message
Kyrylo Galanov (kgalanov) wrote :

Anyway, CI fails each time. I'll take a look.

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Kyrylo Galanov (kgalanov)
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Kyrylo Galanov (kgalanov) wrote :

Hi,

Log https://product-ci.infra.mirantis.net/job/8.0.system_test.ubuntu.thread_3/59/console

The test fails because haproxy sends a request to node-6 which was just stopped. Consequently, request fails by timeout.
Take a look at haproxy conf file: http://paste.openstack.org/show/480664/

I would suggest to put a timeout in the test in order to wait until haproxy detects and detaches the failed node.
Insert 45 seconds timeout here: https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/tests/tests_strength/test_restart.py#L131

Best regards,
Kyrylo

Changed in fuel:
assignee: Kyrylo Galanov (kgalanov) → Fuel QA Team (fuel-qa)
tags: added: area-qa
removed: area-library
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

You mentioned wrong test, this issue has nothing to do with https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/tests/tests_strength/test_restart.py#L131 .

This test is - https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/tests/test_ceph.py#L339 .

We don't have any kind of failover in that test and all nodes should be online

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Andrey Sledzinskiy (asledzinskiy)
status: In Progress → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (master)

Fix proposed to branch: master
Review: https://review.openstack.org/253564

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (master)

Reviewed: https://review.openstack.org/253564
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=1d14aafa2454b5bb615d1ffeca95e74547415636
Submitter: Jenkins
Branch: master

commit 1d14aafa2454b5bb615d1ffeca95e74547415636
Author: asledzinskiy <email address hidden>
Date: Fri Dec 4 17:54:45 2015 +0200

    Untag management and storage networks

    - Untag management and storage networks because management net
    is not available from the host

    Change-Id: Id6b19dbec15ed908cfea235ed51cc7334da3c7b0
    Closes-Bug: #1518952

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.