Open tslothorst opened 4 years ago
Update: I upgraded the module. The issue appeared to be that for this procedure more space was needed on the lvm where /usr/local/share/powershell/Modules
was. The lvm had free space left, but not enough it seems.
The error about administrator rights still is odd and quite misleading here. An insufficient disk space error would feel more logical in this context.
@iSazonov is this issue correct in PowerShell repo or https://github.com/OneGet/oneget
@kvprasoon I don't know. We need more investigations. I think PowerShell might throw a too general exception.
This error is anyways coming from PackageManagement module https://github.com/OneGet/oneget/blob/173df840e345d0a753dd0a9dec684e394f1b22ea/src/Microsoft.PackageManagement/resources/Messages.resx
GitHubPackageManagement (aka OneGet) is a package manager for Windows - OneGet/oneget
/cc @alerickson for information.
I am trying to install/upgrade the VMware.PowerCLI on a RHEL 7.8 machine. The module was installed with the AllUsers scope. This results in an error message saying I need administrator privileges to do this. However I am running pwsh as root.
Steps to reproduce
My system has version 11.x of the VMware.PowerCLI present, which was installed with the AllUsers scope. All components therefor are located at
/usr/local/share/powershell/Modules
I've also ran
Update-Module
with the same parameters, this results in the same outcome.Expected behavior
A succesful upgrade of the module and it's components.
Actual behavior
Output when using
Update-Module
:Since pwsh is already being run by root it should have all privileges needed to write to the location where the modules are located.
Environment data