Re: [ovirt-users] Engine migration and host import

[Ben Bradley]

On 25/09/17 13:56, Simone Tiraboschi wrote:



On Sun, Sep 24, 2017 at 10:59 PM, Ben Bradley > wrote:


On 23/09/17 00:27, Ben Bradley wrote:

On 20/09/17 15:41, Simone Tiraboschi wrote:


On Wed, Sep 20, 2017 at 12:30 AM, Ben Bradley

>> wrote:

 Hi All

 I've been running a single-host ovirt setup for several
months,
 having previously used a basic QEMU/KVM for a few years
in lab
 environments.

 I currently have the ovirt engine running at the
bare-metal level,
 with the box also acting as the single host. I am also
running this
 with local storage.

 I now have an extra host I can use and would like to
migrate to a
 hosted engine. The following documentation appears to
be perfect and
 pretty clear about the steps involved:

https://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/




>

 and

https://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment




>


 However I'd like to try and get a bit more of an
understanding of
 the process that happens behind the scenes during the
cut-over from
 one engine to a new/hosted engine.

 As an experiment I attempted the following:
 - created a new VM within my current environment
(bare-metal engine)
 - creating an engine-backup
 - stopped the bare-metal engine
 - restored the backup into the new VM
 - ran engine-setup within the new VM
 The new engine started up ok and I was able to connect
and login to
 the web UI. However my host was "unresponsive" and I
was unable to
 manage it in any way from the VM. I shut the VM down
and started the
 bare-metal ovirt-engine again on the host and
everything worked as
 before. I didn't try very hard to make it work however.

 The magic missing from the basic process I tried is the
 synchronising and importing of the existing host, which
is what the
 hosted-engine utility does.


No magic up to now: the host are simply in the DB you restored.
If the VM has network connectivity and the same host-name of
the old machine you shouldn't see any issue.
If you changed the host-name moving to the VM, you should
simply run engine-rename after the restore.


Thank you for the reply.
I tried this again this evening - again it failed.

The host is present within the new engine but I am unable to
manage it.
Host is marked as down but Activate is greyed out. I can get get
into the "Edit" screen for the host and on right-click I get the
following options:
- Maintenance
- Confirm Host has been Rebooted
- SSH Management: Restart and Stop both available
The VMs are still running and accessible but are not listed as
running under the web interface. This time however I did lose
access to the ovirtmgmt bridge and the web interface, running
VMs and host SSH session were unavailable until I rebooted.
Luckily I left ovirt-engine service enabled to restart on boot
so everything came back up.

The engine URL is a CNAME so I just re-pointed to the hostname
of the VM just before running engine-setup after the restore.

This time though I have kept the new engine VM so I can power it
up again and try and debug.

I am going to try a few times over the weekend and I have setup
serial console access so I can do a bit more debugging.

[ovirt-users] ovirt 4.0 repos

[Edward Clay]

Hello, I've recently ran into a couple of problems.  One that I'm
noticing right now is that when I do a yum check-update I'm getting a
404 .

yum clean allyum check-updateLoaded plugins: fastestmirror,
versionlockbase
  | 3.6
kB  00:00:00 http://mirror.centos.org/centos/7/virt/x86_64/ovirt-4.
0/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not FoundTrying
other mirror.To address this issue please refer to the below knowledge
base article 
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please create a bug
on https://bugs.centos.org/


 One of the configured repositories failed (CentOS-7 - oVirt 4.0), and
yum doesn't have enough cached data to continue. At this point the
only safe thing yum can do is fail. There are a few ways to work "fix"
this:
 1. Contact the upstream for the repository and get them to fix the
problem.
 2. Reconfigure the baseurl/etc. for the repository, to point to a
workingupstream. This is most often useful if you are using a
newerdistribution release than is supported by the repository
(and thepackages for the previous distribution release still
work).
 3. Run the command with the repository temporarily
disabledyum --disablerepo=centos-ovirt40-release ...
 4. Disable the repository permanently, so yum won't use it by
default. Yumwill then just ignore the repository until you
permanently enable itagain or use --enablerepo for temporary
usage:
yum-config-manager --disable centos-ovirt40-
releaseorsubscription-manager repos --
disable=centos-ovirt40-release
 5. Configure the failing repository to be skipped, if it is
