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_iops doesn't work #1179

Closed
kr008 opened this issue Aug 23, 2024 · 0 comments · Fixed by #1198
Closed

volume_iops doesn't work #1179

kr008 opened this issue Aug 23, 2024 · 0 comments · Fixed by #1198

Comments

@kr008
Copy link

kr008 commented Aug 23, 2024

Describe the bug

Setting volume_iops the value is not set in config.toml.
In template file runner-docker-machine-config.tftpl there is no corresponding iops parameter.

To Reproduce

Install Plugin version: 7.13.1

Configuration plugin:

runner_worker_docker_machine_instance = {
description = "runner-1"
private_address_only = false
destroy_after_max_builds = 30
idle_count = var.runners_idle_count
idle_time = 600
max_growth_rate = 10
monitoring = true
private_address_only = true
root_size = 40
subnet_ids = [var.subnet_private_c_id]
types = var.runner_instance_type
volume_type = "io2"
volume_iops = 6000
}

runner_worker = {
type = "docker+machine"
}

@kr008 kr008 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2024
@kr008 kr008 reopened this Aug 23, 2024
kayman-mk added a commit that referenced this issue Oct 21, 2024
…r_machine_fleet.enabled = true` (#1198)

## Description

The `runner_worker_docker_machine_instance.volume_iops` does not work
for the docker+machine driver, but works for the fleeting mode which can
be enabled via `runner_worker_docker_machine_fleet.enabled = true`. We
amend the comment to make that clear.

Closes #1179
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant