Powertool convertTo-UcsCmdlet returns error message

[Alois Gritsch]

Hi

our customer is getting an error message when he tries to start the convertto-ucscmdlet.

he has installed the actual powertool version 1.0.0.0 on two systems and both getting the same message.

There is no difference if he is connected or not to an UCS system.

i searched for the logfile directory from the UCSM but wasn't successfull.

Here the message:

C:\> disconnect-ucs
C:\> ConvertTo-UcsCmdlet -verbose
WARNING: Please review the generated cmdlets before deployment.
ConvertTo-UcsCmdlet : Could not find the log files directory
At line:1 char:20
+ ConvertTo-UcsCmdlet <<<<  -verbose
     + CategoryInfo          : NotSpecified: (:) [ConvertTo-UcsCmdlet], Exception
     + FullyQualifiedErrorId : Cisco.Ucs.Cmdlets.ConvertToUcsCmdlet

C:\> ConvertTo-UcsCmdlet
WARNING: Please review the generated cmdlets before deployment.
ConvertTo-UcsCmdlet : Could not find the log files directory
At line:1 char:20
+ ConvertTo-UcsCmdlet <<<<
     + CategoryInfo          : NotSpecified: (:) [ConvertTo-UcsCmdlet], Exception
     + FullyQualifiedErrorId : Cisco.Ucs.Cmdlets.ConvertToUcsCmdlet

C:\>

thx Alois

[olivier.boudry]

Hi Anuj,

Thanks for the link.

There is apparently nothing we can do on the customer side as signing the jnlp means signing the jar and making sure the saved JNLP matches the JNLP used for starting the app. Other methods (renaming the properties) need changes to code.

Do you have any idea if fixing this is planned and if not how I could report the bug to Cisco? I'm asking you as there is a cisco logo next to your photo that seems to mean you're working at Cisco.

Thanks,

Olivier.

[Anuj Thapa]

I have tried this on update25 , I would check with update45 and get back to you.

Meanwhile from the comments above I might suspect the defect below , opened for UCSM Gui but the core issue matches.

https://tools.cisco.com/bugsearch/bug/CSCuj84421