New Update: Microsofts Linux work apparently broke itself

New Update: Microsoft Linux work apparently broke itself

Developers

(Image credit: Startup Stock Photos / Pexels)

Lack of official word doesn’t bode well for the corporate, say developers

Microsoft’s official repository, from which it serves all its cross-platform software for several Linux distros, was knocked offline for nearly a whole day.

Microsoft builds and supports a spread of software products for distros like Red Hat Enterprise Linux, CentOS, Debian, Fedora, Ubuntu, et al., and makes them available via standard APT and YUM package repositories. 

Many users who used these software and tools took to GitHub to boost the difficulty with the respective projects, including .NET Core, Microsoft Teams, Microsoft SQL Server for Linux, Microsoft Edge, et al..

Microsoft engineer, Rahul Bhandari, from the .NET team informed users that the repository “ran into some space issues.” 

Bad press

The outage apparently disrupted the workflow of the many developers, who were frustrated by the shortage of communication from Microsoft.

In response to Bhandari’s update, which came several hours into the outage, one user listed several other issues raised by users in other projects that were closed with no update or resolution to the disruption.

A status update on the Azure DevOps project by another Microsoft programmer, Edgar Ruiz Silva pinned the difficulty of maintenance work. 

“The issue is now fully mitigated. Maintenance work on packages.microsoft.com caused temporary unavailability of some files therein the package repository. We apologize for the impact this had on our customers,” wrote Silva.

An outage of this type and scale by one among the leading cloud providers doesn't reflect well on Microsoft, especially when its competition goes all bent to demonstrate the prowess of their cloud computing platform.

The least that Microsoft can do now, especially given the quantity of disruption caused by the broken repositories, is to take the time to interact with its users and explain the difficulty intimately, alongside the steps they’ve taken to make sure such disruptions don’t reoccur.

Source URL