What happened: We are installing Falco via Ansible in our packer builds on Amazon Linux 2. We use largely the role from here: https://github.com/juju4/ansible-falco. This was working with builds until yesterday. Now we get the error Package falco-0.16.0-x86_64.rpm is not signed and yum exits.
What you expected to happen: Falco should install without error
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
falco --version): None, won't installcat /etc/os-release):uname -a): Linux ip-10-31-46-181.ponyformation.com 4.14.123-111.109.amzn2.x86_64 #1 SMP Mon Jun 10 19:37:57 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxPackage falco-0.16.0-x86_64.rpm is not signedTo add to this, the images that succeeded over the last couple of days have a Falco version of 0.15.3
/assign @mstemm
Mark can you PTAL?
Anyway this is probably related to the fact that the 0.16.0 release is still on going.
Maybe rpm --addsign step wasn't executed when adding package to the repo.
I am having this issue as well and this affects everyone(worldwide) who uses install-falco script and getting the packages from draios.repo
This issue is causing bad/abnormal results for automation flows where falco install is part of.
Sorry about this, the publishing of packages got interrupted during the signing step due to an internal config problem. We're working on the fix and I'll update this issue once the packages are fully published.
Thanks very much for looking into this so quickly. Appreciate it.
The packages should be fully signed now. I was able to install them on ubuntu 16.04 and centos 7 via apt-get and yum.
Most helpful comment
The packages should be fully signed now. I was able to install them on ubuntu 16.04 and centos 7 via apt-get and yum.