Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update-AWSToolsModule does not make upgrade to the latest version #340

Open
PetrMa opened this issue Feb 15, 2024 · 11 comments
Open

Update-AWSToolsModule does not make upgrade to the latest version #340

PetrMa opened this issue Feb 15, 2024 · 11 comments
Labels
bug This issue is a bug. module/powershell-cmdlets p2 This is a standard priority issue queued

Comments

@PetrMa
Copy link

PetrMa commented Feb 15, 2024

Describe the bug

Hello,
Currently I have installed AWSTools in version 4.1.515.0 and I would like to use command Update-AWSToolsModule -CleanUp to make an update to the latest version 4.1.516.0 which is currently available on https://www.powershellgallery.com/packages/AWSPowerShell/4.1.516

But if I run the command Update-AWSToolsModule -CleanUp
I´ve got the answer that update modul will make an update to version 4.1.433.0 instead of the latest available version
Performing the operation "Install-AWSToolsModule" on target "AWS Tools version 4.1.433.0".
and the CleanUp command wants to uninstall all newest versions.

So how Can I use this command to update AWSTools to 4.1.516.0 and removing all older versions please?

image

Expected Behavior

Make an upgrade of all modules to latest version available on https://www.powershellgallery.com/packages/AWSPowerShell/

Current Behavior

The command make upgrade to old version of AWSTools

Reproduction Steps

Run a command Update-AWSToolsModule -CleanUp

Possible Solution

No response

Additional Information/Context

No response

AWS Tools for PowerShell version used

AWS.Tools 4.1.515

PowerShell version used

Name Value


PSVersion 5.1.20348.2227
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.20348.2227
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Operating System and version

Windows Server 2022 Datacenter Edition

@PetrMa PetrMa added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 15, 2024
@bhoradc bhoradc self-assigned this Feb 15, 2024
@bhoradc bhoradc added module/powershell-cmdlets p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Feb 15, 2024
@bhoradc
Copy link

bhoradc commented Feb 15, 2024

Hi @PetrMa,

Thank you for reporting this issue. I am able to reproduce it at my end, and therefore will discuss this further with the team for next steps.

Regards,
Chaitanya

@bhoradc bhoradc added needs-review p1 This is a high priority issue queued and removed p2 This is a standard priority issue needs-review labels Feb 15, 2024
@PetrMa
Copy link
Author

PetrMa commented Mar 6, 2024

Hello @bhoradc,

some news about this bug please?

@afroz429
Copy link
Contributor

@PetrMa Sorry for the delay. I am unable to reproduce the issue on my computer. I reached out to @bhoradc and we tried it together but this time he wasn't able to reproduce on his computer either. here's the result with exact same module names and versions as you.


PS C:\Users\localuser> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

PS C:\Users\localuser> Get-Module AWS.Tools.Installer

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.0.2.5    AWS.Tools.Installer                 {Install-AWSToolsModule, Uninstall-AWSToolsModule, Update-AWSToolsModule}


PS C:\Users\localuser> Get-Module -Name AWSPowerShell,AWSPowerShell.NetCore,AWS.Tools.Common -ListAvailable


    Directory: C:\Users\localuser\Documents\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     4.1.515    AWS.Tools.Common                    {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize-AWSDefaultConfiguration, Clear-AWSDefaultConfiguration...}
Binary     4.1.514    AWS.Tools.Common                    {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize-AWSDefaultConfiguration, Clear-AWSDefaultConfiguration...}
Binary     4.1.467    AWS.Tools.Common                    {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize-AWSDefaultConfiguration, Clear-AWSDefaultConfiguration...}
Binary     4.1.433    AWS.Tools.Common                    {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize-AWSDefaultConfiguration, Clear-AWSDefaultConfiguration...}


PS C:\Users\localuser> Update-AWSToolsModule -CleanUp

Confirm
Are you sure you want to perform this action?
Performing the operation "Install-AWSToolsModule" on target "AWS Tools version 4.1.538.0".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): n

Confirm
Are you sure you want to perform this action?
Performing the operation "Uninstall-AWSToolsModule" on target "AWS Tools version 4.1.515, 4.1.514, 4.1.467, 4.1.433".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):

What is the AWS.Tools.Installer version you are using? Can you please run the Update-AWSToolsModule with -Verbose flag and send the results?

Thanks!

@PetrMa
Copy link
Author

PetrMa commented Apr 3, 2024

@afroz429 @bhoradc

Hello,
sorry for the late response. I had a vacation.

I´am still on the same issue as described in my 1st post.
image

The verbose command show this:
image
image

@ashishdhingra
Copy link
Contributor

@PetrMa Good morning. Unfortunately, we are unable to reproduce the issue. Could you please check:

  • If you have sub-directories for AWS .Tools.* module at %USERPROFILE%\Documents\WindowsPowerShell\Modules?
  • If yes, what is the name for version sub-directories look like for an AWS.Tools.<<Service>> directory (e.g. sub-directory under AWS.Tools.S3 directory? Does it look like 4.1.XXX.0? in other words, does have trailing .0 at the end?
    This is a known issue with Windows PowerShell (not PowerShell Core) outside of AWS Tools for PowerShell control.

Thanks,
Ashish

@ashishdhingra ashishdhingra added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Jun 4, 2024
Copy link

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Jun 10, 2024
@PetrMa
Copy link
Author

PetrMa commented Jun 10, 2024

Hi @ashishdhingra

no, there is no directory Modules in %USERPROFILE%\Documents\WindowsPowerShell\

All modules are installed in C:\Program Files\WindowsPowerShell\Modules
Modules are installed for all users, not for specific user.

@github-actions github-actions bot removed closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jun 11, 2024
@jnunn-aws
Copy link
Contributor

@PetrMa I have determined that this issue is caused when trying to update deprecated modules for which we are no longer publishing new versions. We will start working on a fix.

Until then you can workaround this issue by uninstalling modules that are not being updated daily.

AWS.Tools.Mobile
AWS.Tools.BackupStorage
AWS.Tools.Honeycode
AWS.Tools.AlexaForBusiness
AWS.Tools.IoTRoboRunner
AWS.Tools.Macie
AWS.Tools.GameSparks
AWS.Tools.Installer

I obtained this list by invoking Find-Module AWS.Tools.* | Sort-Object 'Version' -Descending and identifying modules at the bottom of the list with a version less than the current latest version.

@PetrMa
Copy link
Author

PetrMa commented Aug 6, 2024

Hello @jnunn-aws ,

I could confirm that uninstalling of modules mentioned above (except AWS.Tools.Installer - this module doesn´t affect this issue) solve this issue. Please let me know when you fix this issue.

Thanks, regards,
Petr

@ashishdhingra ashishdhingra added p2 This is a standard priority issue and removed p1 This is a high priority issue labels Aug 21, 2024
@PetrMa
Copy link
Author

PetrMa commented Oct 21, 2024

Hello @jnunn-aws ,

today I tried to update AWS tools on my computer and again I had to manually delete some other deprecated cmdlets.
4.1.665 AWS.Tools.WorkLink
4.1.639 AWS.Tools.CodeStar

Is there any plan to fix this issue please? In this state it is unusable.

thanks, Petr

@jnunn-aws
Copy link
Contributor

We are actively working on this. We are revising the design of the bug fix to minimize tradeoffs. Once there is an update, I will post here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. module/powershell-cmdlets p2 This is a standard priority issue queued
Projects
None yet
Development

No branches or pull requests

5 participants