e2e: Initial e2e code

[dougsland]

$ ./run-test-e2e
[ INFO ] Starting setup
[ INFO ] ==============================
[ INFO ] Cleaning any previous e2e files
[ INFO ] Creating podman network [netcow]

[ INFO ] Preparing ASIL environment
[ INFO ] ==============================
[ INFO ] Creating container control [ASIL mode]
[ INFO ] Creating stub systemd service: container-safety in container control
[ INFO ] Creating stub systemd service: container-cruise_control in container control
[ INFO ] Creating stub systemd service: container-tires in container control
[ INFO ] Creating stub systemd service: container-breaks in container control

[ INFO ] Preparing QM environment
[ INFO ] ==============================
[ INFO ] Creating container node1 [QM mode]
[ INFO ] Creating containers radio, maps, store
[ INFO ] See: https://github.com/containers/qm/issues/32

[ INFO ] Starting tests
[ INFO ] ==============================
[ INFO ] Waiting hirte containers be ready...

[ INFO ] #1- Test scenario: hirte list all units from control to node (vise-versa)
[ INFO ] Connected to control, listing few systemd units from control
[ INFO ] Executing: podman exec control hirtectl list-units control | head -5
ID                                                                              |   ACTIVE|      SUB
====================================================================================================
dbus.socket                                                                     |   active|  running
dev-cpu-19-msr.mount                                                            |   active|  mounted
integritysetup.target                                                           |   active|   active

[ INFO ] Connected to control, listing few systemd units from node1
[ INFO ] Executing: podman exec control hirtectl list-units node1 | head -5
ID                                                                              |   ACTIVE|      SUB
====================================================================================================
sys-fs-fuse-connections.mount                                                   | inactive|     dead
systemd-machine-id-commit.service                                               | inactive|     dead
dev-cpu-4-cpuid.mount                                                           |   active|  mounted

[ INFO ] All set!

[dougsland]

before merge:

• README what need to run the e2e
• README what this e2e script executes and tests?
• README: document the env variables that change the behaviour of script:NUMBER_OF_NODES, TAG_CONTROL_MACHINE, NET_INTERFACE_IP_CONTROL, TAG_NODE_MACHINE
• SCRIPT: finish QM setup and trigger the containers (see QM issue centos9: qm.te:3:ERROR 'syntax error' at token 'container_use_ptys' on line 3613: #line 3 #32)
• cosmetic: shellcheck in the code
• feedback from others devs

future:

• open an issue to support fedora (other distros?) in e2e, today uses centos9
• share the e2e with hirte project? (we use hirte a bunch here)

/cc @rhatdan for review

[dougsland]

/hold

[lsm5]

Not a review, just a note: it would be great to integrate these tests with Packit and TMT (https://packit.dev/docs/testing-farm/) . Doesn't have to be in this PR, and fwiw, we don't have e2e testing with packit complete in any of our repos yet.

[dougsland]

Not a review, just a note: it would be great to integrate these tests with Packit and TMT (https://packit.dev/docs/testing
-farm/) . Doesn't have to be in this PR, and fwiw, we don't have e2e testing with packit complete in any of our repos yet.

Thanks @lsm5. Indeed, it will require a different github issue (as soon we merge) as I will need to research the tool to start using it.

[rhatdan]

@dougsland Still a WIP?

[lsm5]

Not a review, just a note: it would be great to integrate these tests with Packit and TMT (https://packit.dev/docs/testing
-farm/) . Doesn't have to be in this PR, and fwiw, we don't have e2e testing with packit complete in any of our repos yet.

Thanks @lsm5. Indeed, it will require a different github issue (as soon we merge) as I will need to research the tool to start using it.

containers/container-selinux#230 might be of some use. It's not merged yet and actually running those tests does cause out of disk space issues on the testing env, that I have yet to check on. TMT does allow specifying hardware configuration, but I haven't yet gotten it to work successfully: https://tmt.readthedocs.io/en/stable/spec/hardware.html#disk

[dougsland]

@dougsland Still a WIP?

@rhatdan almost there, we need a README and a fresh test "tomorrow". As today I got surprised with some changes in the new rpm.

[dougsland]

read for the review @rhatdan @lsm5

[lsm5]

Could you please also add in the commit message how to actually run the test (which dir to run from), as root / non-root etc?

[lsm5]

Could you please also add in the commit message how to actually run the test (which dir to run from), as root / non-root etc?

and also in the README

[rhatdan]

Cleanup @lsm5 issues, and then we can merge. We need to get this test to run on PRs.

[lsm5]

I think if we need something running quickly, github actions might be the way, although I don't think it's easy to provision anything other than Ubuntu over there. Packit + TMT might be the way to go long-term.

[dougsland]

Could you please also add in the commit message how to actually run the test (which dir to run from), as root / non-root
etc?

Just run ./run-e2e-test in the dir. There is a asciicinema embedded in the README that show as 'video' how to run it.

[dougsland]

Could you please also add in the commit message how to actually run the test (which dir to run from), as root / non-root etc?

The script will warn if user try to run as non root.

[dougsland]

@rhatdan @lsm5 here how the HTML will look like when README.md is merged: https://github.com/dougsland/qm/tree/e2e/tests/e2e

[lsm5]

LGTM