Archy's Blog

Sometimes it turns out, your initial sizing of a VM might have been too small. While RAM and CPU can easily be extended, Disk, on the other hand, might be a different story but usually, the process is rather simple. This is how I tend to do extend a disk that is used by LVM. First, resize the VM's disk on the hypervisor, note that this command is specific for KVM [archy@hyv01 ~]$ sudo virsh blockresize --domain repo.archyslife.lan --path /srv/kvm/vm-images/repo.archyslife.lan-disk1.qcow2 --size 250G You can verify your changes by running this command [root@hyv01 ~]# sudo virsh domblkinfo --domain repo.archyslife.lan --device vda --human Capacity: 250.000 GiB Allocation: 199.435 GiB Physical: 250.000 GiB If you are using virtio (like me in this example), the disk should automatically be resized in the VM and you can continue to resize the partition or physical volume. If you're resizing a SATA / SAS / SCSI Disk, you'll have to make the VM resca...

The upgrade between minor versions is fairly simple with Zimbra since the install.sh script covers everything with its interactive installer. First, download the archive used for the installation and unpack it. [archy@zimbra ~]$ curl -O https://files.zimbra.com/downloads/8.8.15_GA/zcs-8.8.15_GA_3869.RHEL7_64.20190918004220.tgz [archy@zimbra ~]$ tar -xvzf zcs-8.8.15_GA_3869.RHEL7_64.20190918004220.tgz I'd recommend moving the installation to tmux (or screen) so that in case of a disconnect, the installation will not break anything and you could just detach / attach to the session. You can create a new tmux session by running [archy@zimbra ~]$ tmux new -s zimbra-upgrade Now switch into the directory where the packages have been unpacked to and run the interactive install.sh [archy@zimbra ~]$ cd zcs-8.8.15_GA_3869.RHEL7_64.20190918004220 [archy@zimbra ~]$ sudo ./install.sh ... Use Zimbra's packaging server? [Y]: y ... Do you with to upgrade? [Y]...

Under certain circumstances, it can happen that foreman's components get out of sync and hosts cannot be registered / unregistered anymore. I've had this problem recently with a pulp upgrade in foreman 1.24.2 and pulp packages: pulp-deb-plugins-1.10.1-1.el7.noarch pulp-docker-plugins-3.2.6-1.el7.noarch pulp-puppet-plugins-2.21.1-1.el7.noarch pulp-puppet-tools-2.21.1-1.el7.noarch pulp-rpm-plugins-2.21.1-1.el7.noarch pulp-selinux-2.21.1-1.el7.noarch pulp-server-2.21.1-1.el7.noarch python-pulp-common-2.21.1-1.el7.noarch python-pulp-deb-common-1.10.1-1.el7.noarch python-pulp-docker-common-3.2.6-1.el7.noarch python-pulp-oid_validation-2.21.1-1.el7.noarch python-pulp-puppet-common-2.21.1-1.el7.noarch python-pulp-repoauth-2.21.1-1.el7.noarch python-pulp-rpm-common-2.21.1-1.el7.noarch python-pulp-streamer-2.21.1-1.el7.noarch The result was an 'Error 500' when trying to unregister a host. In order to fix this, you'll need to rerun the installer for f...