Investigating whether skupper-ansible respects until/retries keywords.
Danilo Hashimoto hash-d
https://github.com/skupperproject/skupper-ansible/issues/82
To run the test:
ansible-playbook -i SOME_IP, ./main.yaml -e skupper_platform=linux -vv
ansible-playbook -i SOME_IP, ./main.yaml -e skupper_platform=podman -vv -e link_access=default
skupperproject/skupper-ansible#81
Note that the test has listener and container on the same namespace with the same routingKey. The intention is simply to have the listener match so it opens the port.
To run the test:
ansible-playbook -i SOME_IP, ./main.yaml -e skupper_platform=podman -vv
skupperproject/skupper-ansible#80
This test creates a site and starts it, before adding a Listener and a Connector and reloading the site.
Next, it checks the consequence of the creation of the Listener: port 8082 should be opened.
It works fine for platforms podman and docker, but it fails for linux. And that's because the process is never restarted on systemd.
skupperproject/skupper-ansible#79
On this test, there is a Listener named asdf-Listener.
That name, containing an uppercase letter, is considered invalid by is_valid_name() on plugins/module_utils/args.py.
There is a series of tests on dump() at plugins/module_utils/resource.py which will simply continue in case of unexpected conditions, some of which use is_valid_name().
Reproducer for skupper-router #864
skupperproject/skupper-router#864
On the main branch, a deployment is created to serve openssl s_server,
which is then exported by Skupper.
The script then repeatedly connects to that server using openssl s_client -reconnect,
until the issue on #864 occurs.
It's not working