Cause: if a sample template available in a prior release was removed in a subsequent release, then during upgrade to that subsequent release the removed template could be incorrectly tracked as needing to be updated, and the subsequent failure to read that template from the current payload leads to confusing 'no such file or directory error reading file []' messsages and apiserver errors reported in the samples clusteroperator status Consequence: overall upgraded could be marked as failed if the problematic timing windows in samples operator occurred Fix: samples operated was updated to not attempt to update templates which existed in a prior release but not in the release we are upgrading to Result: templates that are removed release to release should not cause samples operator to fail upgrade or report confusing clusteroperator status