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

volume_type conflicts with "local_type = false" in mks nodegroup #300

Open
MaxOinRU opened this issue Sep 13, 2024 · 2 comments · May be fixed by #303
Open

volume_type conflicts with "local_type = false" in mks nodegroup #300

MaxOinRU opened this issue Sep 13, 2024 · 2 comments · May be fixed by #303

Comments

@MaxOinRU
Copy link

MaxOinRU commented Sep 13, 2024

Terraform Version

Terraform v1.7.4

Affected Resource(s)

  • selectel_mks_nodegroup_v1

Terraform Configuration Files

resource "selectel_mks_nodegroup_v1" "nodegroup_1" {
  ...
  volume_gb           = 50
  local_volume        = false
  volume_type         = fast.ru-7b
  ...
}  

Expected Behavior

local_volume = false don`t conflicts with not null volume_type

Actual Behavior

│ Error: Conflicting configuration arguments
│ 
│   with module.kubernetes_nodegroup_with_flavour.selectel_mks_nodegroup_v1.nodegroup_1,
│   on ../../terraform/global_router/modules/mks/nodegroup/main.tf line 16, in resource "selectel_mks_nodegroup_v1" "nodegroup_1":
│   16:   volume_type         = "fast.ru-7b"
│ 
│ "volume_type": conflicts with local_volume

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. Set local_volume = false, and not null volume_type
  2. terraform plan
@TawR1024
Copy link
Collaborator

@MaxOinRU, hi, please specify which version of terraform-provider-selectel do you use ?

@MaxOinRU
Copy link
Author

@MaxOinRU, hi, please specify which version of terraform-provider-selectel do you use ?

@TawR1024, version 4.1.1

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

Successfully merging a pull request may close this issue.

2 participants