unclear how to test a specific release (e.g. 1.0.0-beta4) with eos

[jnweiger]

Following the steps in https://github.com/owncloud/ocis/blob/master/docs/eos.md#run-it
make eos-start
brings up a fresh instance. This procedure does not respond to a .env file or to setting the environment variable OCIS_DOCKER_TAG=1.0.0-beta4
This is what can be used with compose-playground/ocis, when testing ocis without eos.

Can we achieve a similar effect here?
I want to specify the release that I test.

[jnweiger]

ocis with eos fails to start, when specifying -b v1.0.0-beta4 during checkout. Is that the correct way to test 1.0.0-beta4?

git clone [email protected]:owncloud/ocis.git -b v1.0.0-beta4
cd ocis; make eos-start

...
** Enabling default space with quota disabled and booting filesystems
Wait for FSTs to become online ...
All FSTs are online
success: boot message sent to eos-fst1.eoscluster.cern.ch:/home/data/eos1 eos-fst2.eoscluster.cern.ch:/home/data/eos2 eos-fst3.eoscluster.cern.ch:/home/data/eos3 eos-fst4.eoscluster.cern.ch:/home/data/eos4 eos-fst5.eoscluster.cern.ch:/home/data/eos5 eos-fst6.eoscluster.cern.ch:/home/data/eos6 eos-fst7.eoscluster.cern.ch:/home/data/eos7
success: configuration successfully saved!
Wait for FSTs to boot ...
All FSTs are booted


*** Client servers creation and setup
ded21f6941212b222a430b47bc33eb279726ab66e8893e4bbc8c92f977523343
host/[email protected]: kvno = 1
Error: No such container:path: eos-kdc:/root/eos-user.keytab
chown: cannot access '/home/eos-user/eos-user.keytab': No such file or directory
make: *** [Makefile:195: eos-deploy] Error 1

With default master branch, that succeeds.
Reproducable with https://gitea.owncloud.services/jw/hetzner make_ocis_eos_test.sh

[jnweiger]

Fixed. Followup issue #310