Re: [ovirt-users] unable to pull 2 gluster nodes into ovirt

[Sahina Bose]

>From the host-deploy logs - the error seems to be "RuntimeError: Failed to
start service 'glusterd'"

Can you try to start the glusterd service (systemctl start glusterd) on the
failed nodes? Please attach
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log to analyze the failure.

On Wed, Nov 2, 2016 at 4:31 AM, Thing  wrote:

> DNS responds fine,
>
> ==
> [root@ovirt1 host-deploy]# host 192.168.1.31
> 31.1.168.192.in-addr.arpa domain name pointer
> glusterp1.ods.graywitch.co.nz.
> [root@ovirt1 host-deploy]# host 192.168.1.32
> 32.1.168.192.in-addr.arpa domain name pointer
> glusterp2.ods.graywitch.co.nz.
> [root@ovirt1 host-deploy]# host 192.168.1.33
> 33.1.168.192.in-addr.arpa domain name pointer
> glusterp3.ods.graywitch.co.nz.
> [root@ovirt1 host-deploy]# host 192.168.1.34
> 34.1.168.192.in-addr.arpa domain name pointer ovirt1.ods.graywitch.co.nz.
> [root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
> glusterp1.ods.graywitch.co.nz has address 192.168.1.31
> [root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
> glusterp2.ods.graywitch.co.nz has address 192.168.1.32
> [root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
> glusterp3.ods.graywitch.co.nz has address 192.168.1.33
> [root@ovirt1 host-deploy]# more /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4
> localhost4.localdomain4
> ::1 localhost localhost.localdomain localhost6
> localhost6.localdomain6
> 192.168.1.31glusterp1.ods.graywitch.co.nz   glusterp1
> 192.168.1.32glusterp2.ods.graywitch.co.nz   glusterp2
> 192.168.1.33glusterp3.ods.graywitch.co.nz   glusterp3
> 192.168.1.34ovirt1.ods.graywitch.co.nzovirt1
> [root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
> glusterp1.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp1.ods.graywitch.co.nz
> Address: 192.168.1.31#53
> Aliases:
>
> glusterp2.ods.graywitch.co.nz has address 192.168.1.32
> [root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
> glusterp1.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp1.ods.graywitch.co.nz
> Address: 192.168.1.31#53
> Aliases:
>
> glusterp1.ods.graywitch.co.nz has address 192.168.1.31
> [root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
> glusterp1.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp1.ods.graywitch.co.nz
> Address: 192.168.1.31#53
> Aliases:
>
> glusterp3.ods.graywitch.co.nz has address 192.168.1.33
> [root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
> glusterp2.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp2.ods.graywitch.co.nz
> Address: 192.168.1.32#53
> Aliases:
>
> glusterp2.ods.graywitch.co.nz has address 192.168.1.32
> [root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
> glusterp2.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp2.ods.graywitch.co.nz
> Address: 192.168.1.32#53
> Aliases:
>
> glusterp1.ods.graywitch.co.nz has address 192.168.1.31
> [root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
> glusterp2.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp2.ods.graywitch.co.nz
> Address: 192.168.1.32#53
> Aliases:
>
> glusterp3.ods.graywitch.co.nz has address 192.168.1.33
> [root@ovirt1 host-deploy]# host ovirt1.ods.graywitch.co.nz
> glusterp2.ods.graywitch.co.nz
> Using domain server:
> Name: glusterp2.ods.graywitch.co.nz
> Address: 192.168.1.32#53
> Aliases:
>
> ovirt1.ods.graywitch.co.nz has address 192.168.1.34
> [root@ovirt1 host-deploy]#
> ==
>
> ssh keys work fine from the command line,
>
> ==
> [root@ovirt1 host-deploy]# uname -a
> Linux ovirt1.ods.graywitch.co.nz 3.10.0-327.36.2.el7.x86_64 #1 SMP Mon
> Oct 10 23:08:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [root@ovirt1 host-deploy]# ssh glusterp1
> Last login: Wed Nov  2 10:46:58 2016 from ovirt1.ods.graywitch.co.nz
> [root@glusterp1 ~]# ^C
> [root@glusterp1 ~]# logout
> Connection to glusterp1 closed.
> [root@ovirt1 host-deploy]# ssh glusterp2
> Last login: Wed Nov  2 10:14:09 2016
> [root@glusterp2 ~]# logout
> Connection to glusterp2 closed.
> [root@ovirt1 host-deploy]# ssh glusterp3
> Last login: Wed Nov  2 10:14:19 2016
> [root@glusterp3 ~]# logout
> Connection to glusterp3 closed.
> [root@ovirt1 host-deploy]#
> ==
>
> iptables is disabled,
>
> 
> [root@glusterp2 log]# iptables -L -n
> Chain INPUT (policy ACCEPT)
> target prot opt source   destination
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source   destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source   destination
> [root@glusterp2 log]#
> =
>
>
>
>
>
>
>
> On 2 November 2016 at 11:24, Thing  wrote:
>
>> I have 3 gluster nodes, 1 and 2 repeatedly fail to come in to ovirt but
>> node 3 worked first time.
>>
>> It appears to be saying ssh-keys / root password is failing, but I can
>> ssh in fine from teh command line so this message makes no 

[ovirt-users] SSL Certificates

[Gary Pedretty]

Where do you install a real non self-signed certificate  for use in the Ovirt 
Web Management Console.

Gary

Gary Pedrettyg...@ravnalaska.net 

Systems Manager  www.flyravn.com 

Ravn Alaska   /\907-450-7251
5245 Airport Industrial Road /  \/\ 907-450-7238 fax
Fairbanks, Alaska  99709/\  /\ \ Second greatest commandment
Serving All of Alaska  /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39













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

Re: [ovirt-users] unable to pull 2 gluster nodes into ovirt

[Thing]

DNS responds fine,

==
[root@ovirt1 host-deploy]# host 192.168.1.31
31.1.168.192.in-addr.arpa domain name pointer glusterp1.ods.graywitch.co.nz.
[root@ovirt1 host-deploy]# host 192.168.1.32
32.1.168.192.in-addr.arpa domain name pointer glusterp2.ods.graywitch.co.nz.
[root@ovirt1 host-deploy]# host 192.168.1.33
33.1.168.192.in-addr.arpa domain name pointer glusterp3.ods.graywitch.co.nz.
[root@ovirt1 host-deploy]# host 192.168.1.34
34.1.168.192.in-addr.arpa domain name pointer ovirt1.ods.graywitch.co.nz.
[root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
glusterp1.ods.graywitch.co.nz has address 192.168.1.31
[root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
glusterp2.ods.graywitch.co.nz has address 192.168.1.32
[root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
glusterp3.ods.graywitch.co.nz has address 192.168.1.33
[root@ovirt1 host-deploy]# more /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4
localhost4.localdomain4
::1 localhost localhost.localdomain localhost6
localhost6.localdomain6
192.168.1.31glusterp1.ods.graywitch.co.nz   glusterp1
192.168.1.32glusterp2.ods.graywitch.co.nz   glusterp2
192.168.1.33glusterp3.ods.graywitch.co.nz   glusterp3
192.168.1.34ovirt1.ods.graywitch.co.nzovirt1
[root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
glusterp1.ods.graywitch.co.nz
Using domain server:
Name: glusterp1.ods.graywitch.co.nz
Address: 192.168.1.31#53
Aliases:

glusterp2.ods.graywitch.co.nz has address 192.168.1.32
[root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
glusterp1.ods.graywitch.co.nz
Using domain server:
Name: glusterp1.ods.graywitch.co.nz
Address: 192.168.1.31#53
Aliases:

glusterp1.ods.graywitch.co.nz has address 192.168.1.31
[root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
glusterp1.ods.graywitch.co.nz
Using domain server:
Name: glusterp1.ods.graywitch.co.nz
Address: 192.168.1.31#53
Aliases:

glusterp3.ods.graywitch.co.nz has address 192.168.1.33
[root@ovirt1 host-deploy]# host glusterp2.ods.graywitch.co.nz
glusterp2.ods.graywitch.co.nz
Using domain server:
Name: glusterp2.ods.graywitch.co.nz
Address: 192.168.1.32#53
Aliases:

glusterp2.ods.graywitch.co.nz has address 192.168.1.32
[root@ovirt1 host-deploy]# host glusterp1.ods.graywitch.co.nz
glusterp2.ods.graywitch.co.nz
Using domain server:
Name: glusterp2.ods.graywitch.co.nz
Address: 192.168.1.32#53
Aliases:

glusterp1.ods.graywitch.co.nz has address 192.168.1.31
[root@ovirt1 host-deploy]# host glusterp3.ods.graywitch.co.nz
glusterp2.ods.graywitch.co.nz
Using domain server:
Name: glusterp2.ods.graywitch.co.nz
Address: 192.168.1.32#53
Aliases:

glusterp3.ods.graywitch.co.nz has address 192.168.1.33
[root@ovirt1 host-deploy]# host ovirt1.ods.graywitch.co.nz
glusterp2.ods.graywitch.co.nz
Using domain server:
Name: glusterp2.ods.graywitch.co.nz
Address: 192.168.1.32#53
Aliases:

ovirt1.ods.graywitch.co.nz has address 192.168.1.34
[root@ovirt1 host-deploy]#
==

ssh keys work fine from the command line,

==
[root@ovirt1 host-deploy]# uname -a
Linux ovirt1.ods.graywitch.co.nz 3.10.0-327.36.2.el7.x86_64 #1 SMP Mon Oct
10 23:08:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@ovirt1 host-deploy]# ssh glusterp1
Last login: Wed Nov  2 10:46:58 2016 from ovirt1.ods.graywitch.co.nz
[root@glusterp1 ~]# ^C
[root@glusterp1 ~]# logout
Connection to glusterp1 closed.
[root@ovirt1 host-deploy]# ssh glusterp2
Last login: Wed Nov  2 10:14:09 2016
[root@glusterp2 ~]# logout
Connection to glusterp2 closed.
[root@ovirt1 host-deploy]# ssh glusterp3
Last login: Wed Nov  2 10:14:19 2016
[root@glusterp3 ~]# logout
Connection to glusterp3 closed.
[root@ovirt1 host-deploy]#
==

iptables is disabled,


[root@glusterp2 log]# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
[root@glusterp2 log]#
=







On 2 November 2016 at 11:24, Thing  wrote:

> I have 3 gluster nodes, 1 and 2 repeatedly fail to come in to ovirt but
> node 3 worked first time.
>
> It appears to be saying ssh-keys / root password is failing, but I can ssh
> in fine from teh command line so this message makes no sense.
>
> attached is a host deploy log
>
>
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt 4.0.4?==?utf-8?q? : unable to upload images

[Claude Durocher]

We have a setup with ovirt 4.0.4 (hosted engine) and I try to import a Ubuntu 
qcow cloud image. When I try to import, it stops with the error 'Unable to 
upload image to disk ... due to a network error. Make sure ovirt-imageio-proxy 
service is installed and configured, and ovirt-engine's certificate is 
registered as a valid CA in the browser'.

The ovirt-imageio-proxy service is running on the engine.  No errors in the log 
(just a mention that the service has started up). I also imported the server CA 
in my browser (Firefox 49 on Ubuntu).
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Storage VLAN Issue

[Kendal Montgomery]

I finally got around to re-creating this scenario, only I did it with version 
4.0.4 and I did not experience the same problem so I guess I would consider it 
fixed.

Thanks!

Kendal Montgomery
Lab Manager
Columbus Collaboratory
614-407-5584

Get Outlook for Android

From: Edward Haas
Sent: Sunday, August 21, 3:00 AM
Subject: Re: [ovirt-users] Storage VLAN Issue
To: Kendal Montgomery
Cc: users@ovirt.org



On Wed, Aug 17, 2016 at 2:49 PM, Kendal Montgomery 
> 
wrote:

Hi all,

I just recently started testing out oVirt in our lab.  I'm using CentOS 7 on my 
hosts and using the hosted-engine model, and the oVirt 3.6 repository.  I have 
NFS storage.  I ran across what I think is a bug of some sort, and I'm curious 
if anyone else has tried this or know what's going on.

I wanted to be able to expose the NFS server (not necessarily the share used 
for oVirt storage domains, but other shares on the NFS server) to VMs running 
on my host (currently my setup only involves a single host). I have two 
10GbaseT interfaced bonded together on the hose with two VLAN networks on it 
currently, one for the management network, one for storage.  When the 
hosted-engine deployment was set up, I ended up with an ovirtmgmt interface 
that was bridged to my infrastructure vlan interface (vlan 1080).  So, I added 
another network in my oVirt cluster named VM-Storage with vlan 1092 (my storage 
network).  Here is approximately how I expected this to end up:

bond0 - (bonded interface)

  - bond0.1092 (STORAGE - vlan interface)

 - VM-storage (bridged interface)

  - bond0.1080 (INFR - van interface)

- ovirtmgmt (bridged interface)

However, when I did network setup on the host, and dragged the VM-Storage 
network over to the network interface and hit OK, the UI just froze, and for a 
few seconds I checked on the host via ssh session and the VM-storage bridge was 
setup, then the server just rebooted.  After it rebooted, my vlan interface was 
no longer there and it seems like both the hosted engine VM and the host ended 
up being rebooted.  In thinking about it, I may have caused at least a 
temporary outage with my NFS storage when the new bridged interface was set up 
which caused (maybe) the HA agent to think the hosted engine vm went away or 
something, and that cause the reboots.  Not entirely sure, but this was 
certainly unexpected.  I have tried several times and the same result each time.

I did check that any other VM network with a different VLAN ID provisions just 
fine on the host, so I assume there's something that happens when this storage 
network is provisioned that is catching oVirt off-guard somehow.

Anyone else have this issue before?  Can I solve this by adding another host, 
then moving the hosted-engine to a different host while I add the storage 
network to each host?

Thanks.

Kendal Montgomery

Lab Manager

O: 614.407.5584 | M: 614.571.0172

kmontgom...@cbuscollaboratory.com


Hi Kendal,

Please provide the logs from your host: Especially messages, vdsm.log and 
supervdsm.log.
ovirtmgmt network is set as a VLAN network in Engine? ( a screenshot of your 
network configuration on Engine may help)

Thanks,

Edy.


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

Re: [ovirt-users] Hosted Engine CPU usage always shows 100%

[knarra]

On 10/27/2016 07:10 PM, Simone Tiraboschi wrote:



On Thu, Oct 27, 2016 at 3:33 PM, knarra > wrote:


On 10/27/2016 06:42 PM, Simone Tiraboschi wrote:



On Thu, Oct 27, 2016 at 2:56 PM, knarra > wrote:

Hi Simone,

I see that this patch is merged upstream. I have
installed latest master. But i still see that HostedEngine
CPU shows 100%. Is there something i am missing here?


So maybe it's an unrelated bug.
Do you see the same behavior if you directly check the CPU on the
VM with top?


Thanks
kasturi


Hi simone,

I directly checked it on my machine and i see that the CPU
utilization is very less .

top - 13:33:12 up 32 min,  1 user,  load average: 0.69, 0.66, 0.57
Tasks: 150 total,   1 running, 149 sleeping,   0 stopped,   0 zombie
%Cpu(s):  8.3 us,  9.0 sy,  0.0 ni, 82.5 id,  0.0 wa, 0.0 hi,  0.2
si,  0.0 st


OK, can you please file a bug?



Thanks
kasturi


Hi Simone,

I have filed bug for the same and here is the bug id 
https://bugzilla.redhat.com/show_bug.cgi?id=1390675. I have put the 
ovirt team as Infra and assigned the bug to you. Could you please let me 
know which ovirt team should i be selecting ?


Thanks
kasturi.





On 10/19/2016 10:33 PM, Simone Tiraboschi wrote:



On Wed, Oct 19, 2016 at 3:13 PM, knarra > wrote:

On 10/19/2016 06:43 PM, knarra wrote:

Hi,

I have latest ovirt master and i see that Hosted
Engine CPU is always shown 100%. But the actual
usage in the system is very less.  Is this a known
issue or a bug ?


https://bugzilla.redhat.com/show_bug.cgi?id=1381899
 should
strongly reduce it.
Kasturi, can you please try
https://gerrit.ovirt.org/#/c/65230/
 ?



Thanks

kasturi

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



Attaching the screenshot for the same.


___
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] mass upload of disks?

[Daniel Erez]

On Tue, Nov 1, 2016 at 3:27 PM, Ben De Luca  wrote:

> Could I set up glance for this?
>

You can upload the files to glance first, then import them to oVirt using
the rest-api.

E.g.
POST /ovirt-engine/api/openstackimageproviders/123/images/456/import




images0





>
> On 31 October 2016 at 23:42, Ben De Luca  wrote:
>
>> That's probably a little bit more brave than I am, so there is no way in
>> the current release? I don't mind jumping through a few hoops but sitting
>> for days loading them doesn't fill me joy.
>>
>> If not it's great that feature is added.
>>
>>
>>
>>
>> On Monday, 31 October 2016, Amit Aviram  wrote:
>>
>>> Hi Ben. Actually exactly today REST API for uploading disks was
>>> introduced to master. It is supposed to get into the next 4.0.Z version, so
>>> if you want you can update your version soon enough and use the API.
>>>
>>> When you'll have the right version, you can use examples from
>>> "/api/Model" to upload disks using oVirt's Python SDK.
>>>
>>> If you need any help, please feel free to keep asking on the list.
>>>
>>> Amit.
>>>
>>> On Mon, Oct 31, 2016 at 7:22 PM, Ben De Luca  wrote:
>>>
 Hi,
 I was wondering if there was a method on the cli/script to mass
 upload disks to ovirt. The web loader is great, but also I have 20 disks
 that I really just want to upload via shell.

 I can't seem to find a tool to do it, I have found
 ovirt-image-uploader (but that's for ovf files).

 I hoped that I could just pull the date directly off nfs but that
 doesnt seem to be possible, or I am blind?

 Thanks
 -Ben





 ___
 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] mass upload of disks?

[Ben De Luca]

reading through the mailing list some one suggested glance? I can build a
glance server reference that and then copy in the disks?

On 1 November 2016 at 17:20, Amit Aviram  wrote:

>
>
> On Tue, Nov 1, 2016 at 3:27 PM, Ben De Luca  wrote:
>
>> Could I set up glance for this?
>>
>
>> On 31 October 2016 at 23:42, Ben De Luca  wrote:
>>
>>> That's probably a little bit more brave than I am, so there is no way in
>>> the current release? I don't mind jumping through a few hoops but sitting
>>> for days loading them doesn't fill me joy.
>>
>>
> Unfortunately besides the new API and ovirt-image-uploader there is no
> other way for uploading disks.
>
>
>>
>>> If not it's great that feature is added.
>>>
>>>
>>>
>>>
>>> On Monday, 31 October 2016, Amit Aviram  wrote:
>>>
 Hi Ben. Actually exactly today REST API for uploading disks was
 introduced to master. It is supposed to get into the next 4.0.Z version, so
 if you want you can update your version soon enough and use the API.

 When you'll have the right version, you can use examples from
 "/api/Model" to upload disks using oVirt's Python SDK.

 If you need any help, please feel free to keep asking on the list.

 Amit.

 On Mon, Oct 31, 2016 at 7:22 PM, Ben De Luca  wrote:

> Hi,
> I was wondering if there was a method on the cli/script to mass
> upload disks to ovirt. The web loader is great, but also I have 20 disks
> that I really just want to upload via shell.
>
> I can't seem to find a tool to do it, I have found
> ovirt-image-uploader (but that's for ovf files).
>
> I hoped that I could just pull the date directly off nfs but that
> doesnt seem to be possible, or I am blind?
>
> Thanks
> -Ben
>
>
>
>
>
> ___
> 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] mass upload of disks?

[Amit Aviram]

On Tue, Nov 1, 2016 at 3:27 PM, Ben De Luca  wrote:

> Could I set up glance for this?
>

> On 31 October 2016 at 23:42, Ben De Luca  wrote:
>
>> That's probably a little bit more brave than I am, so there is no way in
>> the current release? I don't mind jumping through a few hoops but sitting
>> for days loading them doesn't fill me joy.
>
>
Unfortunately besides the new API and ovirt-image-uploader there is no
other way for uploading disks.


>
>> If not it's great that feature is added.
>>
>>
>>
>>
>> On Monday, 31 October 2016, Amit Aviram  wrote:
>>
>>> Hi Ben. Actually exactly today REST API for uploading disks was
>>> introduced to master. It is supposed to get into the next 4.0.Z version, so
>>> if you want you can update your version soon enough and use the API.
>>>
>>> When you'll have the right version, you can use examples from
>>> "/api/Model" to upload disks using oVirt's Python SDK.
>>>
>>> If you need any help, please feel free to keep asking on the list.
>>>
>>> Amit.
>>>
>>> On Mon, Oct 31, 2016 at 7:22 PM, Ben De Luca  wrote:
>>>
 Hi,
 I was wondering if there was a method on the cli/script to mass
 upload disks to ovirt. The web loader is great, but also I have 20 disks
 that I really just want to upload via shell.

 I can't seem to find a tool to do it, I have found
 ovirt-image-uploader (but that's for ovf files).

 I hoped that I could just pull the date directly off nfs but that
 doesnt seem to be possible, or I am blind?

 Thanks
 -Ben





 ___
 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] mass upload of disks?

[Ben De Luca]

Could I set up glance for this?

On 31 October 2016 at 23:42, Ben De Luca  wrote:

> That's probably a little bit more brave than I am, so there is no way in
> the current release? I don't mind jumping through a few hoops but sitting
> for days loading them doesn't fill me joy.
>
> If not it's great that feature is added.
>
>
>
>
> On Monday, 31 October 2016, Amit Aviram  wrote:
>
>> Hi Ben. Actually exactly today REST API for uploading disks was
>> introduced to master. It is supposed to get into the next 4.0.Z version, so
>> if you want you can update your version soon enough and use the API.
>>
>> When you'll have the right version, you can use examples from
>> "/api/Model" to upload disks using oVirt's Python SDK.
>>
>> If you need any help, please feel free to keep asking on the list.
>>
>> Amit.
>>
>> On Mon, Oct 31, 2016 at 7:22 PM, Ben De Luca  wrote:
>>
>>> Hi,
>>> I was wondering if there was a method on the cli/script to mass
>>> upload disks to ovirt. The web loader is great, but also I have 20 disks
>>> that I really just want to upload via shell.
>>>
>>> I can't seem to find a tool to do it, I have found
>>> ovirt-image-uploader (but that's for ovf files).
>>>
>>> I hoped that I could just pull the date directly off nfs but that
>>> doesnt seem to be possible, or I am blind?
>>>
>>> Thanks
>>> -Ben
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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] desktop version of client?

[Gianluca Cecchi]

On Sat, Oct 29, 2016 at 11:23 AM, James Michels <
karma.sometimes.hu...@gmail.com> wrote:

> Hello Amy.
>
> We had the same needs back in July as we have some classrooms with thin
> clients and although we don't just offer the oVirt service we wanted
> something simple so users don't need to open a browser and just handle
> their machines in a simple way, so I found this project [1] that works
> quite fine for what we need. Manage virtual machine's power and start a
> viewer. Period. No more funcionalities (not sure if you need something more
> sophisticated...).
>
> The project has been stopped for a time but it seems that the maintainer
> is implementing new capabilities and fixing some things lately.
>
> As a side note, you didn't mention if your thin clients are linux or
> windows based but I believe this is for linux only.
>
> HTH,
>
> James
>
> [1] https://ovirt-desktop-client.click
>
>
Hello,
thanks for reporting about this project I didn't know about.

By the way on a Fedora 24 client I was able to successfully test it without
the need to create a python virtual environment

This is with python 2 present in F24 (not tested with the alternative
python 3 Python 3.5.1):
$ python -V
Python 2.7.12

and the currently provided packages:

sip-4.18-2.fc24.x86_64
python-qt5-5.6-4.fc24.x86_6

I was able to then run

python ovirtclient.py

I was not able to using anyway virtualenv (both 2 and 3 versions) that
seems anyway sort of broken
Without --always-copy switch the sip compilation tried to remove the
provided sip.so and clearly it failed
With --always-copy I got errors able to temporarily fix changing fix_lib64
function but then error again about importing _io

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

Re: [ovirt-users] can not use iscsi storage type on ovirt and Glusterfs hyper-converged environment

[Maor Lipchuk]

Hi 胡茂荣Can u please also add the VDSM and engine logs.
If you try discover and connect to those luns directly from your Host does
it work?

Regards,
Maor


On Tue, Nov 1, 2016 at 6:12 AM, 胡茂荣  wrote:

>
>
> on ovirt and Glusterfs hyper-converged environment , can not use iscsi
> storage type , UI report error: "Could not retrieve LUNs, please check
> your storage." , vdsm report :"VDSM hosted_engine_3 command failed: Error
> block device action: ()" .
> but this block device alse login on centos 7 host :
> =
>
> ## lsscsi
>
> [7:0:0:0]diskSCST_BIO DEVFOR_OVIRT_rbd  221  /dev/sdi
>
>   ## dmesg :
>
> [684521.131186] sd 7:0:0:0: [sdi] Attached SCSI disk
>
> ===---
>
>###vdsm or supervdsm log  report :
>
> MainProcess|jsonrpc.Executor/7::ERROR::2016-11-01
> 11:07:00,178::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper)
> Error in getPathsStatus
>
> MainProcess|jsonrpc.Executor/4::ERROR::2016-11-01
> 11:07:20,964::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper)
> Error in getPathsStatus
>
>jsonrpc.Executor/4::DEBUG::2016-11-01 
> 11:07:04,251::iscsi::434::Storage.ISCSI::(rescan)
> Performing SCSI scan, this will take up to 30 seconds
>
> jsonrpc.Executor/5::INFO::2016-11-01 11:07:19,413::iscsi::567::
> Storage.ISCSI::(setRpFilterIfNeeded) iSCSI iface.net_ifacename not
> provided. Skipping.
>
> 11:09:15,753::iscsiadm::119::Storage.Misc.excCmd::(_runCmd)
> /usr/bin/taskset --cpu-list 0-7 /usr/bin/sudo -n /usr/sbin/iscsiadm -m
> session -R (cwd None)
>
> ==
>
>  the other info please the attachment "bug-info.doc".
>
>  this prolem on ovirt3.6 and 4.X  ovirt and Glusterfs hyper-converged
> environment . how can I use iscsi storage type on ovirt and Glusterfs
> hyper-converged environment .Please help me !
>
> humaorong
>
>2016-11-1
>
>
>
>
>
>
>
> ___
> 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] Upgrading oVirt 3.6 with existing HTTPS certificate signed by custom CA to oVirt 4

[Martin Perina]

On Tue, Nov 1, 2016 at 11:49 AM, Martin Perina  wrote:

> So first of all, we don't support replacing oVirt internal CA which is
> used to sign host certificates. This internal CA is also used to sign HTTPS
> certificate by default, but you can provided your own HTTPS certificate
> signed by custom CA. The correct steps how to do that are (assuming you
> have you custom CA certififcate in PEM format and HTTPS ceritificate along
> with private key in PKCS12 format):
>
> 1.  Add your commercially issued certificate to the host-wide trust store.
>cp YOUR-3RD-PARTY-CA-CERT.pem /etc/pki/ca-trust/source/anchors
>update-ca-trust
>
> 2. Remove Apache CA link pointing to oVirt internal
>rm /etc/pki/ovirt-engine/apache-ca.pem
>
> 3. Install your custom certificate (including complete certificate chain)
>mv YOUR-3RD-PARTY-CA-CERT.pem /etc/pki/ovirt-engine/apache-ca.pem
>

  mv YOUR-3RD-PART-CERT.p12
​​​/etc/pki/ovirt-engine/keys/apache.p12​

The above command was missing in original steps, thanks Didi for pointing
this out.
​


>
> 4. Extract private key and certificate
>
> ​ ​
> openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nocerts -nodes
> > /etc/pki/ovirt-engine/keys/apache.key.nopass
> ​   ​
> openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nokeys >
> /etc/pki/ovirt-engine/certs/apache.cer
>
> ​5. Restart Apache
>   service httpd restart
>
> 6. Create a new trust store configuration file.
>   vi /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf
>
>Add the following content and save the file.
>
>   ENGINE_HTTPS_PKI_TRUST_STORE="/etc/pki/java/cacerts"
>   ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD=""
>
> 7. Restart the ovirt-engine service.
>   systemctl restart ovirt-engine.service​
>
>
> ​Steps 1., 6. and 7. are new to 4.0, other steps are same as in oVirt 3.x​
>
> ​Also it's expected that CA certificate (including whole CA chain) is
> properly installed in all clients that access oVirt using HTTP and/or
> Spice.​
>
> ​Martin Perina​
>
>
>
>
> On Thu, Oct 27, 2016 at 10:38 PM, Kenneth Bingham  wrote:
>
>> That makes sense, but it is also disappointing to realize that oVirt
>> Manager will only trust certificates that itself has issued, and that there
>> is no support for Manager to trust VDSM server certificates issued by
>> another authority.
>>
>> If I understand you correctly, then the *only* way to install a VDSM host
>> certificate is by registering with Manager at which time a certificate is
>> automatically issued and installed by Manager's built-in certificate
>> authority.
>>
>>
>> On Thu, Oct 27, 2016 at 3:27 PM Ravi Nori  wrote:
>>
>> Since you replace ca.pem you need to replace the private key of ca.pem
>>
>> Please copy the private key of  /etc/pki/ovirt-engine/ca.pem to
>> /etc/pki/ovirt-engine/private/ca.pem and let me know if everything works
>>
>> On Thu, Oct 27, 2016 at 2:47 PM, Kenneth Bingham  wrote:
>>
>>
>> Thanks Ravi, that's helpful and I appreciate the precision and attention
>> to detail. I performed similar steps to install a custom certificate for
>> the oVirt Manager GUI. But what about configuring ovirt-engine to trust a
>> certificate issued by the same CA and presented by the VDSM host? On the
>> hypervisor host, I used the existing private key to generate the CSR,
>> issued the server certificate, and installed in three locations before
>> bouncing vdsmd.
>>
>> On the hypervisor Host server (not the Manager/engine server):
>> /etc/pki/vdsm/certs/vdsmcert.pem
>> /etc/pki/vdsm/libvirt-spice/server-cert.pem
>> /etc/pki/libvirt/clientcert.pem
>>
>> Now, that host is "non responsive" in Manager because ovirt-engine does
>> not trust the new certificate even though I already performed all of the
>> steps that you describe above except that I installed the issuer's CA
>> certificate as the trusted entity. I've documented all of the steps I took in
>> this Gist
>> .
>>
>>
>>
>> On Thu, Oct 27, 2016 at 2:12 PM Ravi Nori  wrote:
>>
>> Here is a complete set of instructions that works for me
>>
>> You can skip the first few steps of generating the certificate.
>>
>> Ravi
>>
>>
>> Generate a self-signed certificate using openssl
>> ==
>> openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout
>> privateKey.key -out certificate.pem
>>
>> Convert a PEM certificate file and a private key to PKCS#12 (.p12)
>> =
>> openssl pkcs12 -export -out certificate.p12 -inkey privateKey.key -in
>> certificate.pem
>>
>> Extract the key from the bundle
>> =
>> openssl pkcs12 -in  certificate.p12 -nocerts -nodes > apache.key.nopass
>>
>> Extract the certificate from the bundle
>> ==
>> openssl pkcs12 -in 

Re: [ovirt-users] Upgrading oVirt 3.6 with existing HTTPS certificate signed by custom CA to oVirt 4

[Martin Perina]

So first of all, we don't support replacing oVirt internal CA which is used
to sign host certificates. This internal CA is also used to sign HTTPS
certificate by default, but you can provided your own HTTPS certificate
signed by custom CA. The correct steps how to do that are (assuming you
have you custom CA certififcate in PEM format and HTTPS ceritificate along
with private key in PKCS12 format):

1.  Add your commercially issued certificate to the host-wide trust store.
   cp YOUR-3RD-PARTY-CA-CERT.pem /etc/pki/ca-trust/source/anchors
   update-ca-trust

2. Remove Apache CA link pointing to oVirt internal
   rm /etc/pki/ovirt-engine/apache-ca.pem

3. Install your custom certificate (including complete certificate chain)
   mv YOUR-3RD-PARTY-CA-CERT.pem /etc/pki/ovirt-engine/apache-ca.pem

4. Extract private key and certificate

​ ​
openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nocerts -nodes >
/etc/pki/ovirt-engine/keys/apache.key.nopass
​   ​
openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nokeys >
/etc/pki/ovirt-engine/certs/apache.cer

​5. Restart Apache
  service httpd restart

6. Create a new trust store configuration file.
  vi /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf

   Add the following content and save the file.

  ENGINE_HTTPS_PKI_TRUST_STORE="/etc/pki/java/cacerts"
  ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD=""

7. Restart the ovirt-engine service.
  systemctl restart ovirt-engine.service​


​Steps 1., 6. and 7. are new to 4.0, other steps are same as in oVirt 3.x​

​Also it's expected that CA certificate (including whole CA chain) is
properly installed in all clients that access oVirt using HTTP and/or
Spice.​

​Martin Perina​




On Thu, Oct 27, 2016 at 10:38 PM, Kenneth Bingham  wrote:

> That makes sense, but it is also disappointing to realize that oVirt
> Manager will only trust certificates that itself has issued, and that there
> is no support for Manager to trust VDSM server certificates issued by
> another authority.
>
> If I understand you correctly, then the *only* way to install a VDSM host
> certificate is by registering with Manager at which time a certificate is
> automatically issued and installed by Manager's built-in certificate
> authority.
>
>
> On Thu, Oct 27, 2016 at 3:27 PM Ravi Nori  wrote:
>
> Since you replace ca.pem you need to replace the private key of ca.pem
>
> Please copy the private key of  /etc/pki/ovirt-engine/ca.pem to
> /etc/pki/ovirt-engine/private/ca.pem and let me know if everything works
>
> On Thu, Oct 27, 2016 at 2:47 PM, Kenneth Bingham  wrote:
>
>
> Thanks Ravi, that's helpful and I appreciate the precision and attention
> to detail. I performed similar steps to install a custom certificate for
> the oVirt Manager GUI. But what about configuring ovirt-engine to trust a
> certificate issued by the same CA and presented by the VDSM host? On the
> hypervisor host, I used the existing private key to generate the CSR,
> issued the server certificate, and installed in three locations before
> bouncing vdsmd.
>
> On the hypervisor Host server (not the Manager/engine server):
> /etc/pki/vdsm/certs/vdsmcert.pem
> /etc/pki/vdsm/libvirt-spice/server-cert.pem
> /etc/pki/libvirt/clientcert.pem
>
> Now, that host is "non responsive" in Manager because ovirt-engine does
> not trust the new certificate even though I already performed all of the
> steps that you describe above except that I installed the issuer's CA
> certificate as the trusted entity. I've documented all of the steps I took in
> this Gist
> .
>
>
>
> On Thu, Oct 27, 2016 at 2:12 PM Ravi Nori  wrote:
>
> Here is a complete set of instructions that works for me
>
> You can skip the first few steps of generating the certificate.
>
> Ravi
>
>
> Generate a self-signed certificate using openssl
> ==
> openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout
> privateKey.key -out certificate.pem
>
> Convert a PEM certificate file and a private key to PKCS#12 (.p12)
> =
> openssl pkcs12 -export -out certificate.p12 -inkey privateKey.key -in
> certificate.pem
>
> Extract the key from the bundle
> =
> openssl pkcs12 -in  certificate.p12 -nocerts -nodes > apache.key.nopass
>
> Extract the certificate from the bundle
> ==
> openssl pkcs12 -in certificate.p12 -nokeys > apache.cer
>
> Create a new Keystore for testing
> ==
> keytool -keystore clientkeystore -genkey -alias client
>
> Convert .pem to .der
> 
> openssl x509 -outform der -in certificate.pem -out certificate.der
>
> Import certificates to keystore
> ===
> keytool -import -alias apache -keystore ./clientkeystore -file
> 

Re: [ovirt-users] Setting DNS servers problem on ovirt

[Edward Haas]

On Tue, Nov 1, 2016 at 9:01 AM, Yedidyah Bar David  wrote:

> On Tue, Nov 1, 2016 at 1:38 AM, Thing  wrote:
> > Hi,
> >
> > I have installed IPA across 3 nodes.  In order to point the ovirt server
> at
> > the new IPA/DNS servers and to clean up I ran engine-cleanup aiming to
> delte
> > the ovirt setup.   However it seems even though I ran this something,
> > "vdsm?" is still running and controlling the networking.
>
> engine-cleanup only cleans up the engine. It does nothing to the hosts.
> I am not aware of a similar "vdsm-cleanup" tool.
> In principle, you could have moved your hosts to maintenance and removed
> them
> from the engine. No idea what this would tell vdsm to do wrt to your
> question.
> It definitely would not undo ifcfg-* changes.
>
> >
> > So down under /etc/sysconfig/network-scripts I see,
> >
> > =
> > /etc/sysconfig/network-scripts
> > [root@ovirt1 network-scripts]# ls -l
> > total 256
> > -rw-rw-r--. 1 root root   130 Nov  1 10:32 ifcfg-enp0s25
> > -rw-r--r--. 1 root root   254 Sep 16  2015 ifcfg-lo
> > -rw-rw-r--. 1 root root   252 Nov  1 10:32 ifcfg-ovirtmgmt
> > 8><-
> > ==
> >
> > So my first Q is why when I run engine-cleanup isnt the networking
> cleaned
> > up?  should I file this as a bugzilla?
>
> See above, it's not in the scope for engine-cleanup.
>
> >
> > After that I can see that ifcfg-ovirtmgmt is still controlling DNS,
> >
> > ==
> > 8><
> > [root@ovirt1 network-scripts]# tail ifcfg-ovirtmgmt
> > ONBOOT=yes
> > IPADDR=192.168.1.34
> > NETMASK=255.255.255.0
> > GATEWAY=192.168.1.1
> > BOOTPROTO=none
> > MTU=1500
> > DEFROUTE=yes
> > NM_CONTROLLED=no
> > IPV6INIT=no
> > DNS1=192.168.1.240
> > [root@ovirt1 network-scripts]#
> > ===
> >
> > So I tried to set,
> >
> > DNS1=192.168.1.31
> > DNS2=192.168.1.32
> > DNS3=192.168.1.33
> >
> > rebooted and, no I see,
> >
> > DNS1=192.168.1.240 again
> >
> > So I also see that the vdsm service is still running,
> >
> > ==
> > [root@ovirt1 network-scripts]# systemctl status vdsm-network.service
> > ● vdsm-network.service - Virtual Desktop Server Manager network
> restoration
> >Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service;
> enabled;
> > vendor preset: enabled)
> >Active: active (exited) since Tue 2016-11-01 10:32:51 NZDT; 2h 0min
> ago
> >   Process: 2873 ExecStart=/usr/bin/vdsm-tool restore-nets (code=exited,
> > status=0/SUCCESS)
> >   Process: 2848 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append
> > --logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence
> > (code=exited, status=0/SUCCESS)
> >  Main PID: 2873 (code=exited, status=0/SUCCESS)
> >CGroup: /system.slice/vdsm-network.service
> >
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> client
> > step 2
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> > parse_server_challenge()
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> > ask_user_info()
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> client
> > step 2
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> > ask_user_info()
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> > make_client_response()
> > Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> client
> > step 3
> > Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> client
> > mech dispose
> > Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> common
> > mech dispose
> > Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz systemd[1]: Started Virtual
> > Desktop Server Manager network restoration.
> > [root@ovirt1 network-scripts]#
> > ===
> >
> > why after cleaning up is this still active?
> >
> > Next, I have grep'd under /etc/ and cannot find where its getting its
> > obsolete network DNS info info from.
>
> I think it's somewhere under /var, adding Dan.
>

If VDSM is running, any network devices it used are owned by it.
Editing manually ifcfg files it owns will result in VDSM restoring them to
their persisted state
in vdsm configuration files.

I guess, you can just uninstall/remove vdsm and continue from there: sudo
yum remove -y vdsm\*


>
> >
> > So I need to know where this info is stored? so I can edit is via the
> CLI?
> > database?
> >
> > There is no web ui running as engine-cleanup has removed that so I cant
> work
> > via the web ui.
> >
> > Is there anything else I need to manually stop, disable and remove after
> > running engine-cleanup?
>
> See above.
>
> See also [1], which is for a hosted-engine host, not exactly your case
> but similar. You are welcome to comment there, and/or open another RFE
> bz for general hosts (not hosted-engine ones).
>
> I might be wrong, though - perhaps there is something to undo ifcfg*
> changes that I am unaware of. Dan?
>

There is automatic restoration for rollback scenarios, but these 

Re: [ovirt-users] Setting DNS servers problem on ovirt

[Yedidyah Bar David]

On Tue, Nov 1, 2016 at 1:38 AM, Thing  wrote:
> Hi,
>
> I have installed IPA across 3 nodes.  In order to point the ovirt server at
> the new IPA/DNS servers and to clean up I ran engine-cleanup aiming to delte
> the ovirt setup.   However it seems even though I ran this something,
> "vdsm?" is still running and controlling the networking.

engine-cleanup only cleans up the engine. It does nothing to the hosts.
I am not aware of a similar "vdsm-cleanup" tool.
In principle, you could have moved your hosts to maintenance and removed them
from the engine. No idea what this would tell vdsm to do wrt to your question.
It definitely would not undo ifcfg-* changes.

>
> So down under /etc/sysconfig/network-scripts I see,
>
> =
> /etc/sysconfig/network-scripts
> [root@ovirt1 network-scripts]# ls -l
> total 256
> -rw-rw-r--. 1 root root   130 Nov  1 10:32 ifcfg-enp0s25
> -rw-r--r--. 1 root root   254 Sep 16  2015 ifcfg-lo
> -rw-rw-r--. 1 root root   252 Nov  1 10:32 ifcfg-ovirtmgmt
> 8><-
> ==
>
> So my first Q is why when I run engine-cleanup isnt the networking cleaned
> up?  should I file this as a bugzilla?

See above, it's not in the scope for engine-cleanup.

>
> After that I can see that ifcfg-ovirtmgmt is still controlling DNS,
>
> ==
> 8><
> [root@ovirt1 network-scripts]# tail ifcfg-ovirtmgmt
> ONBOOT=yes
> IPADDR=192.168.1.34
> NETMASK=255.255.255.0
> GATEWAY=192.168.1.1
> BOOTPROTO=none
> MTU=1500
> DEFROUTE=yes
> NM_CONTROLLED=no
> IPV6INIT=no
> DNS1=192.168.1.240
> [root@ovirt1 network-scripts]#
> ===
>
> So I tried to set,
>
> DNS1=192.168.1.31
> DNS2=192.168.1.32
> DNS3=192.168.1.33
>
> rebooted and, no I see,
>
> DNS1=192.168.1.240 again
>
> So I also see that the vdsm service is still running,
>
> ==
> [root@ovirt1 network-scripts]# systemctl status vdsm-network.service
> ● vdsm-network.service - Virtual Desktop Server Manager network restoration
>Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service; enabled;
> vendor preset: enabled)
>Active: active (exited) since Tue 2016-11-01 10:32:51 NZDT; 2h 0min ago
>   Process: 2873 ExecStart=/usr/bin/vdsm-tool restore-nets (code=exited,
> status=0/SUCCESS)
>   Process: 2848 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append
> --logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence
> (code=exited, status=0/SUCCESS)
>  Main PID: 2873 (code=exited, status=0/SUCCESS)
>CGroup: /system.slice/vdsm-network.service
>
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5 client
> step 2
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> parse_server_challenge()
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> ask_user_info()
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5 client
> step 2
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> ask_user_info()
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5
> make_client_response()
> Nov 01 10:32:45 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5 client
> step 3
> Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5 client
> mech dispose
> Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz python[2887]: DIGEST-MD5 common
> mech dispose
> Nov 01 10:32:51 ovirt1.ods.graywitch.co.nz systemd[1]: Started Virtual
> Desktop Server Manager network restoration.
> [root@ovirt1 network-scripts]#
> ===
>
> why after cleaning up is this still active?
>
> Next, I have grep'd under /etc/ and cannot find where its getting its
> obsolete network DNS info info from.

I think it's somewhere under /var, adding Dan.

>
> So I need to know where this info is stored? so I can edit is via the CLI?
> database?
>
> There is no web ui running as engine-cleanup has removed that so I cant work
> via the web ui.
>
> Is there anything else I need to manually stop, disable and remove after
> running engine-cleanup?

See above.

See also [1], which is for a hosted-engine host, not exactly your case
but similar. You are welcome to comment there, and/or open another RFE
bz for general hosts (not hosted-engine ones).

I might be wrong, though - perhaps there is something to undo ifcfg*
changes that I am unaware of. Dan?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1001181

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users