liquidmetal-dev / liquidmetal-dev/flintlock
Setting root_volume.size_in_mb seems to have no effect
Open
kind/bug
lifecycle/stale
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
It would appear we don't actually process that input and resize the volume before mounting.
cf: https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/issues/234
Contributor guide
Research direction
Start by tracing how root_volume.size_in_mb is handled before the volume is mounted, then compare the behavior with the linked cluster-api-provider-microvm issue 234. Done means the requested root volume size is processed and the volume is resized before mounting, with coverage for this input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100