© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
as for work-around: one could try to reduce size of any logical volume for os volume group by 100-200M directly inside nailgun db for every node in the cluster. Perhaps, that needs to be applied to any other volume groups (eg: logs, cinder, etc).
unfortunatelly, that couldn't be achieved by editing disks.yaml files for particular node as those files represent only high level volume roles and don't allow to change logical volume sizes of which this volume role consists of.