Open ghost opened 3 years ago
Hm, I can not reproduce this error
Hm, still have it, using df1b6d77d7ebb9ae07c2b1cf84eb48c0f90aca4b
But the tests also run fine in the github action. You get the error when running using vagrant up
? Which machine?
Yes, with vagrant up
. I only have the issue with the Upgrade test.
Ah, oke, the upgrade-test
machine, I didn't realize you meant that. Yes, that one is not tested by github actions and I can reproduce the error with that. I guess we hit the same problem we discussed on Monday: the ansible recipies copy a custom runtime.conf
on to the machine, but the intelmq packages ship a runtime.yaml
without a file-iput
. A solution would probably be to run the recommendes manual upgrade steps in the ansible/upgrade-tests.yml
file.
As the stable version is 3.0 now, we can drop the old-style configuration and just ship a new runtime.yml. makes the setup simpler and probably solved this bug as well.
relevant part is: