Don't automatically initialize appliances on first-boot

[agrare]

Historically the upstream ManageIQ appliance images have been set up to automatically initialize a region and local database on first boot to allow for simpler demo / developer setup.

With this upstream image being used directly or as a basis for more production deployments, it is quite difficult to deploy an additional appliance into an existing region because you have to manually un-do all of the appliance initialization tasks that have already been done.

• https://github.com/ManageIQ/manageiq-appliance-build/pull/511
• https://github.com/ManageIQ/manageiq-appliance/pull/359
• https://github.com/ManageIQ/manageiq-documentation/pull/1675 (previous auto-init also set up a kafka broker)

[agrare]

NOTE for testing with an existing appliance image you can use libguestfs-tools to modify the qcow2 disk image, the following removes the symlink to the manageiq-initialize.service (which is the part that "enables" it on boot) and then the service itself:

guestfish -a manageiq-libvirt-devel.qc2 -i rm /etc/systemd/system/multi-user.target.wants/manageiq-initialize.service
guestfish -a manageiq-libvirt-devel.qc2 -i rm /usr/lib/systemd/system/manageiq-initialize.service