unavailable.Note that yum will try to contact the repo. when it
runs most commands,so will have to try and fail each time (and
thus. yum will be be muchslower). If it is a very temporary
problem though, this is often a nicecompromise:
yum-config-manager --save --setopt=centos-ovirt40-
release.skip_if_unavailable=true
failure: repodata/repomd.xml from centos-ovirt40-release: [Errno 256]
No more mirrors to try.http://mirror.centos.org/centos/7/virt/x86_64/ov
irt-4.0/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found I
have the following two files in /etc/yum.repo.d that I believe are used
to point me at ovirt repos.
-rw-r--r--. 1 root root 1672 Feb  7  2017 ovirt-4.0-
dependencies.repo[ovirt-4.0-epel]name=Extra Packages for Enterprise
Linux 7 - $basearch#baseurl=http://download.fedoraproject.org/pub/epel/
7/$basearchmirrorlist=https://mirrors.fedoraproject.org/metalink?repo=e
pel-7=$basearchfailovermethod=priorityenabled=1includepkgs=epel-
release,python-uinput,puppet,python-lockfile,python-cpopen,python-
ordereddict,python-pthreading,python-inotify,python-
argparse,novnc,python-ply,python-kitchen,python-daemon,python-
websockify,livecd-tools,spice-html5,mom,python-IPy,python-
ioprocess,ioprocess,safelease,python-paramiko,python2-paramiko,python2-
crypto,libtomcrypt,libtommath,python-cheetah,python-ecdsa,python2-
ecdsa,python-markdown,rubygem-rgen,ovirt-guest-agent*,userspace-
rcu,protobuf-
java,objenesis,python34*gpgcheck=1gpgkey=https://dl.fedoraproject.org/p
ub/epel/RPM-GPG-KEY-EPEL-7
[ovirt-4.0-centos-gluster37]name=CentOS-7 - Gluster 3.7baseurl=http://m
irror.centos.org/centos/7/storage/$basearch/gluster-
3.7/gpgcheck=1enabled=1gpgkey=https://raw.githubusercontent.com/CentOS-
Storage-SIG/centos-release-storage-common/master/RPM-GPG-KEY-CentOS-
SIG-Storage
[ovirt-4.0-patternfly1-noarch-epel]name=Copr repo for patternfly1 owned
by patternflybaseurl=http://copr-be.cloud.fedoraproject.org/results/pat
ternfly/patternfly1/epel-7-
$basearch/enabled=1skip_if_unavailable=1gpgcheck=0
[virtio-win-stable]name=virtio-win builds roughly matching what was
shipped in latest RHELbaseurl=http://fedorapeople.org/groups/virt/virti
o-win/repo/stableenabled=1skip_if_unavailable=1gpgcheck=0
[centos-ovirt40-release]name=CentOS-7 - oVirt 4.0baseurl=http://mirror.
centos.org/centos/7/virt/$basearch/ovirt-4.0/gpgcheck=0enabled=1
-rw-r--r--. 1 root root  289 Feb  7  2017 ovirt-4.0.repo[ovirt-
4.0]name=Latest oVirt 4.0 Release#baseurl=http://resources.ovirt.org/pu
b/ovirt-
4.0/rpm/el$releasever/mirrorlist=http://resources.ovirt.org/pub/yum-
repo/mirrorlist-ovirt-4.0-
el$releaseverenabled=1skip_if_unavailable=1gpgcheck=1gpgkey=file:///etc
/pki/rpm-gpg/RPM-GPG-ovirt-4.0
Should the 4.0 version/repos still be available and if so what's wrong
with my curent config?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ovirt-devel] vdsm vds.dispatcher [Solved]

[Gary Pedretty]

The latest release 4.1 solved this issue.

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 Alaska's Interior  /  \/  /\  \ \/\   "Love your neighbor as
White white everywhere, must be winter  yourself” Matt 22:39






