Re: [ovirt-users] Partition Trouble on oVirt Node

[Andy Michielsen]

Hello Matt,

Can you perform the command cat /etc/fstab and see what partitions you already 
created during installation ?

Did you leave the installation to decide what to do with partitioning by itself 
or did you did that yourself ?

Kind regards.

> On 16 Feb 2018, at 00:23, Matt Simonsen  wrote:
> 
> Hello all,
> 
> This may not be oVirt specific (but it may be) so thank you in advance for 
> any assistance.
> 
> I have a system installed with oVirt Node Next 4.1.9 that was installed to 
> /dev/sda
> 
> I had a seperate RAID Volume /dev/sdb that should not have been used, but now 
> that the operating system is loaded I'm struggling to get the device 
> partitioned.
> 
> I've tried mkfs.ext4 on the device and also pvcreate, with the errors below. 
> I've also rebooted a couple times and tried to disable multipathd.   Is 
> multipathd even safe to disable on Node Next?
> 
> Below are the errors I've received, and thank you again for any tips.
> 
> 
> [root@node1-g6-h3 ~]# mkfs.ext4 /dev/sdb
> mke2fs 1.42.9 (28-Dec-2013)
> /dev/sdb is entire device, not just one partition!
> Proceed anyway? (y,n) y
> /dev/sdb is apparently in use by the system; will not make a filesystem here!
> [root@node1-g6-h3 ~]# gdisk
> GPT fdisk (gdisk) version 0.8.6
> 
> Type device filename, or press  to exit: /dev/sdb
> Caution: invalid main GPT header, but valid backup; regenerating main header
> from backup!
> 
> Caution! After loading partitions, the CRC doesn't check out!
> Warning! Main partition table CRC mismatch! Loaded backup partition table
> instead of main partition table!
> 
> Warning! One or more CRCs don't match. You should repair the disk!
> 
> Partition table scan:
>   MBR: not present
>   BSD: not present
>   APM: not present
>   GPT: damaged
> 
> Found invalid MBR and corrupt GPT. What do you want to do? (Using the
> GPT MAY permit recovery of GPT data.)
>  1 - Use current GPT
>  2 - Create blank GPT
> 
> Your answer: 2
> 
> Command (? for help): n
> Partition number (1-128, default 1):
> First sector (34-16952264590, default = 2048) or {+-}size{KMGTP}:
> Last sector (2048-16952264590, default = 16952264590) or {+-}size{KMGTP}:
> Current type is 'Linux filesystem'
> Hex code or GUID (L to show codes, Enter = 8300): 8e00
> Changed type of partition to 'Linux LVM'
> 
> Command (? for help): w
> 
> Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
> PARTITIONS!!
> 
> Do you want to proceed? (Y/N): y
> OK; writing new GUID partition table (GPT) to /dev/sdb.
> The operation has completed successfully.
> [root@node1-g6-h3 ~]# pvcreate /dev/sdb1
>   Device /dev/sdb1 not found (or ignored by filtering).
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Partition Trouble on oVirt Node

[Alex K]

Did you try partprobe and pvscan before pvcreate?

On Feb 16, 2018 01:23, "Matt Simonsen"  wrote:

> Hello all,
>
> This may not be oVirt specific (but it may be) so thank you in advance for
> any assistance.
>
> I have a system installed with oVirt Node Next 4.1.9 that was installed to
> /dev/sda
>
> I had a seperate RAID Volume /dev/sdb that should not have been used, but
> now that the operating system is loaded I'm struggling to get the device
> partitioned.
>
> I've tried mkfs.ext4 on the device and also pvcreate, with the errors
> below. I've also rebooted a couple times and tried to disable multipathd.
> Is multipathd even safe to disable on Node Next?
>
> Below are the errors I've received, and thank you again for any tips.
>
>
> [root@node1-g6-h3 ~]# mkfs.ext4 /dev/sdb
> mke2fs 1.42.9 (28-Dec-2013)
> /dev/sdb is entire device, not just one partition!
> Proceed anyway? (y,n) y
> /dev/sdb is apparently in use by the system; will not make a filesystem
> here!
> [root@node1-g6-h3 ~]# gdisk
> GPT fdisk (gdisk) version 0.8.6
>
> Type device filename, or press  to exit: /dev/sdb
> Caution: invalid main GPT header, but valid backup; regenerating main
> header
> from backup!
>
> Caution! After loading partitions, the CRC doesn't check out!
> Warning! Main partition table CRC mismatch! Loaded backup partition table
> instead of main partition table!
>
> Warning! One or more CRCs don't match. You should repair the disk!
>
> Partition table scan:
>   MBR: not present
>   BSD: not present
>   APM: not present
>   GPT: damaged
>
> Found invalid MBR and corrupt GPT. What do you want to do? (Using the
> GPT MAY permit recovery of GPT data.)
>  1 - Use current GPT
>  2 - Create blank GPT
>
> Your answer: 2
>
> Command (? for help): n
> Partition number (1-128, default 1):
> First sector (34-16952264590, default = 2048) or {+-}size{KMGTP}:
> Last sector (2048-16952264590, default = 16952264590) or {+-}size{KMGTP}:
> Current type is 'Linux filesystem'
> Hex code or GUID (L to show codes, Enter = 8300): 8e00
> Changed type of partition to 'Linux LVM'
>
> Command (? for help): w
>
> Final checks complete. About to write GPT data. THIS WILL OVERWRITE
> EXISTING
> PARTITIONS!!
>
> Do you want to proceed? (Y/N): y
> OK; writing new GUID partition table (GPT) to /dev/sdb.
> The operation has completed successfully.
> [root@node1-g6-h3 ~]# pvcreate /dev/sdb1
>   Device /dev/sdb1 not found (or ignored by filtering).
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to connect to the graphic server

[Alex Bartonek]

 Original Message 
 On February 15, 2018 12:52 AM, Yedidyah Bar David  wrote:

>On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek a...@unix1337.com wrote:
>> Original Message 
>> On February 14, 2018 2:23 AM, Yedidyah Bar David d...@redhat.com wrote:
>>>On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek a...@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers.  Consider myself pretty good
 at this.  LOL.
 So I am setting up a oVirt server for a friend on his r710.  CentOS 7, 
 ovirt
 4.2.   /etc/hosts has the correct IP and FQDN setup.
 When I build a VM and try to open a console session via  SPICE I am unable
 to connect to the graphic server.  I'm connecting from a Windows 10 box.
 Using virt-manager to connect.
What happens when you try?
>>>Unable to connect to the graphic console is what the error says.  Here is 
>>>the .vv file other than the cert stuff in it:
>>[virt-viewer]
>> type=spice
>> host=192.168.1.83
>> port=-1
>> password=
>>Password is valid for 120 seconds.
>>
>>delete-this-file=1
>> fullscreen=0
>> title=Win_7_32bit:%d
>> toggle-fullscreen=shift+f11
>> release-cursor=shift+f12
>> tls-port=5900
>> enable-smartcard=0
>> enable-usb-autoshare=1
>> usb-filter=-1,-1,-1,-1,0
>> tls-ciphers=DEFAULT
>>host-subject=O=williams.com,CN=randb.williams.com
>>Port 5900 is listening by IP on the server, so that looks correct.  I shut 
>>the firewall off just in case it was the issue..no go.
>>
>
> Did you verify that you can connect there manually (e.g. with telnet)?
> Can you run a sniffer on both sides to make sure traffic passes correctly?
> Can you check vdsm/libvirt logs on the host side?


Ok.. I must have tanked it on install with the firewall.  The firewall is 
blocking port 5900.  This is on CentOS 7.  If I flush the rules, it works.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Partition Trouble on oVirt Node

[Matt Simonsen]

Hello all,

This may not be oVirt specific (but it may be) so thank you in advance 
for any assistance.


I have a system installed with oVirt Node Next 4.1.9 that was installed 
to /dev/sda


I had a seperate RAID Volume /dev/sdb that should not have been used, 
but now that the operating system is loaded I'm struggling to get the 
device partitioned.


I've tried mkfs.ext4 on the device and also pvcreate, with the errors 
below. I've also rebooted a couple times and tried to disable 
multipathd.   Is multipathd even safe to disable on Node Next?


Below are the errors I've received, and thank you again for any tips.


[root@node1-g6-h3 ~]# mkfs.ext4 /dev/sdb
mke2fs 1.42.9 (28-Dec-2013)
/dev/sdb is entire device, not just one partition!
Proceed anyway? (y,n) y
/dev/sdb is apparently in use by the system; will not make a filesystem 
here!

[root@node1-g6-h3 ~]# gdisk
GPT fdisk (gdisk) version 0.8.6

Type device filename, or press  to exit: /dev/sdb
Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: damaged

Found invalid MBR and corrupt GPT. What do you want to do? (Using the
GPT MAY permit recovery of GPT data.)
 1 - Use current GPT
 2 - Create blank GPT

Your answer: 2

Command (? for help): n
Partition number (1-128, default 1):
First sector (34-16952264590, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-16952264590, default = 16952264590) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 8e00
Changed type of partition to 'Linux LVM'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
[root@node1-g6-h3 ~]# pvcreate /dev/sdb1
  Device /dev/sdb1 not found (or ignored by filtering).


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ERROR - some other host already uses IP ###.###.###.###

[Edward Haas]

On Thu, Feb 15, 2018 at 12:36 PM, Mark Steele  wrote:

> Good morning,
>
> We had a storage crash early this morning that messed up a couple of our
> ovirt hosts. Networking seemed to be the biggest issue. I have decided to
> remove the bridge information in /etc/sysconfig/network-scripts and ip the
> nics in order to re-import them into my ovirt installation (I have already
> removed the hosts).
>
> One of the NIC's refuses to come up and is generating the following error:
>
> ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Error, some other
> host (0C:C4:7A:5B:11:5C) already uses address ###.###.###.###.
>
> When I ARP on this server, I do not see that Mac address - and none of my
> other hosts are using it either. I'm not sure where to go next other than
> completely reinstalling Centos on this server and starting over.
>

