Is it possible to backup stopped vm? (ovirt 4.4)
by Łukasz Kołaciński
Hello,
While trying to backup stopped VM (with POST on /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got the response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault>
<detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</detail>
<reason>Operation Failed</reason>
</fault>
I found here: https://www.ovirt.org/develop/release-management/features/storage/increme... that it should be possible to back up a virtual machine that is not running.
"If the VM is not running, the system will create a paused, stripped-down version of the VM, with only backup disks attached, and use libvirt API to start and stop the backup."
But it doesn't seem to work.
Regards,
Łukasz Kołaciński
Junior Java Developer
e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu>
<mailto:m.helbert@storware.eu>
[STORWARE]<http://www.storware.eu/>
ul. Leszno 8/44
01-192 Warszawa
www.storware.eu <https://www.storware.eu/>
[facebook]<https://www.facebook.com/storware>
[twitter]<https://twitter.com/storware>
[linkedin]<https://www.linkedin.com/company/storware>
[Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw>
Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.
4 years, 1 month
Re: OVN Geneve tunnels not been established
by Konstantinos Betsis
I did a restart of the ovn-controller, this is the output of the
ovn-controller.log
2020-09-11T10:54:07.566Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovn-controller.log
2020-09-11T10:54:07.568Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2020-09-11T10:54:07.568Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2020-09-11T10:54:07.570Z|00004|main|INFO|OVS IDL reconnected, force
recompute.
2020-09-11T10:54:07.571Z|00005|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:07.571Z|00006|main|INFO|OVNSB IDL reconnected, force
recompute.
2020-09-11T10:54:07.685Z|00007|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:07.685Z|00008|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:08.685Z|00009|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
waiting 2 seconds before reconnect
2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
waiting 4 seconds before reconnect
2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connecting...
2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected SSL
connection close
2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
connection attempt failed (Protocol error)
2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642:
continuing to reconnect in the background but suppressing further logging
I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP
OVIRTMGMT_NETWORK_DC
This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can
redo it if you wan.
After the restart of the ovn-controller the OVIRT ENGINE still shows only
two geneve connections one with DC01-host02 and DC02-host01.
Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144"
hostname: "dc02-host01"
Encap geneve
ip: "DC02-host01_IP"
options: {csum="true"}
Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c"
hostname: "DC01-host02"
Encap geneve
ip: "DC01-host02"
options: {csum="true"}
I've re-done the vdsm-tool command and nothing changed.... again....with
the same errors as the systemctl restart ovn-controller
On Fri, Sep 11, 2020 at 1:49 PM Dominik Holler <dholler(a)redhat.com> wrote:
> Please include ovirt-users list in your reply, to share the knowledge and
> experience with the community!
>
> On Fri, Sep 11, 2020 at 12:12 PM Konstantinos Betsis <k.betsis(a)gmail.com>
> wrote:
>
>> Ok below the output per node and DC
>> DC01
>> node01
>>
>> [root@dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC01-NODE01*"
>>
>> node02
>>
>> [root@dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC01-NODE02*"
>>
>> DC02
>> node01
>>
>> [root@dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-remote
>> "ssl:*OVIRT_ENGINE_IP*:6642"
>> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-type
>> geneve
>> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open .
>> external-ids:ovn-encap-ip
>>
>> "*OVIRTMGMT_IP_DC02-NODE01*"
>>
>>
> Looks good.
>
>
>> DC01 node01 and node02 share the same VM networks and VMs deployed on top
>> of them cannot talk to VM on the other hypervisor.
>>
>
> Maybe there is a hint on ovn-controller.log on dc01-node02 ? Maybe
> restarting ovn-controller creates more helpful log messages?
>
> You can also try restart the ovn configuration on all hosts by executing
> vdsm-tool ovn-config OVIRT_ENGINE_IP LOCAL_OVIRTMGMT_IP
> on each host, this would trigger
>
> https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/se...
> internally.
>
>
>> So I would expect to see the same output for node01 to have a geneve
>> tunnel to node02 and vice versa.
>>
>>
> Me too.
>
>
>> On Fri, Sep 11, 2020 at 12:14 PM Dominik Holler <dholler(a)redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 11, 2020 at 10:53 AM Konstantinos Betsis <k.betsis(a)gmail.com>
>>> wrote:
>>>
>>>> Hi Dominik
>>>>
>>>> OVN is selected as the default network provider on the clusters and the
>>>> hosts.
>>>>
>>>>
>>> sounds good.
>>> This configuration is required already during the host is added to oVirt
>>> Engine, because OVN is configured during this step.
>>>
>>>
>>>> The "ovn-sbctl show" works on the ovirt engine and shows only two
>>>> hosts, 1 per DC.
>>>>
>>>> Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144"
>>>> hostname: "dc01-node02"
>>>> Encap geneve
>>>> ip: "X.X.X.X"
>>>> options: {csum="true"}
>>>> Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c"
>>>> hostname: "dc02-node1"
>>>> Encap geneve
>>>> ip: "A.A.A.A"
>>>> options: {csum="true"}
>>>>
>>>>
>>>> The new node is not listed (dc01-node1).
>>>>
>>>> When executed on the nodes the same command (ovn-sbctl show) times-out
>>>> on all nodes.....
>>>>
>>>> The output of the /var/log/openvswitch/ovn-conntroller.log lists on all
>>>> logs
>>>>
>>>> 2020-09-11T08:46:55.197Z|07361|stream_ssl|WARN|SSL_connect: unexpected
>>>> SSL connection close
>>>>
>>>>
>>>>
>>> Can you please compare the output of
>>>
>>> ovs-vsctl --no-wait get open . external-ids:ovn-remote
>>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-type
>>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip
>>>
>>> of the working hosts, e.g. dc01-node02, and the failing host dc01-node1?
>>> This should point us the relevant difference in the configuration.
>>>
>>> Please include ovirt-users list in your replay, to share the knowledge
>>> and experience with the community.
>>>
>>>
>>>
>>>> Thank you
>>>> Best regards
>>>> Konstantinos Betsis
>>>>
>>>>
>>>> On Fri, Sep 11, 2020 at 11:01 AM Dominik Holler <dholler(a)redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 10, 2020 at 6:26 PM Konstantinos B <k.betsis(a)gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> We have a small installation based on OVIRT 4.3.
>>>>>> 1 Cluster is based on Centos 7 and the other on OVIRT NG Node image.
>>>>>>
>>>>>> The environment was stable till an upgrade took place a couple of
>>>>>> months ago.
>>>>>> As such we had to re-install one of the Centos 7 node and start from
>>>>>> scratch.
>>>>>>
>>>>>
>>>>> To trigger the automatic configuration of the host, it is required to
>>>>> configure ovirt-provider-ovn as the default network provider for the
>>>>> cluster before adding the host to oVirt.
>>>>>
>>>>>
>>>>>> Even though the installation completed successfully and VMs are
>>>>>> created, the following are not working as expected:
>>>>>> 1. ovn geneve tunnels are not established with the other Centos 7
>>>>>> node in the cluster.
>>>>>> 2. Centos 7 node is configured by ovirt engine however no geneve
>>>>>> tunnel is established when "ovn-sbctl show" is issued on the engine.
>>>>>>
>>>>>
>>>>> Does "ovn-sbctl show" list the hosts?
>>>>>
>>>>>
>>>>>> 3. no flows are shown on the engine on port 6642 for the ovs db.
>>>>>>
>>>>>> Does anyone have any experience on how to troubleshoot OVN on ovirt?
>>>>>>
>>>>>>
>>>>> /var/log/openvswitch/ovncontroller.log on the host should contain a
>>>>> helpful hint.
>>>>>
>>>>>
>>>>>
>>>>>> Thank you
>>>>>> _______________________________________________
>>>>>> Users mailing list -- users(a)ovirt.org
>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>>>> oVirt Code of Conduct:
>>>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>>>> List Archives:
>>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LBVGLQJBWJF...
>>>>>>
>>>>>
4 years, 1 month
ovirt-engine and host certification is expired in ovirt4.0
by momokch＠yahoo.com.hk
hello everyone,
my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host???
i am using the ovirt 4.0
thank you
4 years, 1 month
Upgrade Host Compatibility Version
by jb
Hello everybody,
for some days I upgrade our environment from ovirt 4.3 to 4.4.2 and now
I stuck on upgrading the host compatibility version. It show there a
compatibility until version 4.4. The VMs have a limit until version 4.5
and the cluster shows to that I can upgrade them until 4.5.
On the cluster page is also a Upgrade guide, but this fails when I try
that one. At the moment I have only one host to upgrade (no hosted
engine)...
Thanks for helping!
Jonathan
4 years, 1 month
oVirt 4.3.10 and ansible default timeouts
by Gianluca Cecchi
Hello,
in the past when I was in 4.3.7 I used this file:
/etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf
with
ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80
to bypass the default of 30 minutes at that time.
I updated in steps to 4.3.8 (in February), 4.3.9 (in April) and 4.3.10 (in
July).
Due to an error on my side I noticed that the task for which I extended the
ansible timeout (this task I didn't execute anymore in latest months) fails
with timeout after 80 minutes indeed.
With the intent to extend again the custom timeout I went to
/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf, provided
by ovirt-engine-backend-4.3.10.4-1.el7.noarch
and actually I see this inside:
"
# Specify the ansible-playbook command execution timeout in minutes. It's
used for any task, which executes
# AnsibleExecutor class. To change the value permanentaly create a conf
file 99-ansible-playbook-timeout.conf in
# /etc/ovirt-engine/engine.conf.d/
ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=120
"
and the file seems the original provided, not tampered:
[root@ovmgr1 test_backup]# rpm -qvV
ovirt-engine-backend-4.3.10.4-1.el7.noarch | grep virt-engine.conf$
......... /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf
[root@ovmgr1 test_backup]#
So the question is: has the default intended value passed to 120 in 4.3.10
(or in any version after 4.3.7)?
Thanks,
Gianluca
4 years, 1 month
CEPH - Opinions and ROI
by Jeremey Wise
I have for many years used gluster because..well. 3 nodes.. and so long as
I can pull a drive out.. I can get my data.. and with three copies.. I have
much higher chance of getting it.
Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid
MTBF issues ) and with VDO.. and thin provisioning.. not had issue.
BUT.... gluster seems to be falling out of favor. Especially as I move
towards OCP.
So.. CEPH. I have one SSD in each of the three servers. so I have some
space to play.
I googled around.. and find no clean deployment notes and guides on CEPH +
oVirt.
Comments or ideas..
--
p <jeremey.wise(a)gmail.com>enguinpages.
4 years, 1 month
Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way
by Kushagra Agarwal
I was hoping if i can get some help with the below oVirt scenario:
*Problem Statement*:-
Is it possible to change scheduler optimization settings of cluster using
ansible or some other automation way
*Description*:- Do we have any ansible module or any other CLI based
approach which can help us to change 'scheduler optimization' settings of
cluster in oVIrt. Scheduler optimization settings of cluster can be found
under Scheduling Policy tab ( Compute -> Clusters(select the cluster) ->
click on edit and then navigate to scheduling policy
Any help in this will be highly appreciated.
Thanks,
Kushagra
4 years, 1 month
Question mark VMs
by Vrgotic, Marko
Hi oVIrt wizards,
One of my LocalStorage hypervisors dies. VMs do not need to be rescued.
As expected I see them in WebUI with question mark state (picture below):
What is the step or are steps to clean ovirt engine db from these VMs and its Storage/Hypervisor/Cluster/DC?
[Table Description automatically generated]
Kindly awaiting your reply.
-----
kind regards/met vriendelijke groeten
Marko Vrgotic
Sr. System Engineer @ System Administration
ActiveVideo
o: +31 (35) 6774131
e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com>
w: www.activevideo.com<http://www.activevideo.com>
ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.
4 years, 1 month
ovirt-engine and host certification is expired
by momokch＠yahoo.com.hk
hello everyone,
my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host???
i am using the ovirt 4.0
thank you
4 years, 1 month
Re: CEPH - Opinions and ROI
by Philip Brown
ceph through an iscsi gateway is very.. very.. slow.
----- Original Message -----
From: "Matthew Stier" <Matthew.Stier(a)fujitsu.com>
To: "Jeremey Wise" <jeremey.wise(a)gmail.com>, "users" <users(a)ovirt.org>
Sent: Wednesday, September 30, 2020 10:03:34 PM
Subject: [ovirt-users] Re: CEPH - Opinions and ROI
If you can’t go direct, how about round about, with an iSCSI gateway.
From: Jeremey Wise <jeremey.wise(a)gmail.com>
Sent: Wednesday, September 30, 2020 11:33 PM
To: users <users(a)ovirt.org>
Subject: [ovirt-users] CEPH - Opinions and ROI
I have for many years used gluster because..well. 3 nodes.. and so long as I can pull a drive out.. I can get my data.. and with three copies.. I have much higher chance of getting it.
Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid MTBF issues ) and with VDO.. and thin provisioning.. not had issue.
BUT.... gluster seems to be falling out of favor. Especially as I move towards OCP.
So.. CEPH. I have one SSD in each of the three servers. so I have some space to play.
I googled around.. and find no clean deployment notes and guides on CEPH + oVirt.
Comments or ideas..
--
[ mailto:jeremey.wise@gmail.com | p ] enguinpages.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S4V6NKC62LW...
4 years, 1 month