> On Aug 30, 2017, at 11:34 AM, Gary Pedretty  wrote:
> 
> The bug I assumed this was related to is.
> 
> Bug 1417708 - ovirt-ha-agent should reuse json-rpc connections  
> 
> 
> This is a glusterized 4 host self hosted engine setup.  All storage domains 
> are glusterfs replica 3 volumes on 3 of the 4 hosts that are part of the 
> cluster.
> 
> Centos 3.10.0-514.26.2.el7.x86_64
> 
> vdsm-4.18.21-1.el7.centos.x86_64
> libvirt-2.0.0-10.el7_3.9.x86_64
> glusterfs-3.7.20-1.el7.x86_64
> qemu-kvm-tools-ev-2.6.0-28.el7_3.3.1.x86_64
> 
> Host and engine are all updated to the latest versions
> 
> Here are sample of messages log, vdsm,log, supervdsm.log and mom.log
> 
> messages
> 
> Aug 28 01:20:11 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:16 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:16 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:19 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:22 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:24 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:37 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:41 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:41 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:44 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:47 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> Aug 28 01:20:49 fai-kvm-1 journal: vdsm vds.dispatcher ERROR SSL error during 
> reading data: unexpected eof
> 
> vdsm.log
> 
> Thread-316519::DEBUG::2017-08-28 
> 01:21:13,242::bindingxmlrpc::319::vds::(wrapper) client [::1]
> Thread-316519::DEBUG::2017-08-28 
> 01:21:13,242::task::597::Storage.TaskManager.Task::(_updateState) 
> Task=`7c850537-b9e2-4e4b-b346-5fc8ba40f2d1`::moving from state
> init -> state preparing
> Thread-316519::INFO::2017-08-28 
> 01:21:13,242::logUtils::49::dispatcher::(wrapper) Run and protect: 
> repoStats(options=None)
> Thread-316519::INFO::2017-08-28 
> 01:21:13,243::logUtils::52::dispatcher::(wrapper) Run and protect: repoStats, 
> Return
> response: {u'5e39db25-561f-490a-81b6-46a7225f02b6': {'code': 0, 'actual': 
> True, 'version': 0, 'acquired': True, 'delay': '0.000833501', 'lastCheck': 
> '1.1', 'valid': True}, u'403df7fb-6cff-46e1-8e04-41213fbc0e6e': {'code': 0, 
> 'actual': True, 'version': 3, 'acquired': False, 'delay': '0.000893509', 
> 'lastCheck': '1.1', 'valid': True}, u'cf2f4c75-966b-4f69-90a2-d8e7d21fc052': 
> {'code': 0, 'actual': True, 'version':
> 3, 'acquired': True, 'delay': '0.000776587', 'lastCheck': '1.0', 'valid': 
> True}, u'6654cb0c-3e57-42ca-b996-3660a3d32a43': {'code': 0, 'actual': True, 
> 'version': 3, 'acquired': True, 'delay': '0.000513211', 'lastCheck': '1.1', 
> 'valid': True}, u'2bf8f623-1d82-444e-ae16-d32e5fe4dc9e': {'code': 0, 
> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000493711', 
> 'lastCheck': '1.3', 'valid':
> True}, u'feaebec7-aae3-45b5-9684-1feedede7bec': {'code': 0, 'actual': True, 
> 'version': 0, 'acquired': True, 'delay':
> '0.000512272', 'lastCheck': '1.1', 'valid': True}}
> Thread-316519::DEBUG::2017-08-28 
> 01:21:13,243::task::1193::Storage.TaskManager.Task::(prepare) 
> Task=`7c850537-b9e2-4e4b-b346-5fc8ba40f2d1`::finished: 
> {u'5e39db25-561f-490a-81b6-46a7225f02b6': {'code':
> 0, 'actual': True, 'version': 0,
> 'acquired': True, 'delay': '0.000833501', 'lastCheck': '1.1', 'valid': True}, 
> u'403df7fb-6cff-46e1-8e04-41213fbc0e6e': {'code': 0, 'actual': True, 
> 'version': 3, 'acquired': False, 'delay': '0.000893509', 'lastCheck': '1.1', 
> 'valid': True}, u'cf2f4c75-966b-4f69-90a2-d8e7d21fc052': {'code': 0, 
> 'actual': True, 'version': 3, 'acquired': True, 'delay': '0.000776587', 
> 'lastCheck': '1.0', 

[ovirt-users] Preventing VM's from starting on specific Hosts

[Mark Steele]

Hello,

We've added two new hosts to our Ovirt 3.5.0.1 installation and want to
restrict which VM's can start on it - specifically we do not any VM's to be
able to auto select these two hosts.

How do I prevent VM's from starting on these two HV's without specifically
tying every VM to a host?

Best regards,

***
*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] Addition of hosts fail at network setup

[Paul-Erik Törrönen]

Hello,

I'm attempting to add another host to the cluster, and I'm getting the 
following error when I add the ovirtmgmt network to the physical network 
device:


Error while executing action HostSetupNetworks: Unexpected exception

In the host vdsm.log I have the following:

2017-09-25 19:58:35,060+0300 ERROR (jsonrpc/4) [jsonrpc.JsonRpcServer] 
Internal server error (__init__:577)

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 
572, in _handle_request

res = method(**params)
  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 202, 
in _dynamicMethod

result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 1575, in setupNetworks
supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in 
__call__

return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in 


**kwargs)
  File "", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in 
_callmethod

raise convert_to_error(kind, result)
IOError: [Errno 2] No such file or directory: 
u'/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt'
2017-09-25 19:58:35,061+0300 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] 
RPC call Host.setupNetworks failed (error -32603) in 0.18 seconds 
(__init__:539)


I thought the ifcfg-ovirtmgmt-file was supposed to be created by the 
ovirt setup?


I'm running the latest ovirt 4.1.6 on CentOS7.4 x86_64 
(ovirt-release41-4.1.6-1.el7.centos.noarch).


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

Re: [ovirt-users] Clone of VM and copy of disks doubts

[Gianluca Cecchi]

On Mon, Sep 25, 2017 at 5:23 PM, Gianluca Cecchi 
wrote:

>
>
> So I create a snapshot of VM1 and then "Clone". Inside the "Resource
> Allocation" section, the drop-down for the 3 disks seems not enabled, in
> the sense that for every disk it contains only the name of the origin SD,
> so for 2 disks it contains SDA and no other SD to be chosen, for 1 disk it
> contains SDB and no other SD to be chosen.
> See here:
> https://drive.google.com/file/d/0BwoPbcrMv8mvdFd0RFMzRXhmRzQ/
> view?usp=sharing
> Can anyone replicate this in 4.1.5 to see if it is a problem of mine?
>
>
This one actually is not a problem, because I was trying to expand the
"Disk profile" column... ;-)
Selecting the "Target" column it works..

The other 2 questions remain in place.
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Clone of VM and copy of disks doubts

[Gianluca Cecchi]

Hello,
I have a VM VM1 that I would like to clone.
It has 3 disks: 2 of them on storage domain SDA, 1 of them (size 80Gb) on a
second storage domain SDB

I want the new VM to have all the 3 disks on SDA, because SDB has not
enough space to accomodate the cloned disk

I power off VM1, select it and then "Clone VM". It seems I have no options
at all and that I can only specify the name of the new VM, while oVirt
would copy the VM with exactlly the same disks and so I receive error

Error while executing action:

VM2:

   - Cannot add VM. Low disk space on Storage Domain SDB.

Is this expected? In case it seems not very flexible.

So I create a snapshot of VM1 and then "Clone". Inside the "Resource
Allocation" section, the drop-down for the 3 disks seems not enabled, in
the sense that for every disk it contains only the name of the origin SD,
so for 2 disks it contains SDA and no other SD to be chosen, for 1 disk it
contains SDB and no other SD to be chosen.
See here:
https://drive.google.com/file/d/0BwoPbcrMv8mvdFd0RFMzRXhmRzQ/view?usp=sharing
Can anyone replicate this in 4.1.5 to see if it is a problem of mine?

So as a last resource I decide to copy disk by disk.
Apparently my VM1 disk in SDB is preallocated: at least this is what I see
if I select VM1, Snapshots, select the "Current" line (it is the only oe as
therer are no snapshots), "DIsks" in right subpane
See here for screenshot:
https://drive.google.com/file/d/0BwoPbcrMv8mvclV5bDdsdE9Ubmc/view?usp=sharing

Any more comfortable and correct way from web admin gui to see disk type?

When I copy the disk it seems it tries to create a thin provisioned disk
and it takes about 4 hours to copy 80Gb of disks from SSD to SAS SD with
very few I/O activity on hypervisor in the mean time (I have only one node
in this test)
when I would expect around 40minutes with a throughput of at elast 40MB/s
with a sort of dd as the cemu-img command should be... instead the command
I see from command line is kind of
 /usr/bin/qemu-img convert -p -t none -T none -f qcow2
/rhev/data-center/59b7af54-0155-01c2-0248-0195/70411599-c19f-4a6a-80b5-abdeffc1616e/images/3d357b96-57e1-47bd-be65-558252a591d3/77ba5e2b-dfbe-4801-b5ec-dc9ffae2c481
-O qcow2 -o compat=1.1
/rhev/data-center/mnt/blockSD/fad05d79-254d-4f40-8201-360757128ede/images/73292653-f5d9-49ae-8132-f17d288bf822/deb4b841-95cd-4523-9523-f2ffdbb9b4a9


Also, if get this VM and create a snapshot of it I see this:
- starting point all the 3 disks seem preallocated (same method as above)
- after creating a snapshot, if I select the "Current" line the 3 disks are
all thin-provision, if I select the line of the taken snapshot instead the
disks are all preallocated.

Any comments or suggestions about the points above?

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

Re: [ovirt-users] Snapshot removal vs selinux enforced

[Lionel Caignec]

I reply myself if it can help somemone.
I found a solution with audit2allow/audit2why creating a policy containing this 
: 
type systemd_machined_t;
type svirt_t;
type fixed_disk_device_t;
class blk_file write;
class dir search;
}

It seems to work, and i can keep my host in selinux enforced.

- Mail original -
De: "Lionel Caignec" 
À: "users" 
Envoyé: Lundi 25 Septembre 2017 15:37:16
Objet: [ovirt-users] Snapshot removal vs selinux enforced

Hi,

i have a problem with selinux enforced.
When i tried to live remove a snapshot the operation failed . After some 
headache i found the problem source : selinux.
When i "setenfore 0" the removal task work, when i "setenforce 1" removal task 
failed.

log from audit.log:
  vc: denied {write} for pid = 28360 tmptext = system_u: object_r : 
fixed_disk_device_t: s0 tclass = blk_file

I'm with RHEL 7.4 and ovirt 4.1, is it some specific configuration to do?.

Thanks for help.
___
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

[ovirt-users] Snapshot removal vs selinux enforced

[Lionel Caignec]

Hi,

i have a problem with selinux enforced.
When i tried to live remove a snapshot the operation failed . After some 
headache i found the problem source : selinux.
When i "setenfore 0" the removal task work, when i "setenforce 1" removal task 
failed.

log from audit.log:
  vc: denied {write} for pid = 28360 tmptext = system_u: object_r : 
