vmware-archive / webcommander

Powerful, flexible, intuitive and most importantly simple. That is what a real automation solution should be. No matter how complicated the task is, we'd like to turn it into a single click. Is that possible? Not without webcommander :)
MIT License
165 stars 47 forks source link

Get-Tagassignment Problem sind vcenter 6.5 #182

Open aschi75 opened 7 years ago

aschi75 commented 7 years ago

Hi I have a script for exporting VM Details like Tags, etc. which works since months.

My collegue updated our Vcenter from 6.0 to 6.5 and since than I didn't get the Tags anymore. I installed "VMware-PowerCLI-6.5.0-4624819.exe" and also Powershell 5.1 "Win8.1AndW2K12R2-KB3191564-x64.msu" on the webcommander Server but the Problem persists.

It still works If i run the Script in ISE on the Webserver where Webcommander is running .

Part of the script: $getCategory = Get-TagCategory foreach ($cat in $getCategory) { ->with webcommander it's not going inside the loop.

Another Test: $GetVms = Get-VM | Where-Object {$_.PowerState -eq "PoweredOn"} foreach ($vm in $GetVms) { $vm.name ->this is working with webcommander

$test = ($vm | Get-TagAssignment –Category "Stage").Tag.name ->with webcommander the variable $test is empty }

Any Ideas or a known bug? Any hint is appreciated.

Regards, Roger

9whirls commented 7 years ago

Try to run the script in a clean powershell console (launch cmd.exe and then enter powershell). And see if it works there.

ISE (32bit and 64bit) and powershell console (32bit and 64 bit) all may have different profiles. That's why you may see different results.

aschi75 commented 7 years ago

Yes, it works well in a clean powershell console.

Some other ideas?

Best Regards,

roger

Von: Jian Liu [mailto:notifications@github.com] Gesendet: Mittwoch, 4. Oktober 2017 20:38 An: vmware/webcommander webcommander@noreply.github.com Cc: Aschwanden Roger, ACA-IT-OP-COR Roger.Aschwanden@accarda.com; Author author@noreply.github.com Betreff: Re: [vmware/webcommander] Get-Tagassignment Problem sind vcenter 6.5 (#182)

Try to run the script in a clean powershell console (launch cmd.exe and then enter powershell). And see if it works there.

ISE (32bit and 64bit) and powershell console (32bit and 64 bit) all may have different profiles. That's why you may see different results.

— You are receiving this because you authored the thread. Reply to this email directly, https://github.com/vmware/webcommander/issues/182#issuecomment-334250384 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AL9VRZ0x8o1BQtCiKAAroe1qt80qsrZQks5so9B1gaJpZM4PtIlV mute the thread.

9whirls commented 7 years ago

Please use Start-Transcript to save your script output in a log file. And then run it from both console and webcommander. Finally, compare the two output logs.

aschi75 commented 7 years ago

Hi

Thank you for the hint which gave me better logs.

It seems to be a bug in vcenter 6.5

https://communities.vmware.com/thread/569934

they opened a case: SR 17541052208

I tried some stuff with invoke-command bus wasn’t able to get it running.

I hope the next release of powercli will solve the problem.

You don’t have to investigate more time.

Thank you very much.

Best Regards

Roger

Von: Jian Liu [mailto:notifications@github.com] Gesendet: Donnerstag, 5. Oktober 2017 15:41 An: vmware/webcommander webcommander@noreply.github.com Cc: Aschwanden Roger, ACA-IT-OP-COR Roger.Aschwanden@accarda.com; Author author@noreply.github.com Betreff: Re: [vmware/webcommander] Get-Tagassignment Problem sind vcenter 6.5 (#182)

Please use Start-Transcript to save your script output in a log file. And then run it from both console and webcommander. Finally, compare the two output logs.

— You are receiving this because you authored the thread. Reply to this email directly, https://github.com/vmware/webcommander/issues/182#issuecomment-334467960 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AL9VRbfjtO7CeGDLKvy7dTbXuDM1cf3jks5spNxRgaJpZM4PtIlV mute the thread.

9whirls commented 7 years ago

Thanks for confirming this is not a webcommander issue. I don’t work for VMWare anymore. So I have no vsphere environment to do further investigation. Sorry.