I think it tells you that another node on the network is using the same IP
address. If this iface has that static IP defined, perhaps just replace it.


>
> Ovirt version is oVirt Engine Version: 3.5.0.1-1.el6
>

Very (very) old.


>
> OS version is
>
> CentOS Linux release 7.4.1708 (Core)
>
>

> Thank you
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
> www.telvue.com
> twitter: http://twitter.com/telvue | facebook: https://www.
> facebook.com/telvue
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Virtual networks in oVirt 4.2 and MTU 1500

[Edward Haas]

On Wed, Feb 14, 2018 at 11:12 PM, Dmitry Semenov  wrote:

> I have a not big cluster on oVirt 4.2.
> Each node has a bond, that has several vlans in its turn.
> I use virtual networks OVN (External Provider -> ovirt-provider-ovn).
>
> While testing I have noticed that in virtual network MTU must be less
> 1500, so my question is may I change something in network or in bond in
> order everything in virtual network works correctly with MTU 1500?
>

What do you mean that it must be less?
If you want to have jumbo frames, you need your node to support it (HW
support) and the media that connects the nodes to support it as well.
Then, you can go to the oVirt Engine, network section and set it
(ovirtmgmt?) to whatever mtu you like (9000?).
If you have vlan/s defined on the bond which are not controlled by oVirt,
then you need to do that manually.


>
> Below link with my settings:
> https://pastebin.com/F7ssCVFa
>
> --
> Best regards
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>

Thanks,
Edy.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Alex K]

Yes you can.

On Feb 15, 2018 23:09, "Mark Steele"  wrote:

> I have with no joy.
>
> Question: Can I restart the HostedEngine with running VM's without
> negatively impacting them?
>
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 x128 <800%20885%208886> | mste...@telvue.com | http://
> www.telvue.com
> twitter: http://twitter.com/telvue | facebook: https://www.
> facebook.com/telvue
>
> On Thu, Feb 15, 2018 at 1:41 PM, Alexander Wels  wrote:
>
>> On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
>> > Michal,
>> >
>> > Thank you for the response.
>> >
>> > - there are no qemu processes running
>> > - the server has been rebooted several times
>> > - the engine has been rebooted several times
>> >
>> > The issue persists. I'm not sure where to look next.
>> >
>>
>> Have you tried right clicking on the host, and select 'Confirm Host has
>> been
>> rebooted' that is basically telling the engine that the host is fenced,
>> and
>> you should be able to put it into maintenance mode. It will ask
>> confirmation
>> but we know the host has been rebooted and nothing is running.
>>
>> >
>> > ***
>> > *Mark Steele*
>> > CIO / VP Technical Operations | TelVue Corporation
>> > TelVue - We Share Your Vision
>> > 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> > 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
>> > twitter: http://twitter.com/telvue | facebook:
>> > https://www.facebook.com/telvue
>> >
>> > On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
>> >
>> > michal.skriva...@redhat.com> wrote:
>> > > On 15 Feb 2018, at 12:06, Mark Steele  wrote:
>> > >
>> > > I have a host that is currently reporting down with NO VM's on it or
>> > > associated with it. However when I attempt to put it into maintenance
>> > > mode,
>> > > I get the following error:
>> > >
>> > > Host hv-01 cannot change into maintenance mode - not all Vms have been
>> > > migrated successfully. Consider manual intervention:
>> stopping/migrating
>> > > Vms:  (User: admin)
>> > >
>> > > I am running
>> > > oVirt Engine Version: 3.5.0.1-1.el6
>> > >
>> > >
>> > > that’s a really old version….
>> > >
>> > > first confirm there is no running vm on that host (log in there, look
>> for
>> > > qemu processes)
>> > > if not, it’s likely just engine issue, somewhere it lost track of
>> what’s
>> > > actually running there - in that case you could try to restart the
>> host,
>> > > restart engine. that should help
>> > >
>> > >
>> > > ***
>> > > *Mark Steele*
>> > > CIO / VP Technical Operations | TelVue Corporation
>> > > TelVue - We Share Your Vision
>> > > 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> > > > +Mt.+Laurel,+N
>> > > J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> |
>> > > mste...@telvue.com | http:// www.telvue.com
>> > > twitter: http://twitter.com/telvue | facebook: https://www.
>> > > facebook.com/telvue
>> > > ___
>> > > Users mailing list
>> > > Users@ovirt.org
>> > > http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine deploy 4.2.1 fails when ovirtmgmt is defined on vlan subinterface

[Kuko Armas]

>> Is this a supported configuration? Is there a way I can tell the
>> datacenter that the management network is on vlan 1005? Should I file a bug
>> report?
>> 
> Yes, please.

Submitted
https://bugzilla.redhat.com/show_bug.cgi?id=1545931

>> Is there a workaround?
>>
> 
> You can pass --noansible and fallback to the previous flow, sorry.

Yes, I can confirm that the "noansible" version works

If the ansible playbook is responsible for deploying the engine inside the HE 
VM (and you give me some directions where to look), I can try to fix it in my 
setup and send a patch

Salu2!
-- 
Miguel Armas
CanaryTek Consultoria y Sistemas SL
http://www.canarytek.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Mark Steele]

I have with no joy.

Question: Can I restart the HostedEngine with running VM's without
negatively impacting them?


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Thu, Feb 15, 2018 at 1:41 PM, Alexander Wels  wrote:

> On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
> > Michal,
> >
> > Thank you for the response.
> >
> > - there are no qemu processes running
> > - the server has been rebooted several times
> > - the engine has been rebooted several times
> >
> > The issue persists. I'm not sure where to look next.
> >
>
> Have you tried right clicking on the host, and select 'Confirm Host has
> been
> rebooted' that is basically telling the engine that the host is fenced, and
> you should be able to put it into maintenance mode. It will ask
> confirmation
> but we know the host has been rebooted and nothing is running.
>
> >
> > ***
> > *Mark Steele*
> > CIO / VP Technical Operations | TelVue Corporation
> > TelVue - We Share Your Vision
> > 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> > 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
> > twitter: http://twitter.com/telvue | facebook:
> > https://www.facebook.com/telvue
> >
> > On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
> >
> > michal.skriva...@redhat.com> wrote:
> > > On 15 Feb 2018, at 12:06, Mark Steele  wrote:
> > >
> > > I have a host that is currently reporting down with NO VM's on it or
> > > associated with it. However when I attempt to put it into maintenance
> > > mode,
> > > I get the following error:
> > >
> > > Host hv-01 cannot change into maintenance mode - not all Vms have been
> > > migrated successfully. Consider manual intervention: stopping/migrating
> > > Vms:  (User: admin)
> > >
> > > I am running
> > > oVirt Engine Version: 3.5.0.1-1.el6
> > >
> > >
> > > that’s a really old version….
> > >
> > > first confirm there is no running vm on that host (log in there, look
> for
> > > qemu processes)
> > > if not, it’s likely just engine issue, somewhere it lost track of
> what’s
> > > actually running there - in that case you could try to restart the
> host,
> > > restart engine. that should help
> > >
> > >
> > > ***
> > > *Mark Steele*
> > > CIO / VP Technical Operations | TelVue Corporation
> > > TelVue - We Share Your Vision
> > > 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> > >  7C+Mt.+Laurel,+N
> > > J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> |
> > > mste...@telvue.com | http:// www.telvue.com
> > > twitter: http://twitter.com/telvue | facebook: https://www.
> > > facebook.com/telvue
> > > ___
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Console button greyed out (4.2)

[Vineet Khandpur]

Hello.
Just had the same issue

@ 4.1, upgraded to 4.2(.1)
Updated cluster compatibility, then, data centre compatibility
All VMs lost their hardware (NICs (showed attached but unplugged), disks
(status changed to disabled) and console)

Our solution was simply to connect the NICs, activate the disks, then edit
the VM and set Console to headless.

Shut down the VM

Then before bringing it back up, unchecked headless in the VM

We then had to do a Run-Once which failed
Then did a normal Run.

Console was available, and all hardware came back fine.

Didn't have to delete and re-create anything (although had to perform the
above on all 70+ production hosts including our main web servers and HA
load balancers .. which wasn't fun) ...

Hope this helps someone

vk

On 15 February 2018 at 12:28, John Taylor  wrote:

> On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
>  wrote:
> >
> >
> >> On 15 Feb 2018, at 15:58, John Taylor  wrote:
> >>
> >> Hi Nicolas,
> >> I had the same problem and it looked like it was because of some older
> >> vms (I believe from 3.6) that were configured with console with video
> >> type of CIRRUS and protocol VNC.
> >
> > 3.6 had cirrus indeed. That should work. Can you somehow confirm it was
> really a 3.6 VM and it stopped working in 4.2? The exact steps are
> important, unfortunately.
> >
>
> I'm pretty sure they were VMs created in 3.6, but I can't say for
> absolute certain.  Sorry.
>
> >> Tracing it out it showed that the vm  libvirt xml was begin set to
> >> headless.
> >
> > do you at least recall what cluster level version it was when it stopped
> working? The VM definition should have been changed to VGA when you move
> the VM from 3.6 cluster to a 4.0+
>
> I upgraded from 4.1.something and I'm pretty sure at the time the
> cluster level was 4.1, and those same VMs were able to get consoles.
> Sorry I can't be more help now. I'll see if I have any notes that
> might help me remember.
>
> >
> >>  I tried different settings but the only thing that seemed
> >> to work was to set them to headless, then reopen config and set them
> >> to something else.
> >>
> >> -John
> >>
> >> On Thu, Feb 15, 2018 at 8:48 AM,   wrote:
> >>> Hi,
> >>>
> >>> We upgraded one of our infrastructures to 4.2.0 recently and since
> then some
> >>> of our machines have the "Console" button greyed-out in the Admin UI,
> like
> >>> they were disabled.
> >>>
> >>> I changed their compatibility to 4.2 but with no luck, as they're still
> >>> disabled.
> >>>
> >>> Is there a way to know why is that, and how to solve it?
> >>>
> >>> I'm attaching a screenshot.
> >>>
> >>> Thanks.
> >>> ___
> >>> Users mailing list
> >>> Users@ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >>
> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Console button greyed out (4.2)

[John Taylor]

On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
 wrote:
>
>
>> On 15 Feb 2018, at 15:58, John Taylor  wrote:
>>
>> Hi Nicolas,
>> I had the same problem and it looked like it was because of some older
>> vms (I believe from 3.6) that were configured with console with video
>> type of CIRRUS and protocol VNC.
>
> 3.6 had cirrus indeed. That should work. Can you somehow confirm it was 
> really a 3.6 VM and it stopped working in 4.2? The exact steps are important, 
> unfortunately.
>

I'm pretty sure they were VMs created in 3.6, but I can't say for
absolute certain.  Sorry.

>> Tracing it out it showed that the vm  libvirt xml was begin set to
>> headless.
>
> do you at least recall what cluster level version it was when it stopped 
> working? The VM definition should have been changed to VGA when you move the 
> VM from 3.6 cluster to a 4.0+

I upgraded from 4.1.something and I'm pretty sure at the time the
cluster level was 4.1, and those same VMs were able to get consoles.
Sorry I can't be more help now. I'll see if I have any notes that
might help me remember.

>
>>  I tried different settings but the only thing that seemed
>> to work was to set them to headless, then reopen config and set them
>> to something else.
>>
>> -John
>>
>> On Thu, Feb 15, 2018 at 8:48 AM,   wrote:
>>> Hi,
>>>
>>> We upgraded one of our infrastructures to 4.2.0 recently and since then some
>>> of our machines have the "Console" button greyed-out in the Admin UI, like
>>> they were disabled.
>>>
>>> I changed their compatibility to 4.2 but with no luck, as they're still
>>> disabled.
>>>
>>> Is there a way to know why is that, and how to solve it?
>>>
>>> I'm attaching a screenshot.
>>>
>>> Thanks.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Alexander Wels]

On Thursday, February 15, 2018 1:14:44 PM EST Mark Steele wrote:
> Michal,
> 
> Thank you for the response.
> 
> - there are no qemu processes running
> - the server has been rebooted several times
> - the engine has been rebooted several times
> 
> The issue persists. I'm not sure where to look next.
> 

Have you tried right clicking on the host, and select 'Confirm Host has been 
rebooted' that is basically telling the engine that the host is fenced, and 
you should be able to put it into maintenance mode. It will ask confirmation 
but we know the host has been rebooted and nothing is running.

> 
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
> twitter: http://twitter.com/telvue | facebook:
> https://www.facebook.com/telvue
> 
> On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
> 
> michal.skriva...@redhat.com> wrote:
> > On 15 Feb 2018, at 12:06, Mark Steele  wrote:
> > 
> > I have a host that is currently reporting down with NO VM's on it or
> > associated with it. However when I attempt to put it into maintenance
> > mode,
> > I get the following error:
> > 
> > Host hv-01 cannot change into maintenance mode - not all Vms have been
> > migrated successfully. Consider manual intervention: stopping/migrating
> > Vms:  (User: admin)
> > 
> > I am running
> > oVirt Engine Version: 3.5.0.1-1.el6
> > 
> > 
> > that’s a really old version….
> > 
> > first confirm there is no running vm on that host (log in there, look for
> > qemu processes)
> > if not, it’s likely just engine issue, somewhere it lost track of what’s
> > actually running there - in that case you could try to restart the host,
> > restart engine. that should help
> > 
> > 
> > ***
> > *Mark Steele*
> > CIO / VP Technical Operations | TelVue Corporation
> > TelVue - We Share Your Vision
> > 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> >  > J+08054&entry=gmail&source=g> 800.885.8886 x128 <(800)%20885-8886> |
> > mste...@telvue.com | http:// www.telvue.com
> > twitter: http://twitter.com/telvue | facebook: https://www.
> > facebook.com/telvue
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Michal Skrivanek]

On 15 Feb 2018, at 18:34, Christopher Cox  wrote:

On 02/15/2018 11:10 AM, Michal Skrivanek wrote:
..snippity... with regards to oVirt 3.5

that’s a really old version….


I know I'll catch heat for this, but by "old" you mean like December of
2015?  Just trying put things into perspective.  Thus it goes with the
ancient and decrepit Red Hat Ent. 7.1 days, right?


Hehe. It’s not about using it, rather I was referring to the fact that we
stopped developing it, stopped fixing even critical security issues.  Same
for 3.6, and 4.0.

I know, I know, FOSS... the only thing worse than running today's code is
running yesterday's.


Well, there is only a limited amount of resources you can devote to
actively maintain branches/releases
We typically do that for two versions, covering roughly 1,5 years

We still run a 3.5 oVirt in our dev lab, btw.  But I would not have set
that up (not that I would have recommended oVirt to begin with), preferring
3.4 at the time.  I would have waited for 3.6.

With that said, 3.5 isn't exactly on the "stable line" to Red Hat
Virtualization, that was 3.4 and then 3.6.

Some people can't afford major (downtime) upgrades every 3-6 months or so.


That’s why we do not really require it and still support 3.6 cluster compat
in 4.2, so that does give you longer time to update. And even the cluster
upgrades are rolling, we do not require any real downtime other than for
rebooting individual VMs and some spare capacity to migrate workloads to
during host upgrade.


But, arguably, maybe we shouldn't be running oVirt.  Maybe it's not
designed for "production".

I guess oVirt isn't really for production by definition, but many of us are
doing so.


So... not really a "ding" against oVirt developers, it's just a rapidly
moving target with the normal risks that come with that.  People just need
to understand that.


Absolutely. People should understand the difference between a GA and a
zstream update 6 months later. Every sw has bugs.
But I would argue we do actually have quite a long supported versions, when
compared to a $random project.
And then yes, we do have a longer support for Red Hat Virtualization, but
again in general I would doubt you can find many similar commercial
products being _actively_ supported for more than few years


And with that said, the fact that many of us are running those ancient
decrepit evil versions of oVirt in production today, is actually a
testimony to its quality.  Good job devs!


Thanks!



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Mark Steele]

Michal,

Thank you for the response.

- there are no qemu processes running
- the server has been rebooted several times
- the engine has been rebooted several times

The issue persists. I'm not sure where to look next.


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Thu, Feb 15, 2018 at 12:10 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> On 15 Feb 2018, at 12:06, Mark Steele  wrote:
>
> I have a host that is currently reporting down with NO VM's on it or
> associated with it. However when I attempt to put it into maintenance mode,
> I get the following error:
>
> Host hv-01 cannot change into maintenance mode - not all Vms have been
> migrated successfully. Consider manual intervention: stopping/migrating
> Vms:  (User: admin)
>
> I am running
> oVirt Engine Version: 3.5.0.1-1.el6
>
>
> that’s a really old version….
>
> first confirm there is no running vm on that host (log in there, look for
> qemu processes)
> if not, it’s likely just engine issue, somewhere it lost track of what’s
> actually running there - in that case you could try to restart the host,
> restart engine. that should help
>
>
> ***
> *Mark Steele*
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 
> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
> www.telvue.com
> twitter: http://twitter.com/telvue | facebook: https://www.
> facebook.com/telvue
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Sparsify in 4.2 - where it moved ?

[Michal Skrivanek]

On 15 Feb 2018, at 18:25, Benny Zlotnik  wrote:

Under the 3 dots as can be seen in the attached screenshot


Huh, I guess I confused that with sysprep and was looking for it in VM menu
Thanks!


On Thu, Feb 15, 2018 at 7:07 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> > On 15 Feb 2018, at 14:17, Andrei V  wrote:
> >
> > Hi !
> >
> >
> > I can’t locate “Sparsify” disk image command anywhere in oVirt 4.2.
> > Where it have been moved ?
>
> good question:)
> Was it lost in GUI redesign?
>
> >
> >
> > Thanks
> > Andrei
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Simone Tiraboschi]

On Thu, Feb 15, 2018 at 6:42 PM, Kuko Armas  wrote:

