Solved

Unexpected output from Get-CVJob function if the -ClientName parameter is a non-existent client name

  • 5 February 2021
  • 5 replies
  • 202 views

Badge +1

I’m trying to use the CommVault powershell module to work with the API and integrate our backups with monitoring, so that our users will be able to  see monitori ng and backup stats at a glance. Should be easy enough to show jobs, but the powershell  Get-CVJob function is broken.

 

I had some help previously in the forum, and the broken bit was verified and posted to the gitHub powershell for CommVault projects, but I haven’t seen any movement since. Does anybody know how to fix this issue or what kind of timeframe I am working with to get this module fixed?

 

icon

Best answer by Damian Andre 17 February 2021, 17:29

View original

5 replies

Userlevel 6
Badge +12

My guess is the “unexpected output” is that is still shows all the other jobs correct?  If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.

Userlevel 5
Badge +10

My guess is the “unexpected output” is that is still shows all the other jobs correct?  If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.

@MFasulo yes, I reported the issue in GitHub here. https://github.com/Commvault/CVPowershellSDK/issues/19

Badge +1

My guess is the “unexpected output” is that is still shows all the other jobs correct?  If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.

@MFasulo yes, I reported the issue in GitHub here. https://github.com/Commvault/CVPowershellSDK/issues/19

Is there any kind of timeframe for how long it takes to turn around a GitHub issue? I did see the code alteration was suggested. Is there a way for me to edit the module and correct it to run this module and have the right output? 

Userlevel 7
Badge +23

My guess is the “unexpected output” is that is still shows all the other jobs correct?  If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.

@MFasulo yes, I reported the issue in GitHub here. https://github.com/Commvault/CVPowershellSDK/issues/19

Is there any kind of timeframe for how long it takes to turn around a GitHub issue? I did see the code alteration was suggested. Is there a way for me to edit the module and correct it to run this module and have the right output? 

Hey @JMH_ML - Confirming we have lodged a defect for this issue (MR 309834). So it is being worked on but I don’t know an ETA currently.

Userlevel 3
Badge +4

@Damian Andre @MFasulo @JMH_ML  This is now fixed and changes pushed to GitHub. Closed Issue: https://github.com/Commvault/CVPowershellSDK/issues/19

Reply