We have found some entertaining behavior for Linux Bundles

We create a bundle and assign a system requirement - in this case a file creation date > than some date.
It drops an error "Cannot assign bundle" in the message log for the server, sends an error report to the lucky soul who gets those.
The deployment status shows as unknown and the server shows up in the "Critical Error" column on the ZCM home screen.

All because the bundle failed to meet a system requirement.
Removing the system requirement also removes the error - but of course it also deploy the bundle to a system that it should not have.