Attention is currently required from: laforge, osmith.

View Change

1 comment:

• Commit Message:

  • Patch Set #1, Line 12: ensuring that only successful operations generate confirmation events.

    This sounds like a workaround, why not adjust trx_provision_fsm to check the event data instead?

    I guess we could change the FSM to shutdown immediately if some command fails. But that would be a lot more changes to the existing code. For now it's easier if the FSM remains stuck in the provisioning loop and then we fail due to a timeout. The current approach is not perfect, but still better than ignoring failures and declaring readiness to the BSC.

To view, visit change 42046. To unsubscribe, or for help writing mail filters, visit settings.