redhat-sp-security / tests Goto Github PK

currently the following tests are affected:

• rsyslog/Sanity/ommail-module-test

We should create an option that allows installing dowstream image to catalogue in OpenShift for tang-operator Test Suite. It should be environment variable based, as the rest of the existing ones.

README.md should be included under tang-operator test suite indicating the new repository

A mechanism to include malware detection should be included in the tang-operator Test Suite.

It should:

• Check if podman / docker exist
• Check if clamav is installed
• Mount both container and container bundle in different directories
• Check both directories with clamscan
• Report issues and keep them if issues are found

Tang operator functional test is testing tang server availability, but not a real clevis<->tang test. A clevis test should be added to check that, apart from server running correctly, the whole decryption process work

tang-operator: timeout is expiring for PODs to go to Running state:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   Scale-out scalability test
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 16:13:46 ] :: [   PASS   ] :: Creating scale out test [0] (Expected 0, got 0)
:: [ 16:13:47 ] :: [   PASS   ] :: Checking 1 POD is started [Timeout=120 secs.] (Expected 0, got 0)
:: [ 16:13:47 ] :: [   PASS   ] :: Checking 1 Service is started [Timeout=120 secs.] (Expected 0, got 0)
:: [ 16:13:48 ] :: [   PASS   ] :: Checking pod name not empty (Assert: "tangdeployment-tangserver-scaleout-6b6455fb5b-wn9c4" should not equal "")
:: [ 16:13:58 ] :: [   PASS   ] :: Checking POD in Running state [Timeout=120 secs.] (Expected 0, got 0)
:: [ 16:13:59 ] :: [   PASS   ] :: Creating scale out test [1] (Expected 0, got 0)
:: [ 16:14:00 ] :: [   PASS   ] :: Checking 1+1 PODs are started [Timeout=120 secs.] (Expected 0, got 0)
:: [ 16:14:00 ] :: [   PASS   ] :: Checking pod name not empty (Assert: "tangdeployment-tangserver-scaleout-6b6455fb5b-wzprb" should not equal "")
:: [ 16:16:56 ] :: [   FAIL   ] :: Checking added POD in Running state [Timeout=120 secs.] (Expected 0, got 1)
:: [ 16:18:07 ] :: [   PASS   ] :: Deleting scale out test (Expected 0, got 0)
:: [ 16:18:08 ] :: [   PASS   ] :: Checking no PODs continue running [Timeout=5 secs.] (Expected 0, got 0)
:: [ 16:18:08 ] :: [   PASS   ] :: Checking no Services continue running [Timeout=120 secs.] (Expected 0, got 0)
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

This needs to be investigated, to check if it is a ROSA specific issue, as this timeout has been enough on the rest of the platforms

Many rsyslog test cases need to have certificates created in order to execute the test. In all cases, certificates are created manually at the beginning of each test. I understand that sometimes different types of certificates are required or certificates must be chained but this could be configured.

Consequently, I suggest to implement some kind of a wrapper, which will automatically create desired certificates when invoked. With this approach, tests will be more clean.

What do you think? @sopos @sarroutbi

Failed to load packit config file:

Cannot parse package config: PackitConfigException('Spec file was not found!').

For more info, please check out the documentation: https://packit.dev/packit-as-a-service/ or contact us - Packit team