Fuel system tests for sahara are broken in Juno

Bug #1388775 reported by Aleksandr Didenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Aleksandr Didenko
6.0.x
Fix Released
High
Aleksandr Didenko

Bug Description

http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom.ubuntu.bvt_2/262/console

AssertionError: sahara-api count not equal to 1

It looks like since Juno there should be 'sahara-all' process instead of 'sahara-api'. Here is what I see in custom.ubuntu.bvt_2/262 diagnostic snapshot for node-3:

#process list (sahara-all pid is 29265):
sahara 29265 0.3 1.2 251152 79092 ? S 17:33 0:00 /usr/bin/python /usr/bin/sahara-all --config-file /etc/sahara/sahara.conf

# netstat for sahara-all pid:
tcp 0 0 0.0.0.0:8386 0.0.0.0:* LISTEN 29265/python
tcp 0 0 10.108.22.3:53167 10.108.22.3:3306 ESTABLISHED 29265/python
udp 0 0 0.0.0.0:54515 0.0.0.0:* 29265/python

So 'sahara-all' is up and running and it listens on 8386 port. It looks like we should update our system tests to check for 'sahara-all' process instead of 'sahara-api'.

Tags: system-tests
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

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

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

Reviewed: https://review.openstack.org/132532
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=9012d6252d23f56a244142e5341bdcb2fc1ce5ef
Submitter: Jenkins
Branch: master

commit 9012d6252d23f56a244142e5341bdcb2fc1ce5ef
Author: Aleksandr Didenko <email address hidden>
Date: Mon Nov 3 12:28:00 2014 +0200

    Check for 'sahara-all' instead of 'sahara-api'

    Since Juno we should check for 'sahara-all' in system tests.

    Change-Id: I5c80aaaf87fc7a2d474619c90598a9b68b37edbe
    Closes-bug: #1388775

Changed in fuel:
status: In Progress → Fix Committed
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.