fixed_disk_device_t: s0 tclass = blk_file

I'm with RHEL 7.4 and ovirt 4.1, is it some specific configuration to do?.

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

Re: [ovirt-users] Engine migration and host import

[Simone Tiraboschi]

On Sun, Sep 24, 2017 at 10:59 PM, Ben Bradley  wrote:

> On 23/09/17 00:27, Ben Bradley wrote:
>
>> On 20/09/17 15:41, Simone Tiraboschi wrote:
>>
>>>
>>> On Wed, Sep 20, 2017 at 12:30 AM, Ben Bradley >> > wrote:
>>>
>>> Hi All
>>>
>>> I've been running a single-host ovirt setup for several months,
>>> having previously used a basic QEMU/KVM for a few years in lab
>>> environments.
>>>
>>> I currently have the ovirt engine running at the bare-metal level,
>>> with the box also acting as the single host. I am also running this
>>> with local storage.
>>>
>>> I now have an extra host I can use and would like to migrate to a
>>> hosted engine. The following documentation appears to be perfect and
>>> pretty clear about the steps involved:
>>> https://www.ovirt.org/develop/developer-guide/engine/migrate
>>> -to-hosted-engine/
>>> >> migrate-to-hosted-engine/>
>>> and
>>> https://www.ovirt.org/documentation/self-hosted/chap-
>>> Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment
>>> >> Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment>
>>>
>>> However I'd like to try and get a bit more of an understanding of
>>> the process that happens behind the scenes during the cut-over from
>>> one engine to a new/hosted engine.
>>>
>>> As an experiment I attempted the following:
>>> - created a new VM within my current environment (bare-metal engine)
>>> - creating an engine-backup
>>> - stopped the bare-metal engine
>>> - restored the backup into the new VM
>>> - ran engine-setup within the new VM
>>> The new engine started up ok and I was able to connect and login to
>>> the web UI. However my host was "unresponsive" and I was unable to
>>> manage it in any way from the VM. I shut the VM down and started the
>>> bare-metal ovirt-engine again on the host and everything worked as
>>> before. I didn't try very hard to make it work however.
>>>
>>> The magic missing from the basic process I tried is the
>>> synchronising and importing of the existing host, which is what the
>>> hosted-engine utility does.
>>>
>>>
>>> No magic up to now: the host are simply in the DB you restored.
>>> If the VM has network connectivity and the same host-name of the old
>>> machine you shouldn't see any issue.
>>> If you changed the host-name moving to the VM, you should simply run
>>> engine-rename after the restore.
>>>
>>
>> Thank you for the reply.
>> I tried this again this evening - again it failed.
>>
>> The host is present within the new engine but I am unable to manage it.
>> Host is marked as down but Activate is greyed out. I can get get into the
>> "Edit" screen for the host and on right-click I get the following options:
>> - Maintenance
>> - Confirm Host has been Rebooted
>> - SSH Management: Restart and Stop both available
>> The VMs are still running and accessible but are not listed as running
>> under the web interface. This time however I did lose access to the
>> ovirtmgmt bridge and the web interface, running VMs and host SSH session
>> were unavailable until I rebooted.
>> Luckily I left ovirt-engine service enabled to restart on boot so
>> everything came back up.
>>
>> The engine URL is a CNAME so I just re-pointed to the hostname of the VM
>> just before running engine-setup after the restore.
>>
>> This time though I have kept the new engine VM so I can power it up again
>> and try and debug.
>>
>> I am going to try a few times over the weekend and I have setup serial
>> console access so I can do a bit more debugging.
>>
>> What ovirt logs could I check on the host to see if the new engine VM is
>> able to connect and sync to the host properly?
>>
>> Thanks, Ben
>>
>
> So I tried again to migrate my bare-metal host to a hosted VM but no luck.
> The host remained in unresponsive state in the engine web UI and I was
> unable to manage the host in anyway. Although all VMs continued to run.
>
> I did capture some logs though.
> From the new engine VM... engine.log
> https://p.bsd-unix.net/view/raw/666839d1
>
> From the host...
> mom.log  https://p.bsd-unix.net/view/raw/ac9379f0
> supervdsm.log  https://p.bsd-unix.net/view/raw/f9018dec
> vdsm.log  https://p.bsd-unix.net/view/raw/bcdcdb13
>
>
Sorry but no one of that links is working right now.


> The engine VM is complaining about being unable to connect to the host,
> though I can see from tcpdump communication is fine. I believe this is
> backed up by the pings seen in mom.log
>
> Though I can see the following in vdsm.log... [vds] recovery: waiting for
> storage pool to go up (clientIF:569)
> So I wonder if this is blocking the engine bringing the host up.
>
> The host is running local storage, which I believe is a pretty recent
> 

Re: [ovirt-users] oVirt's VM backup

[Nathanaël Blanchet]

Le 25/09/2017 à 11:27, Yaniv Kaul a écrit :



