[BUG] The default values can't be changed in cluster config file for virtual machine.
See original GitHub issueDescribe the bug It is not possible to change default values in configuration section for infrastructure/virtual-machine such as:
- disk_size_gb
- offer
- sku etc… in cluster config file. Terraform use always default ones.
How to reproduce Steps to reproduce the behavior:
- execute
epicli init ... (with params)
- edit config file and change default os_disk_size or os image
- execute
epicli apply ...
Expected behavior I would like to create cluster with the values which I set in my configuration file. If I set 64GB os disk size, I would like to have 64GB os disk size, not the default 32GB
Config files
---
kind: infrastructure/virtual-machine
title: Virtual Machine Infra
provider: azure
name: default
specification:
tags: []
os_type: linux
size: Standard_DS1_v2
storage_image_reference:
publisher: Canonical
offer: UbuntuServer
sku: 18_04-lts-gen2
version: 18.04.202101290
storage_os_disk:
delete_on_termination: false
managed: false
caching: ReadWrite
create_option: FromImage
disk_size_gb: 64
managed_disk_type: Premium_LRS
Environment
- Cloud provider: [AWS | Azure]
- OS: [all]
epicli version: 0.9
Additional context Add any other context about the problem here.
DoD checklist
- Changelog updated (if affected version was released)
- COMPONENTS.md updated / doesn’t need to be updated
- Automated tests passed (QA pipelines)
- apply
- upgrade
- Case covered by automated test (if possible)
- Idempotency tested
- Documentation updated / doesn’t need to be updated
- All conversations in PR resolved
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
The Default Virtual Machine Configuration Store Cannot be ...
I am trying to change the default virtual machine configuration store from within the hyper-v settings to a SMB 3.0 share.
Read more >2000770 – Failed to Change Cluster settings - Red Hat Bugzilla
To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the...
Read more >Changed Block Tracking (CBT) on virtual machines (1020128)
Right-click the virtual machine and navigate to Edit Settings > Options > Advanced/General > Configuration Parameters. CBT Changed Block ...
Read more >How to Fix the Error Hyper-V failed to Change State - NAKIVO
This blog post explains possible reasons for the “Hyper-V failed to change state” error and the methods available for resolving this issue.
Read more >8.128 Editing Virtual Machine Configuration File Results in ...
For example, if you edit the HA setting in the vm.cfg to disable HA, and the virtual machine is stopped by any method...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rpudlowski93 For now, the only option to change these parameters is to provide the configuration for each vm like this:
✔️ Fixed. Now we can easily change the default values for
OS image
,vm size
,disk size
, etc.