You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VMWare account that we are currently working under has 2 listed sellers on the account, VMWare and AWS and according to the endpoint https://vmc.vmware.com/api/billing/REDACTED_GUID/core/billing-accounts?is_default=false, we have both AWS and VMWare as sellers of record on our account configuration. Interestingly enough, AWS is marked as our default in the returned payload, but when we try to deploy our initial SDDC using Terraform, we end up with a failed deployment due to the following error:
com.vmware.skyscraper.common.InternalSkyscraperException: SingleAZ SDDC provisioning task REDACTED in 2-node provisioning parent task REDACTED failed in substage POST_DEPLOY_PRE_NSXT_CONFIG with the error message com.vmware.skyscraper.common.SkyscraperException: Org REDACTED has multiple SoRs. Subscription shouldve triggered from v2 service. :skyscraper.multi.sor.no.active.subscription
Reproduction steps
1. Create an organization with 2 sellers, VMWare and AWS
2. Atempt deployment of an SDDC of any size
3. The deployment fails after 90-120 minutes and the error shown above is entered into the VMC activity log.
Expected behavior
The SDDC is deployed and defaults to our default billing seller, AWS.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I've checked the code of the VMC service and it seems that there is an issue with the subscription of your organisation's billing account. This is not a problem with the Terraform provider. Please, contact VMC support and show them the error message you're getting.
@dimitarproynov While we have worked past our initial struggles with this, I still believe that it would be beneficial for the provider to be able to configure this setting:
There is nothing preventing us from having multiple SDDCs with multiple sellers in the UI and I would think that we would want the SDDC terraform provider to have the same capabilities, especially considering that importing an SDDC after creation is recipe for disaster when the SDDC gets recreated. Currently, this provider will only allow us to create an SDDC with the default seller on our account.
A little update:
The API that allows to choose a seller is part of a new VMC API collection, which is still not supported in the GoLang VMC SDK. The release of the new GoLang SDK that supports the new VMC API collection is targeted at Q2, then this new SDK has to be incorporated into this Terraform provider, which is not a small amount of work. So fix for the issue is a long way off, but we're keeping it open.
Describe the bug
The VMWare account that we are currently working under has 2 listed sellers on the account, VMWare and AWS and according to the endpoint
https://vmc.vmware.com/api/billing/REDACTED_GUID/core/billing-accounts?is_default=false
, we have both AWS and VMWare as sellers of record on our account configuration. Interestingly enough, AWS is marked as our default in the returned payload, but when we try to deploy our initial SDDC using Terraform, we end up with a failed deployment due to the following error:Reproduction steps
Expected behavior
The SDDC is deployed and defaults to our default billing seller, AWS.
Additional context
No response
The text was updated successfully, but these errors were encountered: