[ovirt-users] Re: Hosted Engine Setup error (oVirt v4.2.3)

This is what I had. Does this look correct?

[root@ovirt-node1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/onn_ovirt--node1-ovirt--node--ng--4.2.3--0.20180515.0+1 14G 1.8G 12G 14% / devtmpfs 32G 0 32G 0% /dev tmpfs 32G 8.0K 32G 1% /dev/shm tmpfs 32G 18M 32G 1% /run tmpfs 32G 0 32G 0% /sys/fs/cgroup /dev/sda1 976M 207M 702M 23% /boot /dev/mapper/onn_ovirt--node1-home 976M 2.6M 907M 1% /home /dev/mapper/onn_ovirt--node1-tmp 976M 2.8M 906M 1% /tmp /dev/mapper/onn_ovirt--node1-var 15G 112M 14G 1% /var /dev/mapper/onn_ovirt--node1-var_log 7.8G 42M 7.3G 1% /var/log /dev/mapper/onn_ovirt--node1-var_log_audit 2.0G 6.3M 1.8G 1% /var/log/audit /dev/mapper/onn_ovirt--node1-var_crash 9.8G 37M 9.2G 1% /var/crash tmpfs 6.3G 0 6.3G 0% /run/user/0 On 2018-05-16 06:14, Simone Tiraboschi wrote: > On Wed, May 16, 2018 at 2:52 PM, <ovirt(a)fateknollogee.com&gt; wrote: > > >> https://www.ovirt.org/documentation/install-guide/chap- > System_Requirements/ > >> [1] says: >> Important: If you are also installing the oVirt Engine Virtual >> Appliance for self-hosted engine installation, the /var partition >> must be at least 60 GB. >> > > The appliance disk is shipped as a qcow2 image: 4 GB should be enough. > > Back to the drawing board, I certainly failed to read that!! >> >> On 2018-05-16 02:37, Andrea Dell'Amico wrote: >> On 16 May 2018, at 09:42, Simone Tiraboschi <stirabos(a)redhat.com&gt; >> wrote: >> >> On Tue, May 15, 2018 at 6:31 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Engine network config error >> >> Following this blog post: >> > > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt > -4-2-and-gluster-storage/ > [2] > > > [1] >>> >>> I get an error saying the hosted engine setup is "trying" to use >>> vibr0 (192.168.xxx.x) even though I have the bridge interface set >>> to "eno1" >>> >> >> Regardless of whether the Edit Hosts File is checked or unchecked, >>> it overwrites my engine IP entry from 10.50.235.x to 192.168.xxx.x >>> >>> The same thing happens whether I set the engine IP to Static or >>> DHCP (I don't have DNS, I'm using static entries in /etc/hosts). >>> >>> Any ideas it "insists" on using "vibr0" instead of "eno1"? >>> >> >> Hi, >> up to this point is absolutely fine: in the new node zero deployment >> flow, hosted-engine-setup bootstraps a local VM with an engine there >> to use that engine to configure the rest of the system (storage, >> network...). >> That bootstrap VM runs over default natted libvirt network, that's >> why you see vibr0 and 192.168.xxx.x at that stage. >> >> If you are facing any issue, it's definitively not there. >> > > Yes, the blog post describes the 4.2.{0,1} behaviour while the local > VM is a change introduced in 4.2.2. > I faced a similar error and in my case the VM creation failed because > there was not enough space in /var/tmp. It wasn’t a problem before, > because the engine VM was created directly on top of a gluster volume. > > Andrea > -- > Andrea Dell'Amico > http://adellam. sevenseas.org/ [3] [2] > > Links: > ------ > [1] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt > -4-2-and-gluster-storage/ > [2] > [2] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > > > > Links: > ------ > [1] https://www.ovirt.org/documentation/install-guide/chap- > System_Requirements/ > [2] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt > -4-2-and-gluster-storage/ > [3] http://sevenseas.org/ >