-
Notifications
You must be signed in to change notification settings - Fork 87
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
New-RubrikSnapshot, Protect-RubrikFileset - Cmdlets using -slaname w/identical Local/Remote SLA names are failing #720
Comments
Hello Steven, That is an interesting situation, I'll take a look at how we can best handle this. A fix that comes to mind would be adding a Run against local cluster
To run against a specific cluster ID
Run against local and remote
Would that be a workable solution for you? |
I think that is a good solution for cmdlets that take a '-sla' parameter to default to only using Local SLAs. These should be all cmdlets that assign/modify a SLA to an object or take a snapshot of an object associated with a SLA. |
Hello @stevenctong, I have updated both |
Hi @jaapbrasser - thanks for the quick fix! I confirmed that
I didn't test all but I did notice a slight difference in error between
Protect-RubrikDatabase
Protect-RubrikVM
Thanks again! |
Thanks Stephen, I have pushed out a prerelease build with the current changes to the PowerShell gallery so you can start using that one now by installing it using the following command: Install-Module Rubrik -AllowPrerelease -Scope CurrentUser I'll take a look at what is happening in Thanks for posting the extensive information and verbose logging, this makes it a lot easier and understandable for me to address the issue you mentioned. |
Current Behavior:
Cmdlets where you pass in 'slaname' on a cluster with SLAs that have identically named Local and Remote SLAs are failing. In the example below the cluster has a Local and Remote SLA named '1d-30d-NoArchive'. The cmdlet finds both the Local and Remote SLA IDs and tries passing it to the REST API call where it should only be passing the Local SLA ID.
This also happened with the 'Protect-RubrikFileset' cmdlet so I assume it will happen to any cmdlet that uses 'slaname'.
Expected Behavior:
When passing a SLA Name we expect it to find and use the Local SLA and not any Remote ones.
Steps to Reproduce:
Context:
I just upgraded to Rubrik Powershell v5.2 from v5.0 and I don't believe this issue was occurring previously.
The text was updated successfully, but these errors were encountered: