Bug 1643982 - The validator passes although the tasks fail
Summary: The validator passes although the tasks fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 14.0 (Rocky)
Assignee: Gaël Chamoulaud
QA Contact: Andrey Fiodorov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-29 16:42 UTC by Andrey Fiodorov
Modified: 2019-01-11 11:54 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-validations-9.3.1-0.20181008110754.4064fb7.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:54:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 616886 0 None None None 2018-11-09 11:38:23 UTC
OpenStack gerrit 618986 0 None None None 2018-11-20 10:55:32 UTC
OpenStack gerrit 620085 0 None None None 2018-11-26 15:32:17 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:40 UTC

Description Andrey Fiodorov 2018-10-29 16:42:42 UTC
Description of problem:
The validation "Check the number of OpenStack processes on undercloud" passes although all tasks fail.

Version-Release number of selected component (if applicable):
openstack-tripleo-validations-9.3.1-0.20181008110747.4064fb7.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install OSP14 from 2018-10-19.1
2. Go to GUI and run the validation "Check the number of OpenStack processes on undercloud"

Actual results:
The tasks fail and validation passes

Expected results:
If the tasks fail the validator should fails also.

Additional info:
Output from this validation in the GUI:

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c heat-engine` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c ironic-inspector` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c ironic-conductor` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c nova-api` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c nova-scheduler` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c nova-conductor` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c nova-compute` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c glance-api` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c swift-proxy-server` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c swift-object-server` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c swift-container-server` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `pgrep -f -c zaqar-server` exited with code: 1: non-zero return code

stdout:
    0

Success! The validation passed for all hosts:
* undercloud

Comment 1 Gaël Chamoulaud 2018-11-09 11:44:04 UTC
Andrey, I did provide a patch to fix the undecloud-process-count which will execute the 'pgrep' command  inside the appropriate container and not on the undercloud itself anymore.

But this validation will always succeed with warnings for the following reason [1].

[1] - https://github.com/openstack/tripleo-validations/commit/02000cccffd962658d885bf1018212281ba79c3a

Comment 16 Udi Kalifon 2018-11-22 13:12:33 UTC
The command is now running in the container as appropriate, but it seems like the same failures persist:

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `docker exec mistral_api pgrep -f -c mistral-api` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `docker exec mistral_engine pgrep -f -c mistral-engine` exited with code: 1: non-zero return code

stdout:
    0

Task 'Collect the number of running processes per OpenStack service' failed:
Host: undercloud
Message: Command `docker exec nova_api pgrep -f -c nova-api` exited with code: 1: non-zero return code

stdout:
    0

Success! The validation passed for all hosts:
* undercloud

Comment 19 Andrey Fiodorov 2018-12-04 06:44:20 UTC
The validator passes.
Verified on version:
(undercloud) [stack@undercloud-0 ~]$ rpm -q openstack-tripleo-validations
openstack-tripleo-validations-9.3.1-0.20181008110754.4064fb7.el7ost.noarch

Comment 23 errata-xmlrpc 2019-01-11 11:54:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045


Note You need to log in before you can comment on or make changes to this bug.