>
> > Can you please attach vdsm and host-deploy logs?
>
> This is what I saw in engine.log
>
> 2018-02-15 13:49:26,850Z INFO  
> [org.ovirt.engine.core.bll.host.HostConnectivityChecker]
> (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Engine managed to
> communicate wi
> th VDSM agent on host 'ovirt1' with address 'ovirt1'
> ('06651b32-4ef8-4b5d-ab2d-c38e84c2d790')
> 2018-02-15 13:49:30,302Z ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-1)
> [15c7e33a] EVENT_ID: VLAN_ID_
> MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure
> management network on host ovirt1. Host ovirt1 has an interface bond0.1005
> for the management netwo
> rk configuration with VLAN-ID (1005), which is different from data-center
> definition (none).
> 2018-02-15 13:49:30,302Z ERROR 
> [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Exception:
> org.ovirt.eng
> ine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException:
> Failed to configure management network
>
> It seems that ovirtmgmt creation is skipper because inconsistency between
> datacenter setup and host setup. Of course we can not configure the vlan
> for mgmt network in datacenter because we are still deploying
>

Yes, you are absolutely right: the setup has to set the VLAN ID at
datacenter level before adding the host as the old flow was doing.


>
> Salu2!
> --
> Miguel Armas
> CanaryTek Consultoria y Sistemas SL
> http://www.canarytek.com/
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine deploy 4.2.1 fails when ovirtmgmt is defined on vlan subinterface

[Simone Tiraboschi]

On Thu, Feb 15, 2018 at 3:54 PM, Kuko Armas  wrote:

>
> I'm not sure if I should submit a bug report about this, so I ask around
> here first...
> I've found a bug that "seems" related but I think it's not (
> https://bugzilla.redhat.com/show_bug.cgi?id=1523661)
>
> This is the problem:
>
> - I'm trying to do a clean HE deploy with oVirt 4.2.1 on a clean CentOS
> 7.4 host
> - I have a LACP bond (bond0) and I need my management network to be on
> vlan 1005, si I have created interface bond0.1005 on the host and
> everything works
> - I run hosted-engine deploy, and it always fails with
>
> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true,
> "cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\ //g | awk '{
> print $9 }'", "delta": "0:00:00.006473", "end": "2018-02-15
> 13:57:11.132359", "rc": 0, "start": "2018-02-15 13:57:11.125886", "stderr":
> "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
> [ ERROR ] Failed to execute stage 'Closing up': Failed executing
> ansible-playbook
>
> - Looking at the ansible playbook, I see it's trying to look for an ip
> rule using a custom routing table, but I have no such rule
>
> [root@ovirt1 ~]# ip rule
> 0:  from all lookup local
> 32766:  from all lookup main
> 32767:  from all lookup default
>
> - I also find that I have no "ovirtmgmt" bridge
>
> bridge name bridge id   STP enabled interfaces
> ;vdsmdummy; 8000.   no
> virbr0  8000.525400e6ca97   yes virbr0-nic
> vnet0
>
> - But I haven't found any reference in the ansible playbook to this
> network creation.
>
> - The HE VM gets created and I can connect with SSH, so I tried to find
> out if the ovirtmgmt network is created via vdsm from the engine
> - Looking at the engine.log I found this:
>
> 2018-02-15 13:49:26,850Z INFO  
> [org.ovirt.engine.core.bll.host.HostConnectivityChecker]
> (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Engine managed to
> communicate wi
> th VDSM agent on host 'ovirt1' with address 'ovirt1'
> ('06651b32-4ef8-4b5d-ab2d-c38e84c2d790')
> 2018-02-15 13:49:30,302Z ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-1)
> [15c7e33a] EVENT_ID: VLAN_ID_
> MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure
> management network on host ovirt1. Host ovirt1 has an interface bond0.1005
> for the management netwo
> rk configuration with VLAN-ID (1005), which is different from data-center
> definition (none).
> 2018-02-15 13:49:30,302Z ERROR 
> [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
> (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Exception:
> org.ovirt.eng
> ine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException:
> Failed to configure management network
>
> - So I guess that the engine tried to create the ovirtmgmt bridge on the
> host via vdsm, but it failed because "Host ovirt1 has an interface
> bond0.1005 for the management netwo
> rk configuration with VLAN-ID (1005), which is different from data-center
> definition (none)"
> - Of course I haven't had the opportunity to setup the management
> network's vlan in the datacenter yet, because I'm still trying to deploy
> the Hosted Engine
>
> Is this a supported configuration? Is there a way I can tell the
> datacenter that the management network is on vlan 1005? Should I file a bug
> report?
>

Yes, please.


> Is there a workaround?
>

You can pass --noansible and fallback to the previous flow, sorry.


>
> Salu2!
> --
> Miguel Armas
> CanaryTek Consultoria y Sistemas SL
> http://www.canarytek.com/
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Kuko Armas]

> Can you please attach vdsm and host-deploy logs?

This is what I saw in engine.log

2018-02-15 13:49:26,850Z INFO  
[org.ovirt.engine.core.bll.host.HostConnectivityChecker] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Engine managed to 
communicate wi
th VDSM agent on host 'ovirt1' with address 'ovirt1' 
('06651b32-4ef8-4b5d-ab2d-c38e84c2d790')
2018-02-15 13:49:30,302Z ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] EVENT_ID: VLAN_ID_
MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure 
management network on host ovirt1. Host ovirt1 has an interface bond0.1005 for 
the management netwo
rk configuration with VLAN-ID (1005), which is different from data-center 
definition (none).
2018-02-15 13:49:30,302Z ERROR 
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Exception: org.ovirt.eng
ine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException: Failed 
to configure management network

It seems that ovirtmgmt creation is skipper because inconsistency between 
datacenter setup and host setup. Of course we can not configure the vlan for 
mgmt network in datacenter because we are still deploying

Salu2!
-- 
Miguel Armas
CanaryTek Consultoria y Sistemas SL
http://www.canarytek.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Kuko Armas]

> In playing with this, I found that 4.2.1 hosted-engine will not install
> on a node with the ovirtmgmt interface being a vlan.
> 
> Is this a still supported config?  I see that access port, bonded and
> vlan tagged are supported by older versions..

That's **exactly** the same problem I just posted some hours ago ;)

Salu2!
-- 
Miguel Armas
CanaryTek Consultoria y Sistemas SL
http://www.canarytek.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Christopher Cox]

On 02/15/2018 11:10 AM, Michal Skrivanek wrote:
..snippity... with regards to oVirt 3.5


that’s a really old version….


I know I'll catch heat for this, but by "old" you mean like December of 
2015?  Just trying put things into perspective.  Thus it goes with the 
ancient and decrepit Red Hat Ent. 7.1 days, right?


I know, I know, FOSS... the only thing worse than running today's code 
is running yesterday's.


We still run a 3.5 oVirt in our dev lab, btw.  But I would not have set 
that up (not that I would have recommended oVirt to begin with), 
preferring 3.4 at the time.  I would have waited for 3.6.


With that said, 3.5 isn't exactly on the "stable line" to Red Hat 
Virtualization, that was 3.4 and then 3.6.


Some people can't afford major (downtime) upgrades every 3-6 months or 
so.  But, arguably, maybe we shouldn't be running oVirt.  Maybe it's not 
designed for "production".


I guess oVirt isn't really for production by definition, but many of us 
are doing so.


So... not really a "ding" against oVirt developers, it's just a rapidly 
moving target with the normal risks that come with that.  People just 
need to understand that.


And with that said, the fact that many of us are running those ancient 
decrepit evil versions of oVirt in production today, is actually a 
testimony to its quality.  Good job devs!



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Sparsify in 4.2 - where it moved ?

[Benny Zlotnik]

Under the 3 dots as can be seen in the attached screenshot

On Thu, Feb 15, 2018 at 7:07 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> > On 15 Feb 2018, at 14:17, Andrei V  wrote:
> >
> > Hi !
> >
> >
> > I can’t locate “Sparsify” disk image command anywhere in oVirt 4.2.
> > Where it have been moved ?
>
> good question:)
> Was it lost in GUI redesign?
>
> >
> >
> > Thanks
> > Andrei
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Michal Skrivanek]

> On 15 Feb 2018, at 12:06, Mark Steele  wrote:
> 
> I have a host that is currently reporting down with NO VM's on it or 
> associated with it. However when I attempt to put it into maintenance mode, I 
> get the following error:
> 
> Host hv-01 cannot change into maintenance mode - not all Vms have been 
> migrated successfully. Consider manual intervention: stopping/migrating Vms: 
>  (User: admin)
> 
> I am running 
> oVirt Engine Version: 3.5.0.1-1.el6

that’s a really old version….

first confirm there is no running vm on that host (log in there, look for qemu 
processes)
if not, it’s likely just engine issue, somewhere it lost track of what’s 
actually running there - in that case you could try to restart the host, 
restart engine. that should help

> 
> ***
> Mark Steele
> CIO / VP Technical Operations | TelVue Corporation
> TelVue - We Share Your Vision
> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
> 800.885.8886 x128 | mste...@telvue.com  | 
> http://www.telvue.com 
> twitter: http://twitter.com/telvue  | facebook: 
> https://www.facebook.com/telvue 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Sparsify in 4.2 - where it moved ?

[Michal Skrivanek]

> On 15 Feb 2018, at 14:17, Andrei V  wrote:
> 
> Hi !
> 
> 
> I can’t locate “Sparsify” disk image command anywhere in oVirt 4.2.
> Where it have been moved ?

good question:)
Was it lost in GUI redesign?

> 
> 
> Thanks
> Andrei
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Console button greyed out (4.2)

[Michal Skrivanek]

> On 15 Feb 2018, at 16:37, Jason Keltz  wrote:
> 
> On 02/15/2018 08:48 AM, nico...@devels.es wrote:
>> Hi,
>> 
>> We upgraded one of our infrastructures to 4.2.0 recently and since then some 
>> of our machines have the "Console" button greyed-out in the Admin UI, like 
>> they were disabled.
>> 
>> I changed their compatibility to 4.2 but with no luck, as they're still 
>> disabled.
>> 
>> Is there a way to know why is that, and how to solve it?
>> 
>> I'm attaching a screenshot.
> 
> Hi Nicolas.
> I had the same problem with most of my VMs after the upgrade from 4.1 to 4.2.
> See bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1528868
> (which admittedly was a mesh of a bunch of different issues that occurred)

yeah, that’s not a good idea to mix more issues:)
Seems https://bugzilla.redhat.com/show_bug.cgi?id=1528868#c26 is the last one 
relevant to the grayed out console problem in this email thread.

it’s also possible to check "VM Devices” subtab and list the graphical devices. 
If this is the same problem as from Nicolas then it would list cirrus and it 
would be great if you can confirm the conditionas are similar (i.e. originally 
a 3.6 VM)
And then - if possible - describe some history of what happened. When was the 
VM created, when was cluster updated, when the system was upgraded and to what 
versions.

Thanks,
michal


> Red Hat was never really able to figure out why, and I think they pretty much 
> just dropped the issue because it seemed like it only happened for me.  In 
> order to resolve it, I had to delete the VMs (not the disk of course), and 
> recreate them, and then I got the console option back.
> It's "good" to see that it's not just me that had this problem. There's a bug 
> to be found there somewhere!!
> 
> Jason.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Simone Tiraboschi]

On Thu, Feb 15, 2018 at 5:56 PM, Simone Tiraboschi 
wrote:

>
>
> On Thu, Feb 15, 2018 at 5:20 PM, Thomas Davis  wrote:
>
>> In playing with this, I found that 4.2.1 hosted-engine will not install
>> on a node with the ovirtmgmt interface being a vlan.
>>
>
> Can you please attach vdsm and host-deploy logs?
>
>
>> Is this a still supported config?  I see that access port, bonded and
>> vlan tagged are supported by older versions..
>>
>
> Yes, absolutely: if not VLAN doens't work it's definitively an issue.
> Adding Ido here.
>

Oh, just another thing.
The old flow is still there as a deprecated fallback.
You can force it passing --noansible option.


>
>
>>
>> thomas
>>
>> On 02/05/2018 08:16 AM, Simone Tiraboschi wrote:
>>
>>>
>>>
>>> On Fri, Feb 2, 2018 at 9:10 PM, Thomas Davis >> tada...@lbl.gov>> wrote:
>>>
>>> Is this supported?
>>>
>>> I have a node, that centos 7.4 minimal is installed on, with an
>>> interface setup for an IP address.
>>>
>>> I've yum installed nothing else except the ovirt-4.2.1-pre rpm, run
>>> screen, and then do the 'hosted-engine --deploy' command.
>>>
>>>
>>> Fine, nothing else is required.
>>>
>>>
>>> It hangs on:
>>>
>>> [ INFO  ] changed: [localhost]
>>> [ INFO  ] TASK [Get ovirtmgmt route table id]
>>> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed":
>>> true, "cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\
>>> //g | awk '{ print $9 }'", "delta": "0:00:00.004845", "end":
>>> "2018-02-02 12:03:30.794860", "rc": 0, "start": "2018-02-02
>>> 12:03:30.790015", "stderr": "", "stderr_lines": [], "stdout": "",
>>> "stdout_lines": []}
>>> [ ERROR ] Failed to execute stage 'Closing up': Failed executing
>>> ansible-playbook
>>> [ INFO  ] Stage: Clean up
>>> [ INFO  ] Cleaning temporary resources
>>> [ INFO  ] TASK [Gathering Facts]
>>> [ INFO  ] ok: [localhost]
>>> [ INFO  ] TASK [Remove local vm dir]
>>> [ INFO  ] ok: [localhost]
>>> [ INFO  ] Generating answer file
>>> '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180202
>>> 120333.conf'
>>> [ INFO  ] Stage: Pre-termination
>>> [ INFO  ] Stage: Termination
>>> [ ERROR ] Hosted Engine deployment failed: please check the logs for
>>> the issue, fix accordingly or re-deploy from scratch.
>>>Log file is located at
>>> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup
>>> -20180202115038-r11nh1.log
>>>
>>> but the VM is up and running, just attached to the 192.168.122.0/24
>>>  subnet
>>>
>>> [root@d8-r13-c2-n1 ~]# ssh root@192.168.122.37
>>> 
>>> root@192.168.122.37 's password:
>>> Last login: Fri Feb  2 11:54:47 2018 from 192.168.122.1
>>> [root@ovirt ~]# systemctl status ovirt-engine
>>> ● ovirt-engine.service - oVirt Engine
>>> Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service;
>>> enabled; vendor preset: disabled)
>>> Active: active (running) since Fri 2018-02-02 11:54:42 PST;
>>> 11min ago
>>>   Main PID: 24724 (ovirt-engine.py)
>>> CGroup: /system.slice/ovirt-engine.service
>>> ├─24724 /usr/bin/python
>>> /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
>>> --redirect-output --systemd=notify start
>>> └─24856 ovirt-engine -server -XX:+TieredCompilation
>>> -Xms3971M -Xmx3971M -Djava.awt.headless=true
>>> -Dsun.rmi.dgc.client.gcInterval=360
>>> -Dsun.rmi.dgc.server.gcInterval=360 -Djsse...
>>>
>>> Feb 02 11:54:41 ovirt.crt.nersc.gov 
>>> systemd[1]: Starting oVirt Engine...
>>> Feb 02 11:54:41 ovirt.crt.nersc.gov 
>>> ovirt-engine.py[24724]: 2018-02-02 11:54:41,767-0800 ovirt-engine:
>>> INFO _detectJBossVersion:187 Detecting JBoss version. Running:
>>> /usr/lib/jvm/jre/...60', '-
>>> Feb 02 11:54:42 ovirt.crt.nersc.gov 
>>> ovirt-engine.py[24724]: 2018-02-02 11:54:42,394-0800 ovirt-engine:
>>> INFO _detectJBossVersion:207 Return code: 0,  | stdout: '[u'WildFly
>>> Full 11.0.0tderr: '[]'
>>> Feb 02 11:54:42 ovirt.crt.nersc.gov 
>>> systemd[1]: Started oVirt Engine.
>>> Feb 02 11:55:25 ovirt.crt.nersc.gov 
>>> python2[25640]: ansible-stat Invoked with checksum_algorithm=sha1
>>> get_checksum=True follow=False
>>> path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
>>> Feb 02 11:55:29 ovirt.crt.nersc.gov 
>>> python2[25698]: ansible-stat Invoked with checksum_algorithm=sha1
>>> get_checksum=True follow=False
>>> path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
>>> Feb 02 11:55:30 ovirt.crt.nersc.gov 
>>> p

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Simone Tiraboschi]

On Thu, Feb 15, 2018 at 5:20 PM, Thomas Davis  wrote:

> In playing with this, I found that 4.2.1 hosted-engine will not install on
> a node with the ovirtmgmt interface being a vlan.
>

Can you please attach vdsm and host-deploy logs?


> Is this a still supported config?  I see that access port, bonded and vlan
> tagged are supported by older versions..
>

Yes, absolutely: if not VLAN doens't work it's definitively an issue.
Adding Ido here.


>
> thomas
>
> On 02/05/2018 08:16 AM, Simone Tiraboschi wrote:
>
>>
>>
>> On Fri, Feb 2, 2018 at 9:10 PM, Thomas Davis > tada...@lbl.gov>> wrote:
>>
>> Is this supported?
>>
>> I have a node, that centos 7.4 minimal is installed on, with an
>> interface setup for an IP address.
>>
>> I've yum installed nothing else except the ovirt-4.2.1-pre rpm, run
>> screen, and then do the 'hosted-engine --deploy' command.
>>
>>
>> Fine, nothing else is required.
>>
>>
>> It hangs on:
>>
>> [ INFO  ] changed: [localhost]
>> [ INFO  ] TASK [Get ovirtmgmt route table id]
>> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed":
>> true, "cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\
>> //g | awk '{ print $9 }'", "delta": "0:00:00.004845", "end":
>> "2018-02-02 12:03:30.794860", "rc": 0, "start": "2018-02-02
>> 12:03:30.790015", "stderr": "", "stderr_lines": [], "stdout": "",
>> "stdout_lines": []}
>> [ ERROR ] Failed to execute stage 'Closing up': Failed executing
>> ansible-playbook
>> [ INFO  ] Stage: Clean up
>> [ INFO  ] Cleaning temporary resources
>> [ INFO  ] TASK [Gathering Facts]
>> [ INFO  ] ok: [localhost]
>> [ INFO  ] TASK [Remove local vm dir]
>> [ INFO  ] ok: [localhost]
>> [ INFO  ] Generating answer file
>> '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180202
>> 120333.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Hosted Engine deployment failed: please check the logs for
>> the issue, fix accordingly or re-deploy from scratch.
>>Log file is located at
>> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup
>> -20180202115038-r11nh1.log
>>
>> but the VM is up and running, just attached to the 192.168.122.0/24
>>  subnet
>>
>> [root@d8-r13-c2-n1 ~]# ssh root@192.168.122.37
>> 
>> root@192.168.122.37 's password:
>> Last login: Fri Feb  2 11:54:47 2018 from 192.168.122.1
>> [root@ovirt ~]# systemctl status ovirt-engine
>> ● ovirt-engine.service - oVirt Engine
>> Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service;
>> enabled; vendor preset: disabled)
>> Active: active (running) since Fri 2018-02-02 11:54:42 PST;
>> 11min ago
>>   Main PID: 24724 (ovirt-engine.py)
>> CGroup: /system.slice/ovirt-engine.service
>> ├─24724 /usr/bin/python
>> /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
>> --redirect-output --systemd=notify start
>> └─24856 ovirt-engine -server -XX:+TieredCompilation
>> -Xms3971M -Xmx3971M -Djava.awt.headless=true
>> -Dsun.rmi.dgc.client.gcInterval=360
>> -Dsun.rmi.dgc.server.gcInterval=360 -Djsse...
>>
>> Feb 02 11:54:41 ovirt.crt.nersc.gov 
>> systemd[1]: Starting oVirt Engine...
>> Feb 02 11:54:41 ovirt.crt.nersc.gov 
>> ovirt-engine.py[24724]: 2018-02-02 11:54:41,767-0800 ovirt-engine:
>> INFO _detectJBossVersion:187 Detecting JBoss version. Running:
>> /usr/lib/jvm/jre/...60', '-
>> Feb 02 11:54:42 ovirt.crt.nersc.gov 
>> ovirt-engine.py[24724]: 2018-02-02 11:54:42,394-0800 ovirt-engine:
>> INFO _detectJBossVersion:207 Return code: 0,  | stdout: '[u'WildFly
>> Full 11.0.0tderr: '[]'
>> Feb 02 11:54:42 ovirt.crt.nersc.gov 
>> systemd[1]: Started oVirt Engine.
>> Feb 02 11:55:25 ovirt.crt.nersc.gov 
>> python2[25640]: ansible-stat Invoked with checksum_algorithm=sha1
>> get_checksum=True follow=False
>> path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
>> Feb 02 11:55:29 ovirt.crt.nersc.gov 
>> python2[25698]: ansible-stat Invoked with checksum_algorithm=sha1
>> get_checksum=True follow=False
>> path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
>> Feb 02 11:55:30 ovirt.crt.nersc.gov 
>> python2[25741]: ansible-stat Invoked with checksum_algorithm=sha1
>> get_checksum=True follow=False
>> path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
>> Feb 02 11:55:30 ovirt.crt.nersc.gov 
>> python2[25767]: ansible-stat Invoked with checksum_algo

