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

[Bug]: Unsupported Dedicated Storage Profile Class #615

Closed
Yobar73 opened this issue Nov 10, 2023 · 6 comments · Fixed by #711
Closed

[Bug]: Unsupported Dedicated Storage Profile Class #615

Yobar73 opened this issue Nov 10, 2023 · 6 comments · Fixed by #711
Assignees
Labels

Comments

@Yobar73
Copy link

Yobar73 commented Nov 10, 2023

Terraform Core Version

1.5.3

Cloud Avenue Provider Version

0.14.0

Affected Resource(s)

cloudavenue_vdc
maybe all resources depending storage_profile

Expected Behavior

We want to be able to import the dedicated storage profile class onto our existing infrastructure and use it into our infrastructure as code

Actual Behavior

Our existing VDC has been updated adding the dedicate storage profile. When we try to import the VDC updated by Orange, we have an issue "Unsupported Dedicated Storage Profile Class silver_xxxxxxxxxx"

Relevant Error/Panic Output Snippet

╷
│ Error: Unsupported Dedicated Storage Profile Class (HTTP Code => 400)
│ 
│   with cloudavenue_vdc.my_vdc,
│   on file.tf line xx, in resource "cloudavenue_vdc" "my_vdc":
│   31: resource "cloudavenue_vdc" "my_vdc" {
│ 
│ Unsupported Dedicated Storage Profile Class silver_xxxxxxxx
╵

Terraform Configuration Files

terraform {
  required_providers {
    cloudavenue = {
      source  = "orange-cloudavenue/cloudavenue"
    }
    vcd = {
      source  = "vmware/vcd"
    }
  }
}

provider "cloudavenue" {
}
provider "vcd" {
}

Steps to Reproduce

Ask to Orange to add a dedicated storage profile onto your VDC and try to import it

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@Yobar73 Yobar73 added the bug Something isn't working label Nov 10, 2023
@azrod
Copy link
Member

azrod commented Nov 13, 2023

Hi @Yobar73 👋
Thank you for reporting this issue and sorry you are running into this unexpected behavior.

Please provide your terraform configuration for the resource "cloudavenue_vdc" "my_vdc"

We support this issue and will let you know when the fix is ​​released.

@Yobar73
Copy link
Author

Yobar73 commented Nov 13, 2023

@azrod See below my current resource definition for cloudavenue_vdc:

resource "cloudavenue_vdc" "my_vdc" {
  name                  = "my_vdc"
  description           = "My main VDC"
  cpu_allocated         = 2600
  memory_allocated      = 120
  cpu_speed_in_mhz      = 1200
  billing_model         = "RESERVED"
  disponibility_class   = "ONE-ROOM"
  service_class         = "STD"
  storage_billing_model = "RESERVED"

  storage_profiles = [
            {
                class   = "silver"
                default = true
                limit   = 100
            },
            {
                class   = "platinum7k"
                default = false
                limit   = 100
            }
        ]
}

As I said, Orange added our dedicated storage profile named silver_xxxxxxxxxx onto my_vdc. Now, when I run terraform plan, it returns the previous error.

Ask me if you want more context.

@azrod
Copy link
Member

azrod commented Nov 13, 2023

@Yobar73 thanks for your feedback.
After investigation the problem il know in CloudAvenue API and the issue has been priorized in backlog.

Once the API is corrected we will quickly make the necessary changes in the terraform provider.

@Yobar73
Copy link
Author

Yobar73 commented Jan 30, 2024

@azrod Do you have any news on the correction of this bug on CloudAvenue API?

@azrod
Copy link
Member

azrod commented Jan 31, 2024

Hi @Yobar73,

This bug has fixed last week in the CloudAvenue API. We working on implement change on terraform provider. We will publish a new release soon with the fix.

@azrod azrod linked a pull request Jan 31, 2024 that will close this issue
3 tasks
@azrod
Copy link
Member

azrod commented Jan 31, 2024

🚀 Release v0.18.0

Hi @Yobar73. The terraform provider has been release. This release contains the fix of your bug. Please try this release. Do not hesitate to re-open issue if your bug is not fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants