Pipeline is busted on "Master" branch

Summary

After our IB "Get Unstuck" meeting and Sean's merge to master last week, the IB pipeline on our master branch is persistently failing. The pipeline ran fine against our development branch. @sean.melissari @kwami.delali

Link to failed pipeline

https://repo1.dso.mil/dsop/f18-navy-boeing/osee/osee-hsql/-/pipelines/154622

What is the current bug behavior?

wl compare lint stage is failing with "script failure". The logging seems to indicate some sort of sync failure / data loss between the container's Iron Bank status and its (non)listing in the newest updated VAT. "error: This container is not noted as an approved image in VAT. Unapproved images cannot run on master branch. Failing stage." This, despite the container having been previously approved (and, in fact present) in Iron Bank.

What is the expected correct behavior?

Pass the "wl compare lint" stage and have 0 non-inherited findings in the output .csv.

Possible fixes

I think someone just needs to fix the container's status in VAT? I think @kwami.delali told me he does not have the privileges to make this fix.

Definition of Done

• Pipeline failure has been resolved

/cc @ironbank-notifications/pipelines