So you wouldn't mind a rollback occurring on the process that builds your paycheck, right? 😉  As recently stated, rollbacks in production ARE failures and may indicate a bigger problem associated with the entire process of code development, testing, and deployment.  

Rollbacks in test are a development "failure" but such things happen because no one can write perfect code all the time for all the scenarios (that's not an excuse for getting lazy, though).  The purpose of testing (QA/UAT, etc) is to test for such things before they get to prod so it's not a "failure" if it's caught in a test environment.  Testing did what it was supposed to do and the people that developed the code just need to fix it.

But, the bottom line is (in my humble opinion), any and all rollbacks in production are, in fact, a failure.