Re: [ovirt-users] Console button greyed out (4.2)

[Michal Skrivanek]

> On 15 Feb 2018, at 15:58, John Taylor  wrote:
> 
> Hi Nicolas,
> I had the same problem and it looked like it was because of some older
> vms (I believe from 3.6) that were configured with console with video
> type of CIRRUS and protocol VNC.

3.6 had cirrus indeed. That should work. Can you somehow confirm it was really 
a 3.6 VM and it stopped working in 4.2? The exact steps are important, 
unfortunately.

> Tracing it out it showed that the vm  libvirt xml was begin set to
> headless.

do you at least recall what cluster level version it was when it stopped 
working? The VM definition should have been changed to VGA when you move the VM 
from 3.6 cluster to a 4.0+

>  I tried different settings but the only thing that seemed
> to work was to set them to headless, then reopen config and set them
> to something else.
> 
> -John
> 
> On Thu, Feb 15, 2018 at 8:48 AM,   wrote:
>> Hi,
>> 
>> We upgraded one of our infrastructures to 4.2.0 recently and since then some
>> of our machines have the "Console" button greyed-out in the Admin UI, like
>> they were disabled.
>> 
>> I changed their compatibility to 4.2 but with no luck, as they're still
>> disabled.
>> 
>> Is there a way to know why is that, and how to solve it?
>> 
>> I'm attaching a screenshot.
>> 
>> Thanks.
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted-engine 4.2.1-pre setup on a clean node..

[Thomas Davis]

In playing with this, I found that 4.2.1 hosted-engine will not install 
on a node with the ovirtmgmt interface being a vlan.


Is this a still supported config?  I see that access port, bonded and 
vlan tagged are supported by older versions..


thomas

On 02/05/2018 08:16 AM, Simone Tiraboschi wrote:



On Fri, Feb 2, 2018 at 9:10 PM, Thomas Davis > wrote:


Is this supported?

I have a node, that centos 7.4 minimal is installed on, with an
interface setup for an IP address.

I've yum installed nothing else except the ovirt-4.2.1-pre rpm, run
screen, and then do the 'hosted-engine --deploy' command.


Fine, nothing else is required.


It hangs on:

[ INFO  ] changed: [localhost]
[ INFO  ] TASK [Get ovirtmgmt route table id]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed":
true, "cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\
//g | awk '{ print $9 }'", "delta": "0:00:00.004845", "end":
"2018-02-02 12:03:30.794860", "rc": 0, "start": "2018-02-02
12:03:30.790015", "stderr": "", "stderr_lines": [], "stdout": "",
"stdout_lines": []}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing
ansible-playbook
[ INFO  ] Stage: Clean up
[ INFO  ] Cleaning temporary resources
[ INFO  ] TASK [Gathering Facts]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [Remove local vm dir]
[ INFO  ] ok: [localhost]
[ INFO  ] Generating answer file
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20180202120333.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: please check the logs for
the issue, fix accordingly or re-deploy from scratch.
           Log file is located at

/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180202115038-r11nh1.log

but the VM is up and running, just attached to the 192.168.122.0/24
 subnet

[root@d8-r13-c2-n1 ~]# ssh root@192.168.122.37

root@192.168.122.37 's password:
Last login: Fri Feb  2 11:54:47 2018 from 192.168.122.1
[root@ovirt ~]# systemctl status ovirt-engine
● ovirt-engine.service - oVirt Engine
    Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service;
enabled; vendor preset: disabled)
    Active: active (running) since Fri 2018-02-02 11:54:42 PST;
11min ago
  Main PID: 24724 (ovirt-engine.py)
    CGroup: /system.slice/ovirt-engine.service
            ├─24724 /usr/bin/python
/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
--redirect-output --systemd=notify start
            └─24856 ovirt-engine -server -XX:+TieredCompilation
-Xms3971M -Xmx3971M -Djava.awt.headless=true
-Dsun.rmi.dgc.client.gcInterval=360
-Dsun.rmi.dgc.server.gcInterval=360 -Djsse...

Feb 02 11:54:41 ovirt.crt.nersc.gov 
systemd[1]: Starting oVirt Engine...
Feb 02 11:54:41 ovirt.crt.nersc.gov 
ovirt-engine.py[24724]: 2018-02-02 11:54:41,767-0800 ovirt-engine:
INFO _detectJBossVersion:187 Detecting JBoss version. Running:
/usr/lib/jvm/jre/...60', '-
Feb 02 11:54:42 ovirt.crt.nersc.gov 
ovirt-engine.py[24724]: 2018-02-02 11:54:42,394-0800 ovirt-engine:
INFO _detectJBossVersion:207 Return code: 0,  | stdout: '[u'WildFly
Full 11.0.0tderr: '[]'
Feb 02 11:54:42 ovirt.crt.nersc.gov 
systemd[1]: Started oVirt Engine.
Feb 02 11:55:25 ovirt.crt.nersc.gov 
python2[25640]: ansible-stat Invoked with checksum_algorithm=sha1
get_checksum=True follow=False
path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
Feb 02 11:55:29 ovirt.crt.nersc.gov 
python2[25698]: ansible-stat Invoked with checksum_algorithm=sha1
get_checksum=True follow=False
path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
Feb 02 11:55:30 ovirt.crt.nersc.gov 
python2[25741]: ansible-stat Invoked with checksum_algorithm=sha1
get_checksum=True follow=False
path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
Feb 02 11:55:30 ovirt.crt.nersc.gov 
python2[25767]: ansible-stat Invoked with checksum_algorithm=sha1
get_checksum=True follow=False
path=/usr/share/ovirt-engine/playbooks/roles/ovir...ributes=True
Feb 02 11:55:31 ovirt.crt.nersc.gov 
python2[25795]: ansible-stat Invoked with checksum_algorithm=sha1
get_checksum=True follow=False
path=/etc/ovirt-engine-metrics/config.yml get_md5...ributes=True

The 'ip rule list' never has an ovirtmgmt rule/table in it.. which
means the ansible script loops then dies

Re: [ovirt-users] Console button greyed out (4.2)

[Jason Keltz]

On 02/15/2018 08:48 AM, nico...@devels.es wrote:

Hi,

We upgraded one of our infrastructures to 4.2.0 recently and since 
then some of our machines have the "Console" button greyed-out in the 
Admin UI, like they were disabled.


I changed their compatibility to 4.2 but with no luck, as they're 
still disabled.


Is there a way to know why is that, and how to solve it?

I'm attaching a screenshot.


Hi Nicolas.
I had the same problem with most of my VMs after the upgrade from 4.1 to 
4.2.

See bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1528868
(which admittedly was a mesh of a bunch of different issues that occurred)
Red Hat was never really able to figure out why, and I think they pretty 
much just dropped the issue because it seemed like it only happened for 
me.  In order to resolve it, I had to delete the VMs (not the disk of 
course), and recreate them, and then I got the console option back.
It's "good" to see that it's not just me that had this problem. There's 
a bug to be found there somewhere!!


Jason.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.2.2 First Release Candidate is now available

[Lev Veyde]

The oVirt Project is pleased to announce the availability of the oVirt
4.2.2 First
Release Candidate, as of February 15th, 2018

This update is a release candidate of the second in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.2

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.2.2 release highlights:
http://www.ovirt.org/release/4. 2
. 
2 /

* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4. 2
. 
2 /

[2] http://resources.ovirt.org/pub/ovirt-4.
2-pre
/iso/


-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] hosted-engine deploy 4.2.1 fails when ovirtmgmt is defined on vlan subinterface

[Kuko Armas]

I'm not sure if I should submit a bug report about this, so I ask around here 
first...
I've found a bug that "seems" related but I think it's not 
(https://bugzilla.redhat.com/show_bug.cgi?id=1523661)

This is the problem:

- I'm trying to do a clean HE deploy with oVirt 4.2.1 on a clean CentOS 7.4 host
- I have a LACP bond (bond0) and I need my management network to be on vlan 
1005, si I have created interface bond0.1005 on the host and everything works
- I run hosted-engine deploy, and it always fails with

[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, 
"cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\ //g | awk '{ print 
$9 }'", "delta": "0:00:00.006473", "end": "2018-02-15 13:57:11.132359", "rc": 
0, "start": "2018-02-15 13:57:11.125886", "stderr": "", "stderr_lines": [], 
"stdout": "", "stdout_lines": []}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing 
ansible-playbook

- Looking at the ansible playbook, I see it's trying to look for an ip rule 
using a custom routing table, but I have no such rule

[root@ovirt1 ~]# ip rule
0:  from all lookup local 
32766:  from all lookup main 
32767:  from all lookup default 

- I also find that I have no "ovirtmgmt" bridge

