Enjoyed the read; hats off to you guys for digging in and finding/resolving and pushing the bugfix upstream. I do have to wonder: did this bug all of a sudden

Enjoyed the read; hats off to you guys for digging in and finding/resolving and pushing the bugfix upstream. I do have to wonder: did this bug all of a sudden spring up on you? Seems like the potential would have always been there on this platform. Could a change management process have lead you to find that "adding megaCLI monitoring to all KVM hosts" or "upgrading to megacli 8.01.06" was the cause of the problem? Just curious if you perceive a better CM or system inventory could have allowed you to deduce the problem area with a bit more efficiency?