ci: remove docker vfs workaround

[ltalirz]

it appears to be no longer needed

[ltalirz]

@rptaylor I fixed the CI setup + an issue with the yum package install line

it now errors here

TASK [cvmfs_contrib.cvmfs_client : CVMFS check setup] **************************
fatal: [instance]: FAILED! => {"changed": false, "cmd": ["/usr/bin/cvmfs_config", "chksetup"], "delta": "0:00:05.680492", "end": "2023-05-20 19:51:10.365095", "msg": "non-zero return code", "rc": 2, "start": "2023-05-20 19:51:04.684603", "stderr": "", "stderr_lines": [], "stdout": "Warning: autofs service is not running\nWarning: cache limit for soft.computecanada.ca is very low (below 1GB)\nError: no public keys in /etc/cvmfs/keys\nError: required parameter CVMFS_SERVER_URL undefined for soft.computecanada.ca", "stdout_lines": ["Warning: autofs service is not running", "Warning: cache limit for soft.computecanada.ca is very low (below 1GB)", "Error: no public keys in /etc/cvmfs/keys", "Error: required parameter CVMFS_SERVER_URL undefined for soft.computecanada.ca"]}

I suggest you squash & merge this PR and then take it from here

[rptaylor]

@ltalirz Thanks for looking into it!
What configuration or playbook are you using for the CI test? It must be using some non-default configuration, I can see for example that the quota is set to a non-default (too small) size. There must be some other configuration also present that is out of date? I can not see anything in the repository that controls this.

If I run your branch on a VM with a playbook such as

- hosts: test
  roles:
    - ansible-cvmfs-client
  vars:
    cvmfs_client_configure_storage: false
    cvmfs_cache_size: 5000

then it works fine, and also avoids the warning.

[rptaylor]

Oh I was looking in .github but I see it is in molecule/ .

Looks like it is using ubuntu 22.04? Can we change it to use a standard Almalinux 8 OS @ltalirz ?
The cvmfs-config-default package is probably not available in the apt repo, if there even is an apt repo for Ubuntu.
The output also indicates that autofs is not running, so the same is probably true for the cvmfs-auto-setup package.
I have no idea how the CVMFS package can even be installed.