On Tue, May 15, 2018 at 6:31 PM, <ovirt(a)fateknollogee.com&gt; wrote: 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.

Andrea, how much space was needed in /var/tmp? 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-glus... >>> [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/ [2] > > > > Links: > ------ > [1] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [2] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org

https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ 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. 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-glus... >>> [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/ [2] > > > > Links: > ------ > [1] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [2] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org

Andrea, thx for the info. I certainly did not have anywhere close to 55GB for /var I will fix that & report back. On 2018-05-16 06:01, Andrea Dell'Amico wrote: >> On 16 May 2018, at 14:52, ovirt(a)fateknollogee.com wrote: >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> 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. > > I remember it used just a bit less, around 55/56GB. > >> Back to the drawing board, I certainly failed to read that!! > > It’s temporary, so you can add a disk and mount it into /var/tmp to > complete the installation and remove it when finished. The VM is > created locally, then moved to gluster and started with its final > configuration. > > Andrea > >> 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-glus... > >>> [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 [1].sevenseas.org/ [2] [2] > Links: > ------ > [1] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [2] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > -- > Andrea Dell'Amico > http://adellam.sevenseas.org/ [2] > > > > Links: > ------ > [1] http://adellam/ > [2] http://sevenseas.org/

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-glus... > [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-glus... > [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-glus... > [3] http://sevenseas.org/

Simone, unfortunately I deleted that install after it failed. I can re-run the install based on the df -h (see previous post) or I can change disks & increase the size of /var then re-run the install. What do you think? The error I was getting said it could not find the hosted engine at vibr0 on 192.168.xxx.xx On 2018-05-16 06:30, Simone Tiraboschi wrote: > On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: > >> This is what I had. >> Does this look correct? > > Yes, I think so. > > can you please share your hosted-engine-setup log file to understand > where it's failing? > >> [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] >> [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-glus... >> [2] >> [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] [3] [2] > > Links: > ------ > [1] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [2] > [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/ > [1] > [2] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [2] > [3] http://sevenseas.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-glus... > [3] http://sevenseas.org/

I will get the logs. Here is the exact error message: [ ERROR ] fatal: [ovirt-engine.fateknollogee.com]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added 'ovirt-engine.fateknollogee.com,192.168.124.198' (ECDSA) to the list of known hosts.\r\nPermission denied (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", "unreachable": true} On 2018-05-16 07:04, Simone Tiraboschi wrote: > On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: > >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx > > On my opinion you could simply retry. > Please share your log file it fails again. > >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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] >> [1] >> [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-glus... >> [2] >> [2] >> [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] [3] [3] [2] >> >> Links: >> ------ >> [1] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [2] >> [2] >> [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/ >> [1] >> [1] >> [2] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [1] >> [2] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [2] >> [3] http://sevenseas.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-glus... > [3] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org

On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: Can you please try with a different more robust password? The log file is under /var/log/ovirt-hosted-engine-setup

Some good news... Hosted Engine Deployment "preparing the vm" completed. I used a simpler password. When I got the previous errors, my password was 12 characters (upper, lower case & numbers) long with a %% (double percent) before and after the characters. I guess it didn't like the double percent!!! Let me continue, I will report back. On 2018-05-17 00:30, Simone Tiraboschi wrote: > On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: > >> More info: >> From my ovirt node (host) I can ping 192.168.124.198 >> If I try to connect via ssh root(a)192.168.124.198, it asks for a >> password. >> The password I used during the hosted engine setup does not work. > > Can you please try with a different more robust password? > The log file is under /var/log/ovirt-hosted-engine-setup > >> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >> I will get the logs. >> >> Here is the exact error message: >> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [1]]: UNREACHABLE! >> => >> {"changed": false, "msg": "Failed to connect to the host via ssh: >> Warning: Permanently added >> 'ovirt-engine.fateknollogee.com [1],192.168.124.198' (ECDSA) to the >> list >> of known hosts.\r\nPermission denied >> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >> "unreachable": true} >> >> On 2018-05-16 07:04, Simone Tiraboschi wrote: >> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx >> >> On my opinion you could simply retry. >> Please share your log file it fails again. >> >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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/ >> [2] >> [1] >> [1] >> [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-glus... >> [3] >> [2] >> [2] >> [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/ [4] [3] [3] [3] [2] >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [3] >> [2] >> [2] >> [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] >> [1] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [3] >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [2] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [3] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [2] >> [2] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [3] >> [3] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > > > > Links: > ------ > [1] http://ovirt-engine.fateknollogee.com > [2] > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ > [3] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [4] http://sevenseas.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org

Yesterday, that install failed because I did not have the required 60GB for /var. Today, I started from scratch & re-installed the oVirt nodes. That install also failed. I've attached the logs via dropbox link https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 On 2018-05-17 01:55, ovirt(a)fateknollogee.com wrote: > Some good news... > Hosted Engine Deployment "preparing the vm" completed. > I used a simpler password. > When I got the previous errors, my password was 12 characters (upper, > lower case & numbers) long with a %% (double percent) before and after > the characters. > I guess it didn't like the double percent!!! > Let me continue, I will report back. > > On 2018-05-17 00:30, Simone Tiraboschi wrote: >> On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >>> More info: >>> From my ovirt node (host) I can ping 192.168.124.198 >>> If I try to connect via ssh root(a)192.168.124.198, it asks for a >>> password. >>> The password I used during the hosted engine setup does not work. >> >> Can you please try with a different more robust password? >> The log file is under /var/log/ovirt-hosted-engine-setup >> >>> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >>> I will get the logs. >>> >>> Here is the exact error message: >>> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [1]]: UNREACHABLE! >>> => >>> {"changed": false, "msg": "Failed to connect to the host via ssh: >>> Warning: Permanently added >>> 'ovirt-engine.fateknollogee.com [1],192.168.124.198' (ECDSA) to the >>> list >>> of known hosts.\r\nPermission denied >>> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >>> "unreachable": true} >>> >>> On 2018-05-16 07:04, Simone Tiraboschi wrote: >>> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >>> >>> Simone, unfortunately I deleted that install after it failed. >>> I can re-run the install based on the df -h (see previous post) or I >>> can change disks & increase the size of /var then re-run the >>> install. >>> What do you think? >>> The error I was getting said it could not find the hosted engine at >>> vibr0 on 192.168.xxx.xx >>> >>> On my opinion you could simply retry. >>> Please share your log file it fails again. >>> >>> On 2018-05-16 06:30, Simone Tiraboschi wrote: >>> >>> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >>> >>> This is what I had. >>> Does this look correct? >>> >>> Yes, I think so. >>> >>> can you please share your hosted-engine-setup log file to understand >>> where it's failing? >>> >>> [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/ >>> [2] >>> [1] >>> [1] >>> [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-glus... >>> [3] >>> [2] >>> [2] >>> [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/ [4] [3] [3] [3] [2] >>> >>> Links: >>> ------ >>> [1] >>> >>> >> https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >>> [3] >>> [2] >>> [2] >>> [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] >>> [1] >>> [1] >>> [2] >>> >>> >> https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >>> [3] >>> [2] >>> [2] >>> [3] http://sevenseas.org/ >>> >>> Links: >>> ------ >>> [1] >>> >>> >> https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >>> [2] >>> [1] >>> [2] >>> >>> >> https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >>> [3] >>> [2] >>> [3] http://sevenseas.org/ >>> >>> Links: >>> ------ >>> [1] >>> >> https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >>> [2] >>> [2] >>> >> https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >>> [3] >>> [3] http://sevenseas.org/ >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> >> >> Links: >> ------ >> [1] http://ovirt-engine.fateknollogee.com >> [2] >> https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [3] >> https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org

Simone, do see any other failures before the MAC error? When the deployment failed, I tried to run it again then it gave me the MAC error. The first time it failed there was no error message, it just stopped & said 'deployment failed' On 2018-05-18 00:09, Simone Tiraboschi wrote: > Hi, > it fails due to > > ERROR The MAC address '00:16:3E:6A:7A:F9' is in use by another > virtual machine. > > and this is probably due to a leftover VM from a previous attempt. > > It's tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1576451 > and it will be properly fixed with the next release. > > In the mean time can you please manually undefine your leftover > HostedEngine VM from your env? > > /usr/bin/virsh -c > qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf > undefine HostedEngine > > should do the job. > > On Fri, May 18, 2018 at 6:46 AM, <ovirt(a)fateknollogee.com&gt; wrote: > >> Yesterday, that install failed because I did not have the required >> 60GB for /var. >> >> Today, I started from scratch & re-installed the oVirt nodes. >> That install also failed. >> I've attached the logs via dropbox link >> > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [1] >> >> On 2018-05-17 01:55, ovirt(a)fateknollogee.com wrote: >> >> Some good news... >> Hosted Engine Deployment "preparing the vm" completed. >> I used a simpler password. >> When I got the previous errors, my password was 12 characters >> (upper, >> lower case & numbers) long with a %% (double percent) before and >> after >> the characters. >> I guess it didn't like the double percent!!! >> Let me continue, I will report back. >> >> On 2018-05-17 00:30, Simone Tiraboschi wrote: >> On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> More info: >> From my ovirt node (host) I can ping 192.168.124.198 >> If I try to connect via ssh root(a)192.168.124.198, it asks for a >> password. >> The password I used during the hosted engine setup does not work. >> >> Can you please try with a different more robust password? >> The log file is under /var/log/ovirt-hosted-engine-setup >> >> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >> I will get the logs. >> >> Here is the exact error message: >> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [2] [1]]: >> UNREACHABLE! >> => >> {"changed": false, "msg": "Failed to connect to the host via ssh: >> Warning: Permanently added >> 'ovirt-engine.fateknollogee.com [2] [1],192.168.124.198' (ECDSA) to >> the >> list >> of known hosts.\r\nPermission denied >> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >> "unreachable": true} >> >> On 2018-05-16 07:04, Simone Tiraboschi wrote: >> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx >> >> On my opinion you could simply retry. >> Please share your log file it fails again. >> >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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/ >> [3] >> [2] >> [1] >> [1] >> [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-glus... >> [4] >> [3] >> [2] >> [2] >> [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/ [5] [4] [3] [3] [3] [2] >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] >> [3] >> [2] >> [2] >> [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/ >> [3] >> [2] >> [1] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] >> [3] >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [3] >> [2] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] >> [3] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [3] >> [2] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] >> [3] >> [3] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> Links: >> ------ >> [1] http://ovirt-engine.fateknollogee.com [2] >> [2] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [3] >> [3] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [4] >> [4] 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.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 > [2] http://ovirt-engine.fateknollogee.com > [3] > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ > [4] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [5] http://sevenseas.org/

Thanks for the info. Unfortunately, I do not have the ovirt-node3 logs since I deleted all 3 nodes. I have now re-installed ovirt node on all 3 hosts. I will double check that hosts can resolve each other. Any other advise (or things to check) before I re-try Hosted Engine Setup? On 2018-05-18 00:46, Simone Tiraboschi wrote: > On Fri, May 18, 2018 at 9:14 AM, <ovirt(a)fateknollogee.com&gt; wrote: > >> Simone, do see any other failures before the MAC error? >> When the deployment failed, I tried to run it again then it gave me >> the MAC error. >> The first time it failed there was no error message, it just stopped >> & said 'deployment failed' > > On the previous attempt it failed on 'Add additional gluster hosts to > engine' on ovirt-node3.fateknollogee.com [7]; not sure on what really > failed there but we need engine.log and host-deploy logs for that host > but I suspect you don't have them anymore since they were on that > engine VM. > > 'Add additional gluster hosts to engine' is one of latest steps, > anything else before that was fine. > > Adding also Gobinda here. > > Just as an hint, are you sure that ovirt-node3.fateknollogee.com [7] > could be properly resolved on your engine VM? > >> On 2018-05-18 00:09, Simone Tiraboschi wrote: >> Hi, >> it fails due to >> >> ERROR The MAC address '00:16:3E:6A:7A:F9' is in use by another >> virtual machine. >> >> and this is probably due to a leftover VM from a previous attempt. >> >> It's tracked here: >> https://bugzilla.redhat.com/show_bug.cgi?id=1576451 [1] >> and it will be properly fixed with the next release. >> >> In the mean time can you please manually undefine your leftover >> HostedEngine VM from your env? >> >> /usr/bin/virsh -c >> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf >> undefine HostedEngine >> >> should do the job. >> >> On Fri, May 18, 2018 at 6:46 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Yesterday, that install failed because I did not have the required >> 60GB for /var. >> >> Today, I started from scratch & re-installed the oVirt nodes. >> That install also failed. >> I've attached the logs via dropbox link >> >> > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [2] >> [1] >> >> On 2018-05-17 01:55, ovirt(a)fateknollogee.com wrote: >> >> Some good news... >> Hosted Engine Deployment "preparing the vm" completed. >> I used a simpler password. >> When I got the previous errors, my password was 12 characters >> (upper, >> lower case & numbers) long with a %% (double percent) before and >> after >> the characters. >> I guess it didn't like the double percent!!! >> Let me continue, I will report back. >> >> On 2018-05-17 00:30, Simone Tiraboschi wrote: >> On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> More info: >> From my ovirt node (host) I can ping 192.168.124.198 >> If I try to connect via ssh root(a)192.168.124.198, it asks for a >> password. >> The password I used during the hosted engine setup does not work. >> >> Can you please try with a different more robust password? >> The log file is under /var/log/ovirt-hosted-engine-setup >> >> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >> I will get the logs. >> >> Here is the exact error message: >> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [3] [2] [1]]: >> UNREACHABLE! >> => >> {"changed": false, "msg": "Failed to connect to the host via ssh: >> Warning: Permanently added >> 'ovirt-engine.fateknollogee.com [3] [2] [1],192.168.124.198' >> (ECDSA) to >> >> the >> list >> of known hosts.\r\nPermission denied >> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >> "unreachable": true} >> >> On 2018-05-16 07:04, Simone Tiraboschi wrote: >> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx >> >> On my opinion you could simply retry. >> Please share your log file it fails again. >> >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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/ >> [4] >> [3] >> [2] >> [1] >> [1] >> [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-glus... >> [5] >> [4] >> >> [3] >> [2] >> [2] >> [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/ [6] [5] [4] [3] [3] [3] [2] >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [2] >> [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/ >> [4] >> [3] >> [2] >> [1] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [2] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [2] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [3] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> Links: >> ------ >> [1] http://ovirt-engine.fateknollogee.com [3] [2] >> [2] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [3] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [4] 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.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [2] >> [2] http://ovirt-engine.fateknollogee.com [3] >> [3] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [4] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [5] http://sevenseas.org/ > > > > Links: > ------ > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1576451 > [2] > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 > [3] http://ovirt-engine.fateknollogee.com > [4] > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ > [5] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [6] http://sevenseas.org/ > [7] http://ovirt-node3.fateknollogee.com

"the engine VM has to correctly resolve the address of all the three hosts" How can I make sure this happens? During the deployment I don't have access to the engine vm? Do I need some additional records in DNS? On 2018-05-18 00:56, Simone Tiraboschi wrote: > On Fri, May 18, 2018 at 9:54 AM, <ovirt(a)fateknollogee.com&gt; wrote: > >> Thanks for the info. >> Unfortunately, I do not have the ovirt-node3 logs since I deleted >> all 3 nodes. >> I have now re-installed ovirt node on all 3 hosts. >> I will double check that hosts can resolve each other. > > All hosts should correctly resolve the engine VM fqdn, the engine VM > has to correctly resolve the address of all the three hosts. > >> Any other advise (or things to check) before I re-try Hosted Engine >> Setup? > > Nothing special on my side. > >> On 2018-05-18 00:46, Simone Tiraboschi wrote: >> On Fri, May 18, 2018 at 9:14 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, do see any other failures before the MAC error? >> When the deployment failed, I tried to run it again then it gave me >> the MAC error. >> The first time it failed there was no error message, it just stopped >> & said 'deployment failed' >> >> On the previous attempt it failed on 'Add additional gluster hosts >> to >> engine' on ovirt-node3.fateknollogee.com [1] [7]; not sure on what >> really >> failed there but we need engine.log and host-deploy logs for that >> host >> but I suspect you don't have them anymore since they were on that >> engine VM. >> >> 'Add additional gluster hosts to engine' is one of latest steps, >> anything else before that was fine. >> >> Adding also Gobinda here. >> >> Just as an hint, are you sure that ovirt-node3.fateknollogee.com >> [1] [7] >> could be properly resolved on your engine VM? >> >> On 2018-05-18 00:09, Simone Tiraboschi wrote: >> Hi, >> it fails due to >> >> ERROR The MAC address '00:16:3E:6A:7A:F9' is in use by another >> virtual machine. >> >> and this is probably due to a leftover VM from a previous attempt. >> >> It's tracked here: >> https://bugzilla.redhat.com/show_bug.cgi?id=1576451 [2] [1] >> and it will be properly fixed with the next release. >> >> In the mean time can you please manually undefine your leftover >> HostedEngine VM from your env? >> >> /usr/bin/virsh -c >> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf >> undefine HostedEngine >> >> should do the job. >> >> On Fri, May 18, 2018 at 6:46 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Yesterday, that install failed because I did not have the required >> 60GB for /var. >> >> Today, I started from scratch & re-installed the oVirt nodes. >> That install also failed. >> I've attached the logs via dropbox link >> >> > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [3] >> [2] >> [1] >> >> On 2018-05-17 01:55, ovirt(a)fateknollogee.com wrote: >> >> Some good news... >> Hosted Engine Deployment "preparing the vm" completed. >> I used a simpler password. >> When I got the previous errors, my password was 12 characters >> (upper, >> lower case & numbers) long with a %% (double percent) before and >> after >> the characters. >> I guess it didn't like the double percent!!! >> Let me continue, I will report back. >> >> On 2018-05-17 00:30, Simone Tiraboschi wrote: >> On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> More info: >> From my ovirt node (host) I can ping 192.168.124.198 >> If I try to connect via ssh root(a)192.168.124.198, it asks for a >> password. >> The password I used during the hosted engine setup does not work. >> >> Can you please try with a different more robust password? >> The log file is under /var/log/ovirt-hosted-engine-setup >> >> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >> I will get the logs. >> >> Here is the exact error message: >> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [4] [3] [2] [1]]: >> UNREACHABLE! >> => >> {"changed": false, "msg": "Failed to connect to the host via ssh: >> Warning: Permanently added >> 'ovirt-engine.fateknollogee.com [4] [3] [2] [1],192.168.124.198' >> >> (ECDSA) to >> >> the >> list >> of known hosts.\r\nPermission denied >> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >> "unreachable": true} >> >> On 2018-05-16 07:04, Simone Tiraboschi wrote: >> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx >> >> On my opinion you could simply retry. >> Please share your log file it fails again. >> >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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/ >> [5] >> [4] >> [3] >> [2] >> [1] >> [1] >> [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-glus... >> [6] >> [5] >> >> [4] >> >> [3] >> [2] >> [2] >> [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/ [7] [6] [5] [4] [3] [3] [3] [2] >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [4] >> [3] >> [2] >> [2] >> [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/ >> [5] >> [4] >> [3] >> [2] >> [1] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [4] >> [3] >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [5] >> [4] >> [3] >> [2] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [4] >> [3] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [5] >> [4] >> [3] >> [2] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [4] >> [3] >> [3] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> Links: >> ------ >> [1] http://ovirt-engine.fateknollogee.com [4] [3] [2] >> [2] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [5] >> [4] >> [3] >> [3] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [4] >> [4] 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.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [3] >> [2] >> [2] http://ovirt-engine.fateknollogee.com [4] [3] >> [3] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [5] >> [4] >> [4] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [5] >> [5] http://sevenseas.org/ >> >> Links: >> ------ >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1576451 [2] >> [2] >> > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [3] >> [3] http://ovirt-engine.fateknollogee.com [4] >> [4] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [5] >> [5] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [6] >> [6] http://sevenseas.org/ >> [7] http://ovirt-node3.fateknollogee.com [1] > > > > Links: > ------ > [1] http://ovirt-node3.fateknollogee.com > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1576451 > [3] > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 > [4] http://ovirt-engine.fateknollogee.com > [5] > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ > [6] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [7] http://sevenseas.org/

On Mon, May 21, 2018 at 7:41 AM, <ovirt(a)fateknollogee.com&gt; wrote: We had a bug in the past ( https://bugzilla.redhat.com/show_bug.cgi?id=1528253 ) but we never really reproduced it, better to double check. Can you please provide an example of password that make it failing? I'm pretty sure that DHCP based configuration are correctly working, I'd suggest to double check your DHCP server.

On Mon, 2018-05-21 at 01:18 -0700, ovirt(a)fateknollogee.com wrote: #meetoo ;) /K > > > > On 2018-05-21 01:07, Simone Tiraboschi wrote: > > > > On Mon, May 21, 2018 at 7:41 AM, <ovirt(a)fateknollogee.com&gt; wrote: > > > > > > > > I finally got it to install...all green lights!! > > > > > > Thanks to Simone and Squeakz (on IRC) for all the help. > > > I have a few follow up questions, I'll post them in a new email > > > thread. > > > > > > Do not: > > > (these 2 items seemed to be the main cause of my deployment > > > errors) > > > -use special characters in any of your passwords - letters & > > > numbers > > > only. > > We had a bug in the past ( > > https://bugzilla.redhat.com/show_bug.cgi?id=1528253 ) but we never > > really reproduced it, better to double check. > > Can you please provide an example of password that make it failing? > > > > > > > > -hosted engine vm - assign static IP, no dhcp reservation. > > I'm pretty sure that DHCP based configuration are correctly > > working, > > I'd suggest to double check your DHCP server. > > > > > > > > On 2018-05-18 00:56, Simone Tiraboschi wrote: > > > On Fri, May 18, 2018 at 9:54 AM, <ovirt(a)fateknollogee.com&gt; wrote: > > > > > > Thanks for the info. > > > Unfortunately, I do not have the ovirt-node3 logs since I deleted > > > all 3 nodes. > > > I have now re-installed ovirt node on all 3 hosts. > > > I will double check that hosts can resolve each other. > > > > > > All hosts should correctly resolve the engine VM fqdn, the engine > > > VM > > > has to correctly resolve the address of all the three hosts. > > > > > > Any other advise (or things to check) before I re-try Hosted > > > Engine > > > Setup? > > > > > > Nothing special on my side. > > > > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org

Does the MAC address ever change during the deployment process? What is meant by "proper MAC reservation"? On 2018-05-21 01:35, Martin Sivak wrote: > Hi, > >> It failed with a password like this ##ZtHouse1234## > > I smell an issue with the Ansible var file we use to pass the password > into the job. We should probably base64 encode it or something. > >> With DHCP, the deployment failed when it was trying to add the gluster >> host. >> Once I changed the engine to static, the deployment passed. > > DHCP is tricky as you need to make sure that the FQDN always matches > the same VM (proper MAC, DNS and DHCP reservation come into play). But > this is the default for all installs I did and always worked fine. > > Best regards > > Martin Sivak > > On Mon, May 21, 2018 at 10:18 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> It failed with a password like this ##ZtHouse1234## >> I changed the password to ZtHouse1234 & the error went away. >> >> With DHCP, the deployment failed when it was trying to add the gluster >> host. >> Once I changed the engine to static, the deployment passed. >> >> Also Squeakz (on ovirt channel - IRC) said he has also seen the >> problem with >> dhcp. >> >> >> >> >> On 2018-05-21 01:07, Simone Tiraboschi wrote: >>> >>> On Mon, May 21, 2018 at 7:41 AM, <ovirt(a)fateknollogee.com&gt; wrote: >>> >>>> I finally got it to install...all green lights!! >>>> >>>> Thanks to Simone and Squeakz (on IRC) for all the help. >>>> I have a few follow up questions, I'll post them in a new email >>>> thread. >>>> >>>> Do not: >>>> (these 2 items seemed to be the main cause of my deployment errors) >>>> -use special characters in any of your passwords - letters & numbers >>>> only. >>> >>> >>> We had a bug in the past ( >>> https://bugzilla.redhat.com/show_bug.cgi?id=1528253 ) but we never >>> really reproduced it, better to double check. >>> Can you please provide an example of password that make it failing? >>> >>>> -hosted engine vm - assign static IP, no dhcp reservation. >>> >>> >>> I'm pretty sure that DHCP based configuration are correctly working, >>> I'd suggest to double check your DHCP server. >>> >>>> On 2018-05-18 00:56, Simone Tiraboschi wrote: >>>> On Fri, May 18, 2018 at 9:54 AM, <ovirt(a)fateknollogee.com&gt; wrote: >>>> >>>> Thanks for the info. >>>> Unfortunately, I do not have the ovirt-node3 logs since I deleted >>>> all 3 nodes. >>>> I have now re-installed ovirt node on all 3 hosts. >>>> I will double check that hosts can resolve each other. >>>> >>>> All hosts should correctly resolve the engine VM fqdn, the engine VM >>>> has to correctly resolve the address of all the three hosts. >>>> >>>> Any other advise (or things to check) before I re-try Hosted Engine >>>> Setup? >>>> >>>> Nothing special on my side. >>> >>> >>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)ovirt.org >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org

Not sure if this would have anything to do with that error on the previous attempt. Even though network config files (in /network-scripts) are set to "ONBOOT=yes" After a reboot, I still need to issue "systemctl restart network.service" otherwise I can not connect to any the 3 hosts? On 2018-05-18 00:46, Simone Tiraboschi wrote: > On Fri, May 18, 2018 at 9:14 AM, <ovirt(a)fateknollogee.com&gt; wrote: > >> Simone, do see any other failures before the MAC error? >> When the deployment failed, I tried to run it again then it gave me >> the MAC error. >> The first time it failed there was no error message, it just stopped >> & said 'deployment failed' > > On the previous attempt it failed on 'Add additional gluster hosts to > engine' on ovirt-node3.fateknollogee.com [7]; not sure on what really > failed there but we need engine.log and host-deploy logs for that host > but I suspect you don't have them anymore since they were on that > engine VM. > > 'Add additional gluster hosts to engine' is one of latest steps, > anything else before that was fine. > > Adding also Gobinda here. > > Just as an hint, are you sure that ovirt-node3.fateknollogee.com [7] > could be properly resolved on your engine VM? > >> On 2018-05-18 00:09, Simone Tiraboschi wrote: >> Hi, >> it fails due to >> >> ERROR The MAC address '00:16:3E:6A:7A:F9' is in use by another >> virtual machine. >> >> and this is probably due to a leftover VM from a previous attempt. >> >> It's tracked here: >> https://bugzilla.redhat.com/show_bug.cgi?id=1576451 [1] >> and it will be properly fixed with the next release. >> >> In the mean time can you please manually undefine your leftover >> HostedEngine VM from your env? >> >> /usr/bin/virsh -c >> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf >> undefine HostedEngine >> >> should do the job. >> >> On Fri, May 18, 2018 at 6:46 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Yesterday, that install failed because I did not have the required >> 60GB for /var. >> >> Today, I started from scratch & re-installed the oVirt nodes. >> That install also failed. >> I've attached the logs via dropbox link >> >> > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [2] >> [1] >> >> On 2018-05-17 01:55, ovirt(a)fateknollogee.com wrote: >> >> Some good news... >> Hosted Engine Deployment "preparing the vm" completed. >> I used a simpler password. >> When I got the previous errors, my password was 12 characters >> (upper, >> lower case & numbers) long with a %% (double percent) before and >> after >> the characters. >> I guess it didn't like the double percent!!! >> Let me continue, I will report back. >> >> On 2018-05-17 00:30, Simone Tiraboschi wrote: >> On Thu, May 17, 2018 at 9:16 AM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> More info: >> From my ovirt node (host) I can ping 192.168.124.198 >> If I try to connect via ssh root(a)192.168.124.198, it asks for a >> password. >> The password I used during the hosted engine setup does not work. >> >> Can you please try with a different more robust password? >> The log file is under /var/log/ovirt-hosted-engine-setup >> >> On 2018-05-16 22:27, ovirt(a)fateknollogee.com wrote: >> I will get the logs. >> >> Here is the exact error message: >> [ ERROR ] fatal: [ovirt-engine.fateknollogee.com [3] [2] [1]]: >> UNREACHABLE! >> => >> {"changed": false, "msg": "Failed to connect to the host via ssh: >> Warning: Permanently added >> 'ovirt-engine.fateknollogee.com [3] [2] [1],192.168.124.198' >> (ECDSA) to >> >> the >> list >> of known hosts.\r\nPermission denied >> (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n", >> "unreachable": true} >> >> On 2018-05-16 07:04, Simone Tiraboschi wrote: >> On Wed, May 16, 2018 at 3:36 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> Simone, unfortunately I deleted that install after it failed. >> I can re-run the install based on the df -h (see previous post) or I >> can change disks & increase the size of /var then re-run the >> install. >> What do you think? >> The error I was getting said it could not find the hosted engine at >> vibr0 on 192.168.xxx.xx >> >> On my opinion you could simply retry. >> Please share your log file it fails again. >> >> On 2018-05-16 06:30, Simone Tiraboschi wrote: >> >> On Wed, May 16, 2018 at 3:25 PM, <ovirt(a)fateknollogee.com&gt; wrote: >> >> This is what I had. >> Does this look correct? >> >> Yes, I think so. >> >> can you please share your hosted-engine-setup log file to understand >> where it's failing? >> >> [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/ >> [4] >> [3] >> [2] >> [1] >> [1] >> [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-glus... >> [5] >> [4] >> >> [3] >> [2] >> [2] >> [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/ [6] [5] [4] [3] [3] [3] [2] >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [2] >> [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/ >> [4] >> [3] >> [2] >> [1] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [2] >> [1] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [2] >> [3] http://sevenseas.org/ >> >> Links: >> ------ >> [1] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [2] >> [2] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [3] >> [3] http://sevenseas.org/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> Links: >> ------ >> [1] http://ovirt-engine.fateknollogee.com [3] [2] >> [2] >> >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [3] >> [3] >> >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [4] >> [4] 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.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 >> [2] >> [2] http://ovirt-engine.fateknollogee.com [3] >> [3] >> > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ >> [4] >> [4] >> > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... >> [5] >> [5] http://sevenseas.org/ > > > > Links: > ------ > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1576451 > [2] > https://www.dropbox.com/s/mnhn5bpuqlsr8ir/ovirt-hosted-engine-setup.zip?dl=0 > [3] http://ovirt-engine.fateknollogee.com > [4] > https://www.ovirt.org/documentation/install-guide/chap-System_Requirements/ > [5] > https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-glus... > [6] http://sevenseas.org/ > [7] http://ovirt-node3.fateknollogee.com