bridge name bridge id   STP enabled interfaces
;vdsmdummy; 8000.   no
virbr0  8000.525400e6ca97   yes virbr0-nic
vnet0

- But I haven't found any reference in the ansible playbook to this network 
creation.

- The HE VM gets created and I can connect with SSH, so I tried to find out if 
the ovirtmgmt network is created via vdsm from the engine
- Looking at the engine.log I found this:

2018-02-15 13:49:26,850Z INFO  
[org.ovirt.engine.core.bll.host.HostConnectivityChecker] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Engine managed to 
communicate wi
th VDSM agent on host 'ovirt1' with address 'ovirt1' 
('06651b32-4ef8-4b5d-ab2d-c38e84c2d790')
2018-02-15 13:49:30,302Z ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] EVENT_ID: VLAN_ID_
MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure 
management network on host ovirt1. Host ovirt1 has an interface bond0.1005 for 
the management netwo
rk configuration with VLAN-ID (1005), which is different from data-center 
definition (none).
2018-02-15 13:49:30,302Z ERROR 
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] 
(EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Exception: org.ovirt.eng
ine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException: Failed 
to configure management network

- So I guess that the engine tried to create the ovirtmgmt bridge on the host 
via vdsm, but it failed because "Host ovirt1 has an interface bond0.1005 for 
the management netwo
rk configuration with VLAN-ID (1005), which is different from data-center 
definition (none)"
- Of course I haven't had the opportunity to setup the management network's 
vlan in the datacenter yet, because I'm still trying to deploy the Hosted Engine

Is this a supported configuration? Is there a way I can tell the datacenter 
that the management network is on vlan 1005? Should I file a bug report?
Is there a workaround?

Salu2!
-- 
Miguel Armas
CanaryTek Consultoria y Sistemas SL
http://www.canarytek.com/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Console button greyed out (4.2)

[John Taylor]

Hi Nicolas,
I had the same problem and it looked like it was because of some older
vms (I believe from 3.6) that were configured with console with video
type of CIRRUS and protocol VNC.
Tracing it out it showed that the vm  libvirt xml was begin set to
headless.  I tried different settings but the only thing that seemed
to work was to set them to headless, then reopen config and set them
to something else.

-John

On Thu, Feb 15, 2018 at 8:48 AM,   wrote:
> Hi,
>
> We upgraded one of our infrastructures to 4.2.0 recently and since then some
> of our machines have the "Console" button greyed-out in the Admin UI, like
> they were disabled.
>
> I changed their compatibility to 4.2 but with no luck, as they're still
> disabled.
>
> Is there a way to know why is that, and how to solve it?
>
> I'm attaching a screenshot.
>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manageiq ovn

[Alona Kaplan]

On Thu, Feb 15, 2018 at 4:03 PM, Aliaksei Nazarenka <
aliaksei.nazare...@gmail.com> wrote:

> and how i can change network in the created VM?
>

It is not possible via manageiq. Only via ovirt.


>
> Sorry for my intrusive questions)))
>
> 2018-02-15 16:51 GMT+03:00 Aliaksei Nazarenka <
> aliaksei.nazare...@gmail.com>:
>
>> ovirt-provider-ovn-1.2.7-0.20180213232754.gitebd60ad.el7.centos.noarch
>> on hosted-engine
>> ovirt-provider-ovn-driver-1.2.5-1.el7.centos.noarch on ovirt hosts
>>
>> 2018-02-15 16:40 GMT+03:00 Alona Kaplan :
>>
>>>
>>>
>>> On Thu, Feb 15, 2018 at 3:36 PM, Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com> wrote:
>>>
 when i try to create network router, i see this message:  *Unable to
 create Network Router "test_router": undefined method `[]' for 
 nil:NilClass*

>>>
>>> What ovn-provider version you're using? Can you please attach the ovn
>>> provider log ( /var/log/ovirt-provider-ovn.log)?
>>>
>>>

 2018-02-15 16:20 GMT+03:00 Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com>:

> Big Thank you! This work! But... Networks are created, but I do not
> see them in the ovirt manager, but through the ovn-nbctl command, I see 
> all
> the networks. And maybe you can tell me how to assign a VM network from
> Manageiq?
>
> 2018-02-15 15:01 GMT+03:00 Alona Kaplan :
>
>>
>>
>> On Thu, Feb 15, 2018 at 1:54 PM, Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com> wrote:
>>
>>> Error - 1 Minute Ago
>>> undefined method `orchestration_stacks' for
>>> # - I
>>> get this message if I try to create a network of overts and then try to
>>> check the status of the network manager.
>>>
>>
>> It is the same bug.
>> You need to apply the fixes in https://github.com/ManageIQ/ma
>> nageiq-providers-ovirt/pull/198/files to make it work.
>> The best option is to upgrade your version.
>>
>>
>>> 2018-02-15 14:28 GMT+03:00 Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com>:
>>>
 I tried to make changes to the file refresher_ovn_provider.yml -
 changed the passwords, corrected the names of the names, but it was not
 successful.

 2018-02-15 14:26 GMT+03:00 Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com>:

> Hi!
> I'm use oVirt 4.2.2 + Manageiq  gaprindashvili-1.2018012514301
> 9_1450f27
> After i set this commits  (upstream - https://bugzilla.redhat.com/
> 1542063) i no saw changes.
>
>
> 2018-02-15 11:22 GMT+03:00 Alona Kaplan :
>
>> Hi,
>>
>> What version of manageiq you are using?
>> We had a bug https://bugzilla.redhat.com/1542152 (upstream -
>> https://bugzilla.redhat.com/1542063) that was fixed in version
>> 5.9.0.20
>>
>> Please let me know it upgrading the version helped you.
>>
>> Thanks,
>> Alona.
>>
>> On Wed, Feb 14, 2018 at 2:32 PM, Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com> wrote:
>>
>>> Good afternoon!
>>> I read your article - https://www.ovirt.org/develop/
>>> release-management/features/network/manageiq_ovn/. I have only
>>> one question: how to create a network or subnet in Manageiq + ovirt 
>>> 4.2.1.
>>> When I try to create a network, I need to select a tenant, but 
>>> there is
>>> nothing that I could choose. How can it be?
>>>
>>> Sincerely. Alexey Nazarenko
>>>
>>
>>
>

>>>
>>
>

>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Console button greyed out (4.2)

[nicolas]

Hi,

We upgraded one of our infrastructures to 4.2.0 recently and since then 
some of our machines have the "Console" button greyed-out in the Admin 
UI, like they were disabled.


I changed their compatibility to 4.2 but with no luck, as they're still 
disabled.


Is there a way to know why is that, and how to solve it?

I'm attaching a screenshot.

Thanks.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manageiq ovn

[Alona Kaplan]

On Thu, Feb 15, 2018 at 3:36 PM, Aliaksei Nazarenka <
aliaksei.nazare...@gmail.com> wrote:

> when i try to create network router, i see this message:  *Unable to
> create Network Router "test_router": undefined method `[]' for nil:NilClass*
>

What ovn-provider version you're using? Can you please attach the ovn
provider log ( /var/log/ovirt-provider-ovn.log)?


>
> 2018-02-15 16:20 GMT+03:00 Aliaksei Nazarenka <
> aliaksei.nazare...@gmail.com>:
>
>> Big Thank you! This work! But... Networks are created, but I do not see
>> them in the ovirt manager, but through the ovn-nbctl command, I see all the
>> networks. And maybe you can tell me how to assign a VM network from
>> Manageiq?
>>
>> 2018-02-15 15:01 GMT+03:00 Alona Kaplan :
>>
>>>
>>>
>>> On Thu, Feb 15, 2018 at 1:54 PM, Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com> wrote:
>>>
 Error - 1 Minute Ago
 undefined method `orchestration_stacks' for
 # - I get
 this message if I try to create a network of overts and then try to check
 the status of the network manager.

>>>
>>> It is the same bug.
>>> You need to apply the fixes in https://github.com/ManageIQ/ma
>>> nageiq-providers-ovirt/pull/198/files to make it work.
>>> The best option is to upgrade your version.
>>>
>>>
 2018-02-15 14:28 GMT+03:00 Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com>:

> I tried to make changes to the file refresher_ovn_provider.yml -
> changed the passwords, corrected the names of the names, but it was not
> successful.
>
> 2018-02-15 14:26 GMT+03:00 Aliaksei Nazarenka <
> aliaksei.nazare...@gmail.com>:
>
>> Hi!
>> I'm use oVirt 4.2.2 + Manageiq  gaprindashvili-1.2018012514301
>> 9_1450f27
>> After i set this commits  (upstream - https://bugzilla.redhat.com/
>> 1542063) i no saw changes.
>>
>>
>> 2018-02-15 11:22 GMT+03:00 Alona Kaplan :
>>
>>> Hi,
>>>
>>> What version of manageiq you are using?
>>> We had a bug https://bugzilla.redhat.com/1542152 (upstream -
>>> https://bugzilla.redhat.com/1542063) that was fixed in version
>>> 5.9.0.20
>>>
>>> Please let me know it upgrading the version helped you.
>>>
>>> Thanks,
>>> Alona.
>>>
>>> On Wed, Feb 14, 2018 at 2:32 PM, Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com> wrote:
>>>
 Good afternoon!
 I read your article - https://www.ovirt.org/develop/
 release-management/features/network/manageiq_ovn/. I have only one
 question: how to create a network or subnet in Manageiq + ovirt 4.2.1. 
 When
 I try to create a network, I need to select a tenant, but there is 
 nothing
 that I could choose. How can it be?

 Sincerely. Alexey Nazarenko

>>>
>>>
>>
>

>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manageiq ovn

[Alona Kaplan]

Hi Alexey,

Please reply to the users list so all the user may enjoy the information.

