It is entirely possible that this is a success story of a lower-level engineer raising an issue that the higher levels then addressed.
Just because no one immediately jumps and say "by golly, we have to get rid of component X right now!" doesn't mean that the issue didn't begin percolating vertically and horizontally, ultimately resulting in a large-scale corrective effort.
Then I did not take the high road. The guy was very obnoxious and I had other issues to address. So I let it slide to maintain my "this is important" quota for other matters.
And a couple of months later, when some units failed on the test aircrafts (I insist on the fact that this was not a critical system), I had an issue report showing that the issue was observed during supplier-side tests and then ignored.
I reported the issue and the systems architect waved it off arguing that his analysis of the supplier data had proven that the MTBF for this component was over 500 thousand hours.
Few months later, a task force was established by the project management to look for an alternate supplier for this component after it became obvious that its failure rate was significantly higher than advertised.