Live data from Hacker News

Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

azure.status.microsoft

1–10 of 12 posts

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#3
How unreliable azure is, it is impressive, just like with recent version of Windows

It seems like something at this company is not functioning well, it seems to be operated like it's no big deal, no QA, no quality and performance culture, it's a giant mess

It has infected Github too, impressive..

Google Cloud / Microsoft Azure, they have a looooooong way to go before being able to properly compete with AWS

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#4
post #3

How unreliable azure is, it is impressive, just like with recent version of Windows It seems like something at this company is not functioning well, it seems to be operated like it's no big deal, no QA, no quality and performance culture, it's a giant mess It has infected Github too, impressive.. Google Cloud / Microsoft Azure, they have a looooooong way to go before being able to properly compete with AWS

But the same issue would happen on AWS, it's an Ubuntu problem caused by Canonical

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#5
post #2

This is more of a Canonical issue than an Azure issue IMO. They pushed a broken systemd package. Is there any QA even going on at Canonical?!

systemd resolved has been broken in many releases of Ubuntu, this isn't surprising. it works most of the time but frequently will return errors.

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#8
post #4
post #3

How unreliable azure is, it is impressive, just like with recent version of Windows It seems like something at this company is not functioning well, it seems to be operated like it's no big deal, no QA, no quality and performance culture, it's a giant mess It has infected Github too, impressive.. Google Cloud / Microsoft Azure, they have a looooooong way to go before being able to properly compete with AWS

But the same issue would happen on AWS, it's an Ubuntu problem caused by Canonical

It's hitting loganalytics. That's not really a service for which customers deal with VMS directly.

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#9
post #3

How unreliable azure is, it is impressive, just like with recent version of Windows It seems like something at this company is not functioning well, it seems to be operated like it's no big deal, no QA, no quality and performance culture, it's a giant mess It has infected Github too, impressive.. Google Cloud / Microsoft Azure, they have a looooooong way to go before being able to properly compete with AWS

What other cockamamie opinions do you have? You should write a book, publish it to /dev/null

Re: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors

#10
post #4
post #3

How unreliable azure is, it is impressive, just like with recent version of Windows It seems like something at this company is not functioning well, it seems to be operated like it's no big deal, no QA, no quality and performance culture, it's a giant mess It has infected Github too, impressive.. Google Cloud / Microsoft Azure, they have a looooooong way to go before being able to properly compete with AWS

But the same issue would happen on AWS, it's an Ubuntu problem caused by Canonical

MS push having automatic unattended updates turned on. Azure complains without end if you don't, sometimes Defender (which Azure complains about if you don't have installed) updates override you having turned them off when it updates.

There being a bug in the package may be an Ubuntu thing, me losing time to diagnosing problems caused by the update getting applied without my knowledge is very much an MS/Azure problem.

At least this incident gives me fuel for strongly suggesting that we turn unattended-updates off and darn well keep it off (obviously we need to keep alerts on, but we should install updates in an orderly manner, when we can monitor the results and smoke-test, preferably applying to test resources before uat/prod/other).

Post reply on HN