On Mon, Sep 25, 2017 at 11:02 AM, Nathanaël Blanchet > wrote:




Le 24/09/2017 à 11:11, Yaniv Kaul a écrit :



On Sep 21, 2017 7:09 PM, "Nathanaël Blanchet" > wrote:

Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will
be removed in the next version 4.2, so I'm looking at sdk4
project.


So it has recently changed! There was a dedicated ticket in
bugzilla about this and many warnings intended to users, but
nothing to tell sdk3 removal will be postponed...


We decided to just let it stay, instead of forcing everyone to convert.
Nice to hear such a new, community is the key, and ovirt devs seem to 
remember!
Note that none of the new features since 4.0 are supported in v3 API, 
it has far fewer examples, documentation or features for the SDKs 
themselves (see[1] for example).
So does that mean v3 API will be kept far in the future? What about 
derivated tools like ovirt-shell?


From personal experience, I believe it is also easier to develop with 
the new SDKs.

Y.

[1] https://ovirt.org/blog/2017/05/higher-performance-for-python-sdk/




SDKv3 will not be removed in 4.2.

You may want to adapt it?


Note that you can gradually move to v4. You can mix v4 API with
v3 API and convert function by function.
Y.


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup


Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet
>:

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a
écrit :

Hello everyone, i created a python tool to backup and
restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image
of the snapshot vm in the backup vm. It seems to be
compliant with the official backup API, except on
the step 2.

 1. /Take a snapshot of the virtual machine to be backed