Automatic sync of ovn networks to ovirt was added on version
ovirt-engine-4.2.1.3 (https://bugzilla.redhat.com/1511823).
If you use lower version you should import the network to ovirt manually
(networks tab -> import button).

Once the ovn network is imported to ovirt a vnic profile is automatically
created to it.
In manageiq, you can assign this profile to a vm you provision (provision
vm -> network tab -> vlan field).

Alona.



On Thu, Feb 15, 2018 at 3:20 PM, Aliaksei Nazarenka <
aliaksei.nazare...@gmail.com> wrote:

> Big Thank you! This work! But... Networks are created, but I do not see
> them in the ovirt manager, but through the ovn-nbctl command, I see all the
> networks. And maybe you can tell me how to assign a VM network from
> Manageiq?
>
> 2018-02-15 15:01 GMT+03:00 Alona Kaplan :
>
>>
>>
>> On Thu, Feb 15, 2018 at 1:54 PM, Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com> wrote:
>>
>>> Error - 1 Minute Ago
>>> undefined method `orchestration_stacks' for
>>> # - I get
>>> this message if I try to create a network of overts and then try to check
>>> the status of the network manager.
>>>
>>
>> It is the same bug.
>> You need to apply the fixes in https://github.com/ManageIQ/ma
>> nageiq-providers-ovirt/pull/198/files to make it work.
>> The best option is to upgrade your version.
>>
>>
>>> 2018-02-15 14:28 GMT+03:00 Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com>:
>>>
 I tried to make changes to the file refresher_ovn_provider.yml -
 changed the passwords, corrected the names of the names, but it was not
 successful.

 2018-02-15 14:26 GMT+03:00 Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com>:

> Hi!
> I'm use oVirt 4.2.2 + Manageiq  gaprindashvili-1.2018012514301
> 9_1450f27
> After i set this commits  (upstream - https://bugzilla.redhat.com/
> 1542063) i no saw changes.
>
>
> 2018-02-15 11:22 GMT+03:00 Alona Kaplan :
>
>> Hi,
>>
>> What version of manageiq you are using?
>> We had a bug https://bugzilla.redhat.com/1542152 (upstream -
>> https://bugzilla.redhat.com/1542063) that was fixed in version
>> 5.9.0.20
>>
>> Please let me know it upgrading the version helped you.
>>
>> Thanks,
>> Alona.
>>
>> On Wed, Feb 14, 2018 at 2:32 PM, Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com> wrote:
>>
>>> Good afternoon!
>>> I read your article - https://www.ovirt.org/develop/
>>> release-management/features/network/manageiq_ovn/. I have only one
>>> question: how to create a network or subnet in Manageiq + ovirt 4.2.1. 
>>> When
>>> I try to create a network, I need to select a tenant, but there is 
>>> nothing
>>> that I could choose. How can it be?
>>>
>>> Sincerely. Alexey Nazarenko
>>>
>>
>>
>

>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Sparsify in 4.2 - where it moved ?

[Andrei V]

Hi !


I can’t locate “Sparsify” disk image command anywhere in oVirt 4.2.
Where it have been moved ?


Thanks
Andrei


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manageiq ovn

[Alona Kaplan]

On Thu, Feb 15, 2018 at 1:54 PM, Aliaksei Nazarenka <
aliaksei.nazare...@gmail.com> wrote:

> Error - 1 Minute Ago
> undefined method `orchestration_stacks' for # :InfraManager:0x0007bf9288> - I get this message if I try to create a
> network of overts and then try to check the status of the network manager.
>

It is the same bug.
You need to apply the fixes in
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/198/files to make
it work.
The best option is to upgrade your version.


> 2018-02-15 14:28 GMT+03:00 Aliaksei Nazarenka <
> aliaksei.nazare...@gmail.com>:
>
>> I tried to make changes to the file refresher_ovn_provider.yml - changed
>> the passwords, corrected the names of the names, but it was not successful.
>>
>> 2018-02-15 14:26 GMT+03:00 Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com>:
>>
>>> Hi!
>>> I'm use oVirt 4.2.2 + Manageiq  gaprindashvili-1.20180125143019_1450f27
>>> After i set this commits  (upstream - https://bugzilla.redhat.com/
>>> 1542063) i no saw changes.
>>>
>>>
>>> 2018-02-15 11:22 GMT+03:00 Alona Kaplan :
>>>
 Hi,

 What version of manageiq you are using?
 We had a bug https://bugzilla.redhat.com/1542152 (upstream -
 https://bugzilla.redhat.com/1542063) that was fixed in version 5.9.0.20

 Please let me know it upgrading the version helped you.

 Thanks,
 Alona.

 On Wed, Feb 14, 2018 at 2:32 PM, Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com> wrote:

> Good afternoon!
> I read your article - https://www.ovirt.org/develop/
> release-management/features/network/manageiq_ovn/. I have only one
> question: how to create a network or subnet in Manageiq + ovirt 4.2.1. 
> When
> I try to create a network, I need to select a tenant, but there is nothing
> that I could choose. How can it be?
>
> Sincerely. Alexey Nazarenko
>


>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to put Host into Maintenance mode

[Reznikov Alexei]

15.02.2018 14:06, Mark Steele пишет:

Consider manual intervention


vdsClient -s 0 list table on your host

and then vdsClient -s 0 destroy vmID

Regards,

Alex.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Unable to put Host into Maintenance mode

[Mark Steele]

I have a host that is currently reporting down with NO VM's on it or
associated with it. However when I attempt to put it into maintenance mode,
I get the following error:

Host hv-01 cannot change into maintenance mode - not all Vms have been
migrated successfully. Consider manual intervention: stopping/migrating
Vms:  (User: admin)

I am running
oVirt Engine Version: 3.5.0.1-1.el6

***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ERROR - some other host already uses IP ###.###.###.###

[Mark Steele]

Good morning,

We had a storage crash early this morning that messed up a couple of our
ovirt hosts. Networking seemed to be the biggest issue. I have decided to
remove the bridge information in /etc/sysconfig/network-scripts and ip the
nics in order to re-import them into my ovirt installation (I have already
removed the hosts).

One of the NIC's refuses to come up and is generating the following error:

ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Error, some other
host (0C:C4:7A:5B:11:5C) already uses address ###.###.###.###.

When I ARP on this server, I do not see that Mac address - and none of my
other hosts are using it either. I'm not sure where to go next other than
completely reinstalling Centos on this server and starting over.

Ovirt version is oVirt Engine Version: 3.5.0.1-1.el6

OS version is

CentOS Linux release 7.4.1708 (Core)


Thank you

***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] VDSM SSL validity

[Punaatua PAINT-KOUI]

 Hi,

I setup an hyperconverged solution with 3 nodes, hosted engine on glusterfs.
We run this setup in a PCI-DSS environment. According to PCI-DSS
requirements, we are required to reduce the validity of any certificate
under 39 months.

I saw in this link
https://www.ovirt.org/develop/release-management/features/infra/pki/ that i
can use the option VdsCertificateValidityInYears at engine-config.

I'm running ovirt engine 4.2.1 and i checked when i was on 4.2 how to edit
the option with engine-config --all and engine-config --list but the option
is not listed

Am i missing something ?

I thing i can regenerate a VDSM certificate with openssl and the CA conf in
/etc/pki/ovirt-engine on the hosted-engine but i would rather modifiy the
option for future host that I will add.

-- 
-
PAINT-KOUI Punaatua
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted engine install fails on useless DHCP lookup

[Simone Tiraboschi]

On Thu, Feb 15, 2018 at 1:08 AM, Jamie Lawrence 
wrote:

> > On Feb 14, 2018, at 1:27 AM, Simone Tiraboschi 
> wrote:
> > On Wed, Feb 14, 2018 at 2:11 AM, Jamie Lawrence <
> jlawre...@squaretrade.com> wrote:
> > Hello,
> >
> > I'm seeing the hosted engine install fail on an Ansible playbook step.
> Log below. I tried looking at the file specified for retry, below
> (/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.retry);
> it contains the word, 'localhost'.
> >
> > The log below didn't contain anything I could see that was actionable;
> given that it was an ansible error, I hunted down the config and enabled
> logging. On this run the error was different - the installer log was the
> same, but the reported error (from the installer changed).
> >
> > The first time, the installer said:
> >
> > [ INFO  ] TASK [Wait for the host to become non operational]
> > [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts":
> {"ovirt_hosts": []}, "attempts": 150, "changed": false}
> > [ ERROR ] Failed to execute stage 'Closing up': Failed executing
> ansible-playbook
> > [ INFO  ] Stage: Clean up
> >
> > 'localhost' here is not an issue by itself: the playbook is executed on
> the host against the same host over a local connection so localhost is
> absolutely fine there.
> >
> > Maybe you hit this one:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1540451
>
> That seems likely.
>

At the point the engine VM is up but you can reach it only from that host
since it's on a natted network.
I'd suggest to connect to the engine VM from there and check host-deploy
logs.


>
>
> > It seams NetworkManager related but still not that clear.
> > Stopping NetworkManager and starting network before the deployment seams
> to help.
>
> Tried this, got the same results.
>
> [snip]
> > Anyone see what is wrong here?
> >
> > This is absolutely fine.
> > The new ansible based flow (also called node zero) uses an engine
> running on a local virtual machine to bootstrap the system.
> > The bootstrap local VM runs over libvirt default natted network with its
> own dhcp instance, that's why we are consuming it.
> > The locally running engine will create a target virtual machine on the
> shared storage and that one will be instead configured as you specified.
>
> Thanks for the context - that's useful, and presumably explains why
> 192.168 addresses  (which we don't use) are appearing in the logs.
>
> Not being entirely sure where to go from here, I guess I'll spend the
> evening figuring out ansible-ese in order to try to figure out why it is
> blowing chunks.
>
> Thanks for the note.
>
> -j
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users