Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/841
> During the deployment, I noticed the following message. I was not sure if
this can be ignored or needs to be looked at.
Hi Anand - Thanks for testing! I saw that a few times also. During
deployment it has to reboot the VM to pickup new kernel options. Sometimes
Ansible fails to wait long enough for the reboot. If this error does happen,
running `vagrant provision` it will continue the progress. That is what I did
during my testing.
I am not sure exactly what the problem is, but the same condition occurs in
master. I would call this a pre-existing condition that we can handle with a
separate PR.
Of course that is just my opinion and you or others may feel differently.
Let me know what you think.
---
