canonical / canonical/microcloud
`microcloud add` should exit if mandatory selections aren't made
Open
Bug
Jira
- Dominant language
- Go
- Stars
- 532
- Forks
- 83
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 36
Description
When adding a new node and the existing cluster already has distributed networking (MicroOVN) and a `local` storage pool configured, it's mandatory that an uplink network's interface and storage disk is selected also for the new systems.
Right now this is optional and will cause errors later in the setup.
Instead MicroCloud should reject such selections and force the selection of the respective resources. We already know if we are running a bootstrap operation or adding new members and can use this as the base to identify how to proceed.
Contributor guide
Assessment
This issue has not been assessed yet.