There are a handful of things that I don't understand.

For one, why can't certain vendors let their customers know that the product that they depend on for their day to day usage was not actually patched to the current patch level on the scheduled time.

Not only was the time scheduled, but it was of course scheduled by the vendor, seeing as how the customer is basically at the mercy of said vendor.

Not only did the customer (us) have to check to ensure that the product was patched, but then the customer (us, again) has to contact big vendor support to ask why it wasn't patched.

Why can't they just pop some kind of email notification that says it was either successful or not?

Then if not - what the plan of action is?

Yeah. We asked this question on Monday.

I was out sick on Tuesday.

The only response we've had thus far was an incorrect notice that none of our instances have been patched at all.

We have three instances: one each for development, testing and production.

Our development instance had already been patched, as scheduled, so I got to let the vendor know that...um, no, I don't believe that's correct please don't re-patch.

Sigh.

Anyhow - now the vendor has let us know that it's time to board the patching train because they've scheduled the production instance for updating next week, when we haven't had a chance to do any testing in the test instance. Which is less of a playground than dev.

It's beyond infuriating.

Welcome to the cloud.

This is post 18/100 of my #100DaysToOffload posts. You can read the other posts in this series here.

Share this article

Published 17 Jul 2024