03/22/2020 02:30 UTC The PowerShell Gallery was unable via HTTPS.
Status: Resolved
Summary of Impact: Users were unable to access the gallery or download packages using HTTPS.
Root Cause: In the last few months we addressed some internal compliance mandates to autorotate our certificates every 3 months. The renewal for these certs was set to 80% of the lifespan of the cert. Because our certificates were valid for a year this meant we had nealry 3 months to do a deployment in order to update the thumbprint to reference the new certificate (a timeframe in which our deployment cadence fell within). Because the validity period is now only 3 months, it was renewed only about 8 days before the old cert became invalid. Thumbprint values have a Key Vault secret reference in the repository and this value gets retrieved and updated in the cloud service configuration file whenever a new cloud service is deployed. We are in the process of automating this process so that a deployment is not necessary to update a cert's thumbprint and thumbprints are updated upon cert renewal.
10/30/2020 18:15 UTC The PowerShell Gallery is currently: __Experiencing a continued outage
Status: Resolved
Summary of Impact: PowerShellGallery.com is experiencing an outage. Users will be unable to access the gallery or download packages.
Root Cause: Work was happening to migrate data lost from the last outage to get the statistics up-to-date. However, an update to the database caused extremely high CPU/DTU utilization which tied up cloud service resources. In an effort to mitigate this issue the production database was restored to a point in time where the database was in a stable state, however this restore caused an error in the configuration of the SQL cluster that resulted in the gallery front end not able to authenticate with the SQL backend. Unfortunately, it took awhile to figure this out. Once that was identified, the SQL configuration was fixed and validated that basic operations are working again. This means for now the statistics are not complete and we'll look at fixing that later after reviewing how this mistake occurred. We are actively monitoring the gallery to ensure it maintains proper operation across all regions.
Database updates will be made on Monday, October 19th at 9am and will last 10 minutes. The update will lock specific tables in the database and may potentially impact search requests made to the gallery. This should not impact package downloads.
10/7/2020 - PowerShellGallery.com is experiencing low availability that may result in an inability to install package or access data on the website.
Status: Resolved
Summary of Impact: PowerShellGallery.com is experiencing lags and low availability. Further updates will be made pending mitigation and resolution.
Root Cause: Under investigation
Status: Resolved
Summary of Impact: PowerShellGallery.com was unavailable between 8:15 AM and 11:15 AM Pacific Time.
Root Cause: This occurred because of a routine configuration update the previous day: we updated a password used for sending email. The new password contained a character which was not valid as part of a URL, but the script used to perform the update did not correctly escape the character. This meant that each service instance as it restarted would read the new configuration and fail to load. This would have been caught in the test gallery, but the script also silently failed to restart the service instances, so nothing went wrong immediately and the configuration change was applied to the production gallery as well. As each service instance restarted afterwards, it entered a failed state. At the start of the incident, the last instances restarted and the service became unavailable.
Resolution: Changes have been made to the script and process used to roll out configuration changes to prevent this problem from recurring, and the service itself has also been made more robust against this kind of issue.
Status: Resolved
Summary of Impact: Users in some regions reported issues downloading some packages. The downloads reported an error similar to: "Install-Package : Package 'AzureRM.profile' failed to be installed because: End of Central Directory record could not be found.".
This was due to an error in CDN configuration which lead to an invalid file being cached and served by some CDN regions. The issue is now believed resolved, please contact cgadmin@microsoft.com if you still see this problem.
Status: Resolved
Summary of Impact: The link from the package details pages to Facebook is not currently working. Root cause is being investigated. As a temporary workaround, users need to manually create entries in Facebook that link to their PowerShell Gallery items.
Root Cause: Related to update to newer gallery version
Resolution: Due to historical low usage, all the social media buttons (FaceBook, Twitter and LinkedIn) have been removed from the site.
Next Steps:
Status: Resolved
Summary of Impact: The interaction between Azure Automation and PowerShell Gallery was broken temporarily. The links to the PowerShell Gallery from inside Azure Automation were not functioning.
Root Cause: A configuration change was applied to Azure Automation that corrected the issue.
Resolution: Changes to data structures in the new PowerShell Gallery resulted in the Automation Gallery not being able to interpret the data.
Next Steps: A configuration change has been applied, the issue is resolved to the best of our knowledge.
Status: RESOLVED
Summary of Impact: The PowerShell Gallery experienced a period of very high latency, resulting in intermittent connection issues, beginning approximately 5pm (PDT) 10/10/17. While resolving the issue, the site was taken offline for 2 hours starting approximately 10pm (PDT). The site was restored shortly before midnight 10/10/2017.
Root Cause:
Resolution: The web services had to be taken offline and restored in order to address the primary issue.
Next Steps:
Status: RESOLVED
Summary of Impact: Deploying items with dependencies to Azure Automation from the PowerShell Gallery is currently unavailable. Importing items from the PowerShell Gallery from inside Azure Automation is still available.
Root Cause: Items that have dependencies on others, and have been previously deployed to Azure Automation, will not be deployed to Azure Automation. Engineers have identified an issue with how ARM templates are generated for items with dependencies for the Deploy to Azure Automation functionality.
Resolution: Engineers are working to resolve issue. The current workaround for users is to import the item from the PowerShell Gallery from inside Azure Automation.
Next Steps: Engineers will release the fix shortly. In the meantime, please use the recommended workaround.
Status: RESOLVED
Summary of Impact: Some users were unable to log in to the PowerShell Gallery using Azure AD Accounts.
Root Cause: During an update to interact more securely with AAD, a setting change was missed. The testing done to validate the change did not include certain types of AAD accounts, so the deployment proceeded.
Resolution: Engineers identified the missing setting and corrected the problem.
Next Steps: We will be modifying our testing to include a broader set of AAD account types.
Status: RESOLVED
Summary of Impact: Direct links to individual module and script pages on https://www.powershellgallery.com were broken. This was being reported across all the regions. This did not impact any of the PowerShellGet cmdlets ie., Install-Module, Install-Script, Update-Module, Update-Script, Publish-Module, Publish-Scirpt continued to work.
Root Cause: Engineers identified the cause as an issue bringing up social media buttons like Facebook onto the page.
Resolution: Engineers fixed the problem by disabling the Facebook count information.
Next Steps: We opened an internal tracking issue to fix our usage of Facebook API.
Status: RESOLVED
Summary of Impact: Between 12/13/2016 and 12/15/2016, any messages sent via Contact Owners, Manage Owners, Contact Support, or Report Abuse were not received by the PowerShell Gallery Administrators.
Root Cause: Engineers identified the cause as an authentication issue with the SMTP server.
Resolution: Engineers were able to resolve the authentication issue and restore connection to the SMTP server.
Next Steps: If you used the Contact Owners, Manage Owners, Contact Support, or Report Abuse links to send mail to cgadmin@microsoft.com during this time and we have not responded, please try again. We apologize for the inconvenience.
8/10/2016 - Resolved: Unable to send emails to cgadmin@microsoft.com
Status: RESOLVED
Summary of Impact: Between 8/5/2016 and 8/10/2016, customers were unable to send emails to cgadmin@microsoft.com, or use the Contact Us feature.
Root Cause: Engineers identified the cause as a configuration change of the email account.
Resolution: Engineers worked to resolve the configuration issue.
Next Steps: If you used the Contact Us link or sent mail to cgadmin@microsoft.com during this time and we have not responded, please try again. Thank you for your patience.
Status: RESOLVED
Summary of Impact: Between 7/11/2016 and 7/13/2016, a subset of customers experienced issues downloading items from the PowerShell Gallery. The issue likely manifested itself in the following error message returned from Install-Module/Install-Script and Save-Module/Save-Script:
PS C:\> Install-Module xStorage
PackageManagement\Install-Package : Package 'xStorage' failed to be installed because:
End of Central Directory record could not be found. At C:\Program
Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1375 char:21 + ...
$null = PackageManagement\Install-Package @PSBoundParameters +
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidResult:
(xStorage:String) [Install-Package], Exception + FullyQualifiedErrorId : Package '{0}'
failed to be installed because: {1},Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage Preliminary root cause: Engineers identified an issue with Azure Content Deliver Network (CDN), which was deployed to the PowerShell Gallery on 7/11/2016.
Mitigation: Engineers disabled Azure CDN in the PowerShell Gallery.
Next Steps: Investigate the underlying root cause and developing a solution to prevent future occurrences.
Status: RESOLVED
Summary of Impact: Between 5/17/2016 and 5/19/2016, a subset of customers experienced issues downloading items from the PowerShell Gallery. The issue likely manifested itself in the following error message returned from Install-Module/Install-Script and Save-Module/Save-Script:
VERBOSE: Hash for package 'AzureRM.OperationalInsights' does not match hash provided from the server.
VERBOSE: InstallPackageLocal' - name='AzureRM.OperationalInsights', version='1.0.8',
destination='C:\Users\jbritt\AppData\Local\Temp\2\1741355729'
WARNING: Package 'AzureRM.OperationalInsights' failed to be installed because:
End of Central Directory record could not be found.
WARNING: Dependent Package 'AzureRM.OperationalInsights' failed to install.
WARNING: Package 'AzureRM' failed to install.
VERBOSE: Module 'AzureRM.Network' was saved successfully.
VERBOSE: Saving the dependency module 'AzureRM.NotificationHubs' with version '1.0.8' for the
module 'AzureRM'.
VERBOSE: Module 'AzureRM.NotificationHubs' was saved successfully.
PackageManagement\Save-Package : Unable to save the module 'AzureRM'. At C:\Program
Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1187 char:21 +
$null = PackageManagement\Save-Package @PSBoundParameters +
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +
CategoryInfo : InvalidOperation: (Microsoft.Power...ets.SavePackage:SavePackage)
[Save-Package], Exception + FullyQualifiedErrorId : ProviderFailToDownloadFile,
Microsoft.PowerShell.PackageManagement.Cmdlets.SavePackage Preliminary root cause: Engineers identified an outage in the underlying provider of Azure Content Deliver Network (CDN), which was deployed to the PowerShell Gallery on 5/17/2016.
Mitigation: Engineers disabled Azure CDN in the PowerShell Gallery.
Next Steps: Investigate the underlying root cause and developing a solution to prevent future occurrences.