So it turns out that the cause was indeed a rogue change they couldn’t roll back as we had been speculating.

Weird that whatever this issue is didn’t occur in their test environment before they deployed into Production. I wonder why that is.

  • No1
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    7 months ago

    Change Manager who approved this is gonna be sweating bullets lol

    “Let’s take a look at the change request. Now, see here, this section for Contingencies and Rollback process? Why is it blank?”

    • zurohki
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 months ago

      I’m sure there was a rollback process, it just didn’t work.

      • MalReynolds@slrpnk.net
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        7 months ago

        If you don’t test a restored backup, you don’t have a backup, same applies here.