up - (existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the
time of the snapshot (the disk configuration can be
backed up as well if needed) - (added capability to
oVirt as part of the Backup API)/

I can't see any vm configuration anywhere but only the
qcow2 disk itself

 1. /Attach the disk snapshots that were created in (1)
to the virtual appliance for data backup - (added
capability to oVirt as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4)
from the virtual appliance - (added capability to
oVirt as part of the Backup API)/

An other case is when the vm to backup has more than one
disk. After I tested it, I found that only one qcow2
disk is saved on the backup vm. This is really a matter
when the original vm has many disks part of lvm, it
makes the vm restoration unusable.

  * About vm restoration, it seems that you are using
the upload_disk api, so the disk is uploaded to the
pre-defined storage domain, so it is not a real vm
restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




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



-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr 

Re: [ovirt-users] oVirt's VM backup

[Yaniv Kaul]

On Mon, Sep 25, 2017 at 11:02 AM, Nathanaël Blanchet 
wrote:

>
>
> Le 24/09/2017 à 11:11, Yaniv Kaul a écrit :
>
>
>
> On Sep 21, 2017 7:09 PM, "Nathanaël Blanchet"  wrote:
>
> Hi Bernardo,
>
> Thanks, I knew this tool, but it is based on sdk3 which will be removed in
> the next version 4.2, so I'm looking at sdk4 project.
>
> So it has recently changed! There was a dedicated ticket in bugzilla about
> this and many warnings intended to users, but nothing to tell sdk3 removal
> will be postponed...
>

We decided to just let it stay, instead of forcing everyone to convert.
Note that none of the new features since 4.0 are supported in v3 API, it
has far fewer examples, documentation or features for the SDKs themselves
(see[1] for example).

>From personal experience, I believe it is also easier to develop with the
new SDKs.
Y.

[1] https://ovirt.org/blog/2017/05/higher-performance-for-python-sdk/


>
> SDKv3 will not be removed in 4.2.
>
> You may want to adapt it?
>
>
> Note that you can gradually move to v4. You can mix v4 API with v3 API and
> convert function by function.
> Y.
>
>
> Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>
> Hi Nathanael,
>
> You may want to take a look at this too:
>
> https://github.com/bjuanico/oVirtBackup
>
> Regards,
>
> Bernardo
>
> PGP Key 
> Skype: mattraken
>
> 2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :
>
>> Hello Victor,
>>
>> I have some questions about your script
>>
>> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>>
>> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>>
>> Also i created a little "how to" on my blog:
>> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>
>>
>>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>>vm in the backup vm. It seems to be compliant with the official backup 
>> API,
>>except on the step 2.
>>
>>
>>1. *Take a snapshot of the virtual machine to be backed up -
>>(existing oVirt REST API operation)*
>>2. *Back up the virtual machine configuration at the time of the
>>snapshot (the disk configuration can be backed up as well if needed) -
>>(added capability to oVirt as part of the Backup API)*
>>
>> I can't see any vm configuration anywhere but only the qcow2 disk itself
>>
>>1. *Attach the disk snapshots that were created in (1) to the virtual
>>appliance for data backup - (added capability to oVirt as part of the
>>Backup API)*
>>2.
>> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>>appliance - (added capability to oVirt as part of the Backup API)*
>>
>> An other case is when the vm to backup has more than one disk. After I
>> tested it, I found that only one qcow2 disk is saved on the backup vm. This
>> is really a matter when the original vm has many disks part of lvm, it
>> makes the vm restoration unusable.
>>
>>- About vm restoration, it seems that you are using the upload_disk
>>api, so the disk is uploaded to the pre-defined storage domain, so it is
>>not a real vm restoration.
>>
>> Do you plan to backup and restore a full VM (disks + vm definition) in a
>> next release?
>>
>>
>> I hope it help someone else
>>
>> Regards
>>
>> Victor Acosta
>>
>>
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>> 
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> 
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> 
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Issues getting agent working on Ubuntu 17.04

[Matthew Pease]

Try https://packages.debian.org/sid/python/python-ethtool
This fixed it for me, looks like a bug that's been fixed in debian but not
yet ported over to ubuntu

Ubuntu was 0.12-1 where as debian has a newer 0.12-1.1
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Failed gdeploy

[Kasturi Narra]

Hi Sean,

 This error is expected and there is a bug to change this script so
that it can  properly disable multipath devices. To continue you can simply
add 'ignore_script_errors=yes'  under script3 which continues with this
failure. Please note that this script is used to disable multipath devices
and proceeding with this script simply means that you will have multipath
enabled for all your devices.

[script3]

file=/usr/share/gdeploy/scripts/disable-multipath.sh
ignore_script_errors=yes

Thanks
kasturi

On Fri, Sep 22, 2017 at 9:41 PM, Sean McMurray  wrote:

> After reading https://bugzilla.redhat.com/show_bug.cgi?id=1469469 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1491548#c2 I changed
> gdeployConfig.conf so that [script3] has file=/usr/share/gdeploy/script
> s/disable-multipath.sh
>
> That gives me a different failture:
>
> TASK [Run a shell script] **
> 
> **
> task path: /tmp/tmp4kfKbY/run-script.yml:7
> failed: [192.168.1.3] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.3 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:47 | DM
> multipath kernel driver not loaded\r\nSep 22 08:58:47 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 08:58:47 | DM multipath
> kernel driver not loaded", "Sep 22 08:58:47 | DM multipath kernel driver
> not loaded"]}
> failed: [192.168.1.2] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.2 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 15:57:47 | DM
> multipath kernel driver not loaded\r\nSep 22 15:57:47 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 15:57:47 | DM multipath
> kernel driver not loaded", "Sep 22 15:57:47 | DM multipath kernel driver
> not loaded"]}
> failed: [192.168.1.1] (item=/usr/share/gdeploy/scripts/disable-multipath.sh)
> => {"changed": true, "failed": true, "failed_when_result": true, "item":
> "/usr/share/gdeploy/scripts/disable-multipath.sh", "rc": 1, "stderr":
> "Shared connection to 192.168.1.1 closed.\r\n", "stdout": "iscsiadm: No
> active sessions.\r\nThis script will prevent listing iscsi devices when
> multipath CLI is called\r\nwithout parameters, and so no LUNs will be
> discovered by applications like VDSM\r\n(oVirt, RHV) which shell-out to
> call `/usr/sbin/multipath` after target login\r\nSep 22 08:58:50 | DM
> multipath kernel driver not loaded\r\nSep 22 08:58:50 | DM multipath kernel
> driver not loaded\r\n", "stdout_lines": ["iscsiadm: No active sessions.",
> "This script will prevent listing iscsi devices when multipath CLI is
> called", "without parameters, and so no LUNs will be discovered by
> applications like VDSM", "(oVirt, RHV) which shell-out to call
> `/usr/sbin/multipath` after target login", "Sep 22 08:58:50 | DM multipath
> kernel driver not loaded", "Sep 22 08:58:50 | DM multipath kernel driver
> not loaded"]}
> to retry, use: --limit @/tmp/tmp4kfKbY/run-script.retry
>
> PLAY RECAP 
> ***
> 192.168.1.1: ok=0changed=0unreachable=0 failed=1
> 192.168.1.2: ok=0changed=0unreachable=0 failed=1
> 192.168.1.3: ok=0changed=0unreachable=0 failed=1
>
>
> On 09/22/2017 09:05 AM, Sean McMurray wrote:
>
>> My latest attempt to deploy went like this (/tmp/tmpaQJuTG/run-script.yml
>> 

Re: [ovirt-users] API Snapshot removal ending event

[Luca 'remix_tj' Lorenzetto]

On Mon, Sep 25, 2017 at 8:27 AM, Lionel Caignec  wrote:
> Hi,
>
> For snap creation i use a loop like this to know when task is finished:
>> snap = snapshots_service.add(types.Snapshot(description=description,
>persist_memorystate=False))
>> snap_service = snapshots_service.snapshot_service(snap.id)
>>while snap.snapshot_status != types.SnapshotStatus.OK:
>
>
> is it possible to do the same think for snap deletion? i did not find 
> anything in api doc.

Hi Lionel,

i wrote this function for deleting all the VM snapshots and waiting
the deletion:


def clean_snap_ovirt(vm_data):
vm, connection = vm_data
vms_service = connection.system_service().vms_service()
vm_service = vms_service.vm_service(vm.id)
snapshots_service = vm_service.snapshots_service()
snapshots = snapshots_service.list()
for snapshot in snapshots:
if snapshot.snapshot_type != types.SnapshotType.REGULAR:
continue
snapshot_service = snapshots_service.snapshot_service(snapshot.id)
snapshot_service.remove()
snapshot = snapshot_service.get()
while snapshot.snapshot_status == types.SnapshotStatus.LOCKED:
try:
snapshot = snapshot_service.get()
except:
break
print("Still removing snapshot of  {0} ".format(vm.name))
time.sleep(10)


vm_data is a tuple containing the connection to ovirt and the output
of a vm lookup by name

If you want to delete only specific snapshot, you have to filter out
by description, or id or something else.

Luca


-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Is this guide still valid?data-warehouse

[Arman Khalatyan]

Dear Ovirt documents maintainers is this document still valid?
https://www.ovirt.org/documentation/data-warehouse/Data_Warehouse_Guide/
When I go one level up it is bringing an empty page:
https://www.ovirt.org/documentation/data-warehouse/

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

Re: [ovirt-users] oVirt's VM backup

[Nathanaël Blanchet]

Le 24/09/2017 à 11:11, Yaniv Kaul a écrit :



On Sep 21, 2017 7:09 PM, "Nathanaël Blanchet" > wrote:


Hi Bernardo,

Thanks, I knew this tool, but it is based on sdk3 which will be
removed in the next version 4.2, so I'm looking at sdk4 project.

So it has recently changed! There was a dedicated ticket in bugzilla 
about this and many warnings intended to users, but nothing to tell sdk3 
removal will be postponed...


SDKv3 will not be removed in 4.2.

You may want to adapt it?


Note that you can gradually move to v4. You can mix v4 API with v3 API 
and convert function by function.

Y.


Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup


Regards,

Bernardo

PGP Key

Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet >:

Hello Victor,

I have some questions about your script


Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :

Hello everyone, i created a python tool to backup and
restore oVirt's VMs.

Also i created a little "how to" on my blog:
http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/



  * Backup step is okay, and I get a usable qcow2 image of
the snapshot vm in the backup vm. It seems to be
compliant with the official backup API, except on the step 2.

 1. /Take a snapshot of the virtual machine to be backed up -
(existing oVirt REST API operation)/
 2. /Back up the virtual machine configuration at the time of
the snapshot (the disk configuration can be backed up as
well if needed) - (added capability to oVirt as part of
the Backup API)/

I can't see any vm configuration anywhere but only the qcow2
disk itself

 1. /Attach the disk snapshots that were created in (1) to
the virtual appliance for data backup - (added capability
to oVirt as part of the Backup API)/
 2. /
/
 3. /Detach the disk snapshots that were attached in (4) from
the virtual appliance - (added capability to oVirt as
part of the Backup API)/

An other case is when the vm to backup has more than one
disk. After I tested it, I found that only one qcow2 disk is
saved on the backup vm. This is really a matter when the
original vm has many disks part of lvm, it makes the vm
restoration unusable.

  * About vm restoration, it seems that you are using the
upload_disk api, so the disk is uploaded to the
pre-defined storage domain, so it is not a real vm
restoration.

Do you plan to backup and restore a full VM (disks + vm
definition) in a next release?



I hope it help someone else

Regards

Victor Acosta




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



-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

[ovirt-users] API Snapshot removal ending event

[Lionel Caignec]

Hi,

For snap creation i use a loop like this to know when task is finished:
> snap = snapshots_service.add(types.Snapshot(description=description,
   persist_memorystate=False))
> snap_service = snapshots_service.snapshot_service(snap.id)
>while snap.snapshot_status != types.SnapshotStatus.OK:


is it possible to do the same think for snap deletion? i did not find anything 
in api doc.


Thank you
--
Lionel 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Restoring from backup

[Yedidyah Bar David]

On Sun, Sep 24, 2017 at 10:46 PM, Tyson Landon
 wrote:
> The final setup in restoring a backup has you run engine-setup. When I try
> to run engine-setup I get "[ ERROR ] Failed to execute stage 'Setup
> validation': Hosted Engine setup detected, but Global Maintenance is not
> set."

Which version? This should not happen in 4.1. If earlier, perhaps consider
upgrading? Also check recent thread in this list 'Engine
Backup/Restore Question'.

> I am in Global Maintenance mode however.

You should be in Global maintenance during backup.
During restore, the error you get is based on a test against the
db contents only, not actual processes.

> If I exit Global Maintenance
> the hosted engine reboots every few minutes and it fails liveliness checks.

Right.

> Is there a service i have to stop so that the setup wont think HA is
> running?

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