qm
qm copied to clipboard
QM is a containerized environment for running Functional Safety qm (Quality Management) software
As soon a new patch arrives for review, we need to trigger a test to make sure QM is executing well the **nested container via podman**. The example below are...
See: https://github.com/containers/qm/tree/main/tests/e2e/tools/FFI/sysctl
qm.container contain multiple definitions that explain what QM is behind the scenes. Explore this file a bit in the README.md.
Show integration possibilities like [simple-images](https://gitlab.com/CentOS/automotive/sample-images) project and simple way like copying files over /usr/share/qm/rootfs.
Use the tool provided via #376 to create a test plan integrated to FFI-tools (https://gitlab.com/CentOS/automotive/container-images/ffi-tools). See-Also: #376 #375
Here the test scenario using CentOS Automotive VM via qemu: ``` git clone https://gitlab.com/CentOS/automotive/sample-images cd sample-images/osbuild-manifests sudo make cs9-qemu-qmcontainer-regular.x86_64.qcow2 ./runvm --nographics ./cs9-qemu-qmcontainer-regular.x86_64.qcow2 ``` **Please note**. =============. default values can be...
This test case should test inside QM the command `setenforce 0` which must fail ``` bash-5.1# setenforce 0 setenforce: security_setenforce() failed: Permission denied ```
Basically, inside QM sched_setscheduler() syscall is not allowed and we should prove it. Transform the below steps into a test plan. Steps: 1- Build source code: `gcc -o test_sched_setscheduler test_sched_setscheduler.c`...
> > > As a first step, maybe it's worth switching Packit copr tasks to use the automotive-sig coprs in https://github.com/containers/qm/blob/main/.packit.yaml . Currently, it uses `rhcontainerbot/packit-builds` and `rhcontainerbot/qm` coprs. >...
Set existing tier-0 test run against ffi setup, Rename old tier-0 test. it does not fit to AutoSD QM. Both tests should run in CI tests New tier-0 will run...