Skip to content
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

[DataProtection/BackupVaults] Failed to create backupVaults with datastoreType value set to SnapshotStore #21183

Closed
sinbai opened this issue Oct 19, 2022 · 4 comments · Fixed by #21551
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. DataProtection

Comments

@sinbai
Copy link

sinbai commented Oct 19, 2022

When creating the backupVaults with the datastoreType value set to SnapshotStore via the latest version API, the error occurs as follows.

Error:


{
    "error": {
        "additionalInfo": [
            {
                "type": "UserFacingError",
                "info": {
                    "message": "Input provided for the call is invalid",
                    "recommendedAction": [
                        "Please check the required inputs"
                    ],
                    "details": null,
                    "code": "BMSUserErrorInvalidInput",
                    "target": "",
                    "innerError": null,
                    "isRetryable": false,
                    "isUserError": false,
                    "properties": {
                        "ActivityId": "8cea6775-2521-4f90-8b71-6fcf7794a1da"
                    }
                }
            }
        ],
        "code": "BMSUserErrorInvalidInput",
        "message": "Input provided for the call is invalid",
        "target": null,
        "details": null
    }
}

Request URL: https://management.azure.com/subscriptions/xxx/resourceGroups/1019/providers/Microsoft.DataProtection/backupVaults/sft-3?api-version=2022-05-01

Request Body:
{"location":"eastus","properties":{"storageSettings":[{"datastoreType":"SnapshotStore","type":"LocallyRedundant"}]},"tags":{}}

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Oct 19, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Oct 20, 2022
@navba-MSFT
Copy link
Contributor

@sinbai Apologies for the late reply. Thanks for reaching out to us and reporting this issue. It seems like the valid enum values for the storage settings are ArchiveStore, OperationalStore, VaultStore.

So could you please try to specify either of the above enum values instead of SnapshotStore and check if that helps ?

In the meantime, I will be creating a PR to get this addressed.

@navba-MSFT navba-MSFT added DataProtection bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 14, 2022
@sinbai
Copy link
Author

sinbai commented Nov 14, 2022

@navba-MSFT thanks for your reply. Since the enum values for the storage settings are listed in the latest API as ArchiveStore, SnapshotStore, VaultStore. If the SnapshotStore should be replaced with OperationalStore, the API should be updated first. This is because Terraform relies on the Azure API to create Data Protection Backup Vaults. Could you let me know once the Azure API is updated?

Refer to the original terraform issue: hashicorp/terraform-provider-azurerm#18826

@navba-MSFT
Copy link
Contributor

@sinbai Thanks for getting back. As mentioned in my above comment, I will be creating a PR to update the same and this will be reviewed by the Service team later.

@sinbai
Copy link
Author

sinbai commented Nov 14, 2022

@navba-MSFT thanks for your time:).

@navba-MSFT navba-MSFT self-assigned this Nov 15, 2022
navba-MSFT added a commit that referenced this issue Nov 15, 2022
 fixes #21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
xiaoxuqi-ms pushed a commit that referenced this issue Nov 28, 2022
fixes #21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-go that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-net that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-powershell that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-js that referenced this issue Nov 28, 2022
{AzureDataProtection} fixes Azure/azure-rest-api-specs#21183 (Azure#21551)

fixes Azure/azure-rest-api-specs#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
anandanthony pushed a commit to anandMicro/azure-rest-api-specs that referenced this issue Dec 16, 2022
fixes Azure#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
kayousef-zz pushed a commit to kayousef-zz/azure-rest-api-specs that referenced this issue Dec 21, 2022
fixes Azure#21183

The enum values for the storage settings are listed in the latest API as `ArchiveStore, SnapshotStore, VaultStore.`
However while providing `SnapshotStore` value it fail with `BMSUserErrorInvalidInput` error. Also while trying the same from PS cmdlet using

> New-AzDataProtectionBackupVaultStorageSettingObject -DataStoreType SnapshotStore -Type LocallyRedundant

**Error:**
```
Error: "Unable to match the identifier name 
SnapshotStore to a valid enumerator name. Specify one of the following enumerator names and try again:
ArchiveStore, OperationalStore, VaultStore"
```

This PR fixes the enum value of storage setting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. DataProtection
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants