Hi All, experiencing a very strange anomaly since upgrading to 10.3.3
here is an example:
all ok here:
PS C:\scripts\catalog_loop\day1> Get-Catalog $CICatalog|Get-CIVAppTemplate | Where-Object {$_.Name -like "*4.5.300*"}
Name Status Owner StorageUsedGB
---- ------ ----- -------------
4.5.300_4_node_DE PoweredOff system 4846.000
PS C:\scripts\catalog_loop\day1> Get-Catalog $CICatalog|Get-CIVAppTemplate | Where-Object {$_.Name -like "*7.0.370*"}
Name Status Owner StorageUsedGB
---- ------ ----- -------------
7.0.370_4+2_node_DE PoweredOff system 7006.000
7.0.370_Robo_WTS_DE_Brownfield PoweredOff system 6298.000
PS C:\scripts\catalog_loop\day1>
all ok here too:
PS C:\scripts\catalog_loop\day1> Get-CIVAppTemplate -Name 4.5.300_4_node_DE
Name Status Owner StorageUsedGB
---- ------ ----- -------------
4.5.300_4_node_DE PoweredOff system 4846.000
PS C:\scripts\catalog_loop\day1>
I can't find the 7.0.370 example above:
PS C:\scripts\catalog_loop\day1> Get-CIVAppTemplate -Name 7.0.370_4+2_node_DE
Get-CIVAppTemplate : 6/7/2022 1:23:46 PM Get-CIVAppTemplate CIVAppTemplate with name '7.0.370_4+2_node_DE' was not found using the specified filter(s).
At line:1 char:1
+ Get-CIVAppTemplate -Name 7.0.370_4+2_node_DE
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [Get-CIVAppTemplate], VimException
+ FullyQualifiedErrorId : Core_OutputHelper_WriteNotFoundError,VMware.VimAutomation.Cloud.Commands.Cmdlets.GetCIVAppTemplate
PS C:\scripts\catalog_loop\day1>
any ideas why I cant find these? I've re-created the catalog item, same issue, I'm crossing my fingers & toes that this is not a database issue.
thanks!
Ok, this method works, not sure why it only happened since the upgrade
PS C:\scripts\catalog_loop\day1> Get-CIVApptemplate | Where-Object {$_.Name -like "*7.0.370_4+2_node_DE*"}
Name Status Owner StorageUsedGB
---- ------ ----- -------------
7.0.370_4+2_node_DE PoweredOff system 7006.000
PS C:\scripts\catalog_loop\day1>
seems to be bug with latest powercli , regression
modules:
PS C:\scripts\catalog_loop\day1> Get-Module
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script 1.0.0.0 ISE {Get-IseSnippet, Import-IseSnippet, New-IseSnippet}
Manifest 3.1.0.0 Microsoft.PowerShell.Management {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...}
Manifest 3.1.0.0 Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-Variable, Compare-Object...}
Script 7.0.3.1... VMware.Vim
Script 12.6.0.... VMware.VimAutomation.Cis.Core {Connect-CisServer, Disconnect-CisServer, Get-CisService}
Script 12.0.0.... VMware.VimAutomation.Cloud {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, Get-Catalog...}
Script 12.6.0.... VMware.VimAutomation.Common {Get-PowerCLIContext, Get-Task, New-OAuthSecurityContext, Stop-Task...}
Script 12.6.0.... VMware.VimAutomation.Core {Add-PassthroughDevice, Add-VirtualSwitchPhysicalNetworkAdapter, Add-VMHost, Add-VMHostNtpServer...}
Script 12.5.0.... VMware.VimAutomation.Sdk {Get-ErrorReport, EnableParameterCompleters, Get-InstallPath, Get-PSVersion}
Script 12.6.0.... VMware.VimAutomation.Storage {Add-EntityDefaultKeyProvider, Add-KeyManagementServer, Add-VsanFileServiceOvf, Add-VsanObjectToRepairQueue...}
Script 12.5.0.... VMware.VimAutomation.Vds {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, Export-VDPortGroup, Export-VDSwitch...}
Ok, this method works, not sure why it only happened since the upgrade
PS C:\scripts\catalog_loop\day1> Get-CIVApptemplate | Where-Object {$_.Name -like "*7.0.370_4+2_node_DE*"}
Name Status Owner StorageUsedGB
---- ------ ----- -------------
7.0.370_4+2_node_DE PoweredOff system 7006.000
PS C:\scripts\catalog_loop\day1>
seems to be bug with latest powercli , regression