As a cloud administrator, it’s important to be aware of potential traps when setting up and maintaining your own Orchestrator and Gateways, especially when upgrading software versions. This blog post will discuss one such trap that was recently discovered during an update to version 4.5.x of Velocloud Orchestrator (VCO).

Background:

Velocloud Orchestrator is a cloud management platform designed to help organizations deploy and manage their cloud infrastructure. It provides features such as automated deployment, scaling, and monitoring of workloads, as well as integrated security and networking capabilities.

Recent Update Failure:

During an update to version 4.5.x of VCO, a general error occurred due to inadequate disk space. Specifically, the error message “OSError: [Errno 28] No space left on device” was displayed when attempting to upgrade the software. This issue was encountered during the installation of the updated software, which could not be completed due to the lack of available disk space.

The problem arises from the fact that some Logical Volumes (LVs) are too small, and as a result, they can quickly fill up with data. In particular, the LV for /var is only 4GB in size, which is not sufficient for the amount of data being stored.

Solution:

To resolve this issue, it is necessary to increase the disk size of the /var Logical Volume (LV) to avoid filling it quickly with data. The solution involves using the “lvextend” command to extend the size of the LV, followed by a “resize2fs” command to resize the filesystem on the LV to match the new size.

After consulting with PS from VMware, they suggested increasing the disk size of the /var LVM so that it can handle more data without filling up quickly. The solution is to use the “lvextend” command to extend the size of the LV and then use the “resize2fs” command to resize the filesystem on the LV to match the new size.

The “lvextend” command was used to extend the size of the LVM, followed by a “resize2fs” command to resize the filesystem on the LVM to match the new size. After increasing the disk size of the /var LVM from 4GB to 8GB, the upgrade worked without any issues.

Conclusion:

In conclusion, it is essential to be aware of potential traps when setting up and maintaining your own Orchestrator and Gateways, especially when upgrading software versions. This blog post highlights one such trap that was recently discovered during an update to version 4.5.x of Velocloud Orchestrator (VCO). Specifically, the issue arises from inadequate disk space due to small LVs filling up quickly with data. Increasing the disk size of the /var LVM resolved this problem by avoiding filling it quickly with data. As a result, upgrading the software was successful without any issues.