Closed kyanha closed 3 years ago
Same here with Pester and other modules
Having similar problem installing PSScriptTools, our build pipelines failing as a result.
Same behavior on my side
I am getting a 503 error when trying to pull any modules down at the moment
Modules cannot be pulled from the PowerShell Gallery at the moment. The PowerShell Gallery seems to be unavailable for at least a few hours already.
Is there any official websites for PowerShell Gallery status? It is hard to know that it is down or just an internet error.
https://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md
Although nothing on there as yet for this
Hi all, we currently have an outage and are working on resolving it. Our CDN is down preventing packages from being downloaded and availability for the gallery itself has been extremely low. I'll update here as mitigation steps progress.
Same problem here
PowerShellGallery has become a essential resource for many. It's been unstable and have had other problems for months.
@alerickson : Is Microsoft comitting to making PowerShellGallery a reliable resource for PowerShell modules in near future, or do we have to look for other solutions (like GitHub maybe) for reliably hosting PowerShell modules?
PowerShellGallery has become a essential resource for many. It's been unstable and have had other problems for months.
@alerickson : Is Microsoft comitting to making PowerShellGallery a reliable resource for PowerShell modules in near future, or do we have to look for other solutions (like GitHub maybe) for reliably hosting PowerShell modules?
I want to second the sentiment. Our CI/CD Pipelines quite heavily rely on the availability of multiple third-party modules that are primarily hosted on PS Gallery... I guess we should try to get rid of that single point of failure but Microsoft also should be doing more to guaranty the availability of something so vital to a lot of people.
Although I personally appreciate that @alerickson gave us the first official information about the problem from the responsible team from Microsoft, I think they should be doing a better job at communicating outages and mitigation progress than replying on Github issues.
I concur I have a change which is reliant on me pulling a module down to a new server so this is eating away at my change window.
facing same issue. Our ADO pipelines relies on powershell gallery for ps module. when we can aspect fix. Same kind of issue was observed few days back, but it was fixed by India Noon time on that day.
Same here..
Same here. Need to install Docker on a new server and therefore need psgallery to install my modules. Can't work on this server now..
Same issue here (Netherlands).
https://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md
Although nothing on there as yet for this
I think this page is for history now...
Same here, our pipelines came to a halt.
https://github.com/PowerShell/PowerShellGallery/blob/master/psgallery_status.md Although nothing on there as yet for this
I think this page is for history now...
Yes and apparently the only person on the team that thinks about informing users has no way of updating the repo
The gallery's been experiencing ongoing low availability. The issue should be mitigated now. I unfortunately don't have write permissions to this repo, but I've put in a PR to update the status. Feel free to comment here with updates on whether builds are still breaking. We're working on completely resolving the issue, but I'm hoping the scenario's improved for most.
Originally posted by @alerickson in https://github.com/PowerShell/PowerShellGallery/issues/132#issuecomment-704875043
Same issue here. Hopefully it will be fixed soon.
Took longer to time out but still failed
Yeah, still doesn't work here either.
Still not working.
Same issue here..
same here (Ireland)
Can confirm @aperally statement. Continues to be down in Ireland.
@alerickson Any update?
Same here UK
Large impact here.
Same here, pulling out my hairs as to why it wasn's working
Created a pull request to update the status page - https://github.com/PowerShell/PowerShellGallery/pull/136
it JUST came up for me.. hopefully long enough to get a couple pipelines through
Still not for me. I tried a few minutes back
I had a problem with installing PSReadline, now I have a second one - I don't understand why so many people don't vendor pipeline dependencies.
We (In Sitecore) still have the issue, any ETA on that? has been blocking us for hours.
Unable to install azure related modules...
For me this means I am dead in the water to managing my WVD 1.0 environment because it is 100% managed by Powershell and I rebuilt my machine and cannot reinstall the modules needed to manage it.
It's been down for over 7 hours now....this is getting ridiculous
what is happening??? Still down.....
Anybody remember last year when Azure Devops went down in south central US and we all wondered why there was no redundancy of the Azure Devops systems in other datacenters. The entirety of their development platform was down for a day for the entire customer base.
Pepperidge farms remembers
Workaround to install Az module: Az module could be installed from the last msi file: https://github.com/Azure/azure-powershell/releases/download/v5.0.0-October2020/Az-Cmdlets-5.0.0.33612-x64.msi
For those who just need Az modules and are using Azure Pipelines see this comment, negates the need to install them at all as they are already pre-installed on Azure Pipelines Hosted Agents: https://github.com/PowerShell/PowerShellGallery/issues/132#issuecomment-716863626
For those who just need Az modules and are using Azure Pipelines see this comment, negates the need to install them at all as they are already pre-installed on Azure Pipelines Hosted Agents: #132 (comment)
we are experiencing the issue even in AzurePowershell task.
Inline Scripts to test:
Script 1 : Get-PSRepository
Script 2: Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
we are experiencing the issue even in AzurePowershell task.
Personally we are using Azure CLI task set to Powershell Core and we use this bit of code to authenticate Az module from the CLI as we use both Az and CLI in our scripts.
function Connect-AzAccountFromCli {
Write-Debug "Connecting Az powershell account from cli"
$token = (az account get-access-token) | ConvertFrom-Json
$null = Connect-AzAccount -AccessToken $token.accessToken -AccountId $token.subscription -Tenant $token.tenant
}
Note if you do this the token will only last an hour or so and you will have to call that function again
Doesnt help us that needs modules that are not azure based
For other modules if you have them downloaded locally on your dev PC you could ship them with your code and do a local import, I've just changed our deployment scripts to do this with Newtonsoft.Json to eliminate our dependency on Powershell Gallery.
For example, I copied C:\Users\<user>\Documents\Powershell\Modules\newtonsoft.json\1.0.2.201
(location varies depending on PowerShell version and install scope) into the same folder as our deployment scripts, renamed it to Newtonsoft.Json
and then in our script ran Import-Module -Name (Join-Path $PSScriptRoot "Newtonsoft.Json")
You can see what modules are pre-installed on Azure Pipeline agents if you use those here: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
Jesus, how is this still not fixed?
Because it's probably a hard problem
I can't download EXO V2 powershell module from PSGallery.
Because it's probably a hard problem
It seems they don't have any DR plan. 🤦♂️
Powershell Gallery is returning 503. I can't currently run https://github.com/powershell/powershell tests because they try to pull Pester from it.