Fuel for OpenStack

bvt test for 5.1 has been failed with new cinder

Bug #1370429 reported by Roman Vyalov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Library (Deprecated)
Fuel for OpenStack 6.0

Bug Description

http://jenkins-product.srt.mirantis.net:8080/job/custom.centos.bvt_1/122/

   return func(*args, **kwagrs)
  File "/home/jenkins/workspace/custom.centos.bvt_1/fuelweb_test/tests/test_neutron.py", line 259, in deploy_neutron_vlan_ha
    self.fuel_web.deploy_cluster_wait(cluster_id)
  File "/home/jenkins/workspace/custom.centos.bvt_1/fuelweb_test/models/fuel_web_client.py", line 394, in deploy_cluster_wait
    self.assert_task_success(task, interval=interval)
  File "/home/jenkins/workspace/custom.centos.bvt_1/fuelweb_test/__init__.py", line 48, in wrapped
    result = func(*args, **kwargs)
  File "/home/jenkins/workspace/custom.centos.bvt_1/fuelweb_test/models/fuel_web_client.py", line 237, in assert_task_success
    task['status'], 'ready', name=task["name"]
AssertionError: Task 'deploy' has incorrect status. error != ready

Roman Vyalov (r0mikiam)
Changed in fuel:
importance: Undecided → Critical
status: New → In Progress
assignee: nobody → Fuel QA Team (fuel-qa)
milestone: none → 5.1
status: In Progress → Confirmed
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

Deployment failed on first controller (node-1) on command execution:

bash -c "source /root/openrc ; keystone tenant-list" | grep "services" > /tmp/services returned 1 instead of one of [0]
Authorization Failed: Gateway Timeout (HTTP 504)

Trying to restart haproxy but restarting failed with:
[root@node-1 ~]# /etc/init.d/haproxy restart
Stopping haproxy: [ OK ]
Starting haproxy: [WARNING] 258/231405 (17530) : config : 'stats' statement ignored for proxy 'rabbitmq' as it requires HTTP mode.
[WARNING] 258/231405 (17530) : config : 'stats' statement ignored for proxy 'mysqld' as it requires HTTP mode.
[ALERT] 258/231405 (17530) : Starting proxy nova-metadata-api: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api-cfn: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api-cfn: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api-cloudwatch: cannot bind socket
[ALERT] 258/231405 (17530) : Starting proxy heat-api-cloudwatch: cannot bind socket
                                                           [FAILED]

So probably some problems with haproxy

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
Andrey Sledzinskiy (asledzinskiy)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Fuel Library Team (fuel-library)
Revision history for this message
Roman Vyalov (r0mikiam) wrote :

bug not reproduced after restarted job http://jenkins-product.srt.mirantis.net:8080/job/custom.centos.bvt_1/124/

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

I think we should move it to 6.0 and reduce severity because it wasn't reproduced

Changed in fuel:
milestone: 5.1 → 6.0
importance: Critical → High
Revision history for this message
Mike Scherbakov (mihgen) wrote :

After >4h of research yesterday by a few engineers by stracing & pdb'ing, we've found out the root cause of the issue lies in python-memcached. bug reported: https://bugs.launchpad.net/mos/+bug/1370324

So I'm closing this as duplicate of that bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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