[qa] RabbitMQ automated tests should be updated

Bug #1580193 reported by Timur Nurlygayanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
High
Alexey Galkin
9.x
Confirmed
High
Alexey Galkin

Bug Description

We need to update automated tests for RabbitMQ, here are the fixes for master branch of MOS integration tests:

https://review.gerrithub.io/275968
https://review.gerrithub.io/#/c/275970/

Steps To Reproduce:
1. Run MOS integration tests for RabbitMQ

Observed Result:
7 tests will fail, example of the report:
https://mirantis.testrail.com/index.php?/runs/view/10422&group_by=cases:section_id&group_order=asc&group_id=23588

Expected Result:
All tests will pass

Tags: area-qa
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :
description: updated
Changed in mos:
importance: Undecided → High
assignee: nobody → Alexey Galkin (agalkin)
tags: added: area-qa
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Let's wait for the next test run to verify that fixes work fine.

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Tests failed again with another issue:

https://mirantis.testrail.com/index.php?/runs/view/10516&group_by=cases:section_id&group_order=asc&group_id=23588

self = <mos_tests.environment.ssh.SSHClient object at 0x7f7715e4b910> [10.109.2.4:22]
command = 'pcs resource --wait=60 disable p_rabbitmq-server;pcs resource --wait=60 enable p_rabbitmq-server'
verbose = True

    def check_call(self, command, verbose=True):
        ret = self.execute(command, verbose)
        if ret['exit_code'] != 0:
            raise CalledProcessError(command, ret['exit_code'],
> ret['stdout'] + ret['stderr'])
E CalledProcessError: Command 'pcs resource --wait=60 disable p_rabbitmq-server;pcs resource --wait=60 enable p_rabbitmq-server' returned non-zero exit status 1
E ["Resource 'p_rabbitmq-server' is not running on any node\n", 'Error: waiting timeout\n', "Resource 'p_rabbitmq-server' is master on node node-1.test.domain.local.\n", '\n', 'Pending actions:\n', '\tAction 270: p_rabbitmq-server:2_post_notify_start_0\ton node-2.test.domain.local\n', '\tAction 269: p_rabbitmq-server:1_post_notify_start_0\ton node-3.test.domain.local\n', '\tAction 268: p_rabbitmq-server:0_post_notify_start_0\ton node-1.test.domain.local\n', '\tAction 267: p_rabbitmq-server:0_pre_notify_start_0\ton node-1.test.domain.local\n', '\tAction 129: p_rabbitmq-server:2_monitor_35000\ton node-2.test.domain.local\n', '\tAction 128: p_rabbitmq-server:2_monitor_30000\ton node-2.test.domain.local\n', '\tAction 127: p_rabbitmq-server:2_start_0\ton node-2.test.domain.local\n', '\tAction 126: p_rabbitmq-server:1_monitor_35000\ton node-3.test.domain.local\n', '\tAction 125: p_rabbitmq-server:1_monitor_30000\ton node-3.test.domain.local\n', '\tAction 124: p_rabbitmq-server:1_start_0\ton node-3.test.domain.local\n', 'Error performing operation: Timer expired\n']

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.