NGINX Virtual Machine Building with cloud-init
Traditionally, building new servers was a manual process. A system administrator had a run book with all the steps required and would perform each task one by one. If the admin had multiple servers to build the same steps were repeated over and over. All public cloud compute platforms provide an automation tool called cloud-init that makes it easy to automate configuration tasks while a new VM instance is being launched. In this article, you will learn how to automate the process of building out a new NGINX Plus server usingcloud-init.Installation of 14.1.2.6 fails
Hi All, We have two customers which are trying to install 14.1.2.6 on a partition prior to upgrade from 14.1.2.5. But the installation fails right away with the following erros in /var/log/liveinstall.log *** Live install start at 2020/07/06 18:08:23 *** info: tm_install::BootLoader::BootLoader_mboot_sync_from_old_conf -- Configurations match. info: Daemon-driven execution indicated by ENV variable. info: Repository tm_install version/release is 2.12.0.6/4.0 info: System tm_install version/release is 2.12.0.6/4.0 info: Platform id is C117 /dev/sdd: No medium found sfdisk: cannot open /dev/sdd for reading info: Basic disk format validation passed. info: >++++ result: info: mount: /dev/mapper/vg--db--sda-set.2._usr is already mounted or /mnt/tm_install/30655.GyI1Fy/usr busy info: /dev/mapper/vg--db--sda-set.2._usr is already mounted on /usr info: /dev/mapper/vg--db--sda-set.2._usr is already mounted on /opt/.sdm/usr info: /dev/mapper/vg--db--sda-set.2._usr is already mounted on /opt/.sdm/lib info: /dev/mapper/vg--db--sda-set.2._usr is already mounted on /opt/.sdm/lib64 info: >---- error: status 8192 returned by command: mount -oro /dev/vg-db-sda/set.2._usr /mnt/tm_install/30655.GyI1Fy/usr 2>/dev/null info: >++++ result: info: umount: /mnt/tm_install/30655.GyI1Fy/shared: not mounted info: >---- error: status 8192 returned by command: umount /mnt/tm_install/30655.GyI1Fy/shared Terminal error: Could not access configuration source; sda, 2 *** Live install end at 2020/07/06 18:08:27: failed (return code 2) *** I could not find anything related in the F5 knowledge base articles. Customer already tried to delete an create a partition again, but this did not solve the issue. Anyone else facing the same issue? Anyone has a solution? Regards, Martijn
