Open xdkreij opened 6 days ago
Seems it got 'fixed' 2 day's ago
is there a way to make this less 'static'? Otherwise one would require to pull the latest changes each time to make sure image creation might work.... which may cause former dependency & manual change issues... then I'll have to fork the repo...#morework
Dear @xdkreij thanks for bringing the issue to our attention.
You are indeed right about it being too 'static', this is a fix we are currently working on and it will probably be there in the next release
-D
It gets even stranger
Once the playbook is running... the first repo task finishes no problemo
But getting further down the line it tries to do the same... again...(yes i know, this time for the image... but the task is 100% the same..nonetheless; The fact that it breaks makes it everything but idempotent)
trix-tree trinity/init-nodes trinity/repos...
Seems like a repo issue - related to: https://github.com/clustervision/trinityX/issues/401#issuecomment-2192543389
Executed LC_ALL=C.UTF-8 ansible-playbook compute-redhat.yml -e "image_name: testimage" -v
Issue
Cause
roles/trinity/repos/vars/RedHat8.yaml
epel-release-8-19.el8.noarch.rpm is hardcoded and does not exist anymore
Expected results