Incorrect configuration can cause the BFB object to reference the wrong BFB file

[wpeng102]

Incorrect configuration can cause the BFB object to reference the wrong BFB file

If the user creates a BFB object with a fileName that match an existing file in shared volume (it may have a different CR name but same fileName field), but it targets a different BFB file via the url, but we won't have a way to know that so we mark the bfb as ready and progress.

Mitigating the Issue:

Recreate BFB object with a unique fileName or do not set fileName in BFB object.