- Users - oVirt List Archives

oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri 09 Apr '17

09 Apr '17

Hi oVirt developers and users, Some of you might be familiar with the oVirt repositories and all their flavors, while some of you are just familiar with the official releases. The fact is, we have plenty of them and each has its own role and a right usage. Moreover, we did a significant overhaul on all the repositories in the past months, So hopefully now it will be easier to explain which repo to use when. I'll start with reviewing each oVirt repository and give a bit of background and the logic behind it, how to consume it and the relevant usage for it. For simplicity, I'll review the repositories on the 4.1 release, but it valid for all other oVirt releases ( except 'master' which doesn't have an official or pre-release repositories ). I will also upload this information to the oVirt.org site, but since this is important, I didn't want to wait with the sending this email. *oVirt repositories* *Official repositories* *Desc:* here you can find the official signed oVirt RPMs, immediately after an official release has been done. *Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro *Update frequency:* on every oVirt release, usually happens on a monthly cadence. *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm *Who should use it? * oVirt users, developers or anyone who wants a final and official release *Pre-release repositories* *Desc:* here you can find the pre-release bits of oVirt RC builds, just before they are released. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro *Update frequency:* usually on a weekly or bi-weekly basis *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-pre.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt new version before its out, Keeping in mind this isn't a fully verified release and might still have critical bugs which are not fixed yet. Packages in this repo are verified by automation and checked by humans for basic sanity before publishing. *Nightly snapshot (verified) repositories* *Desc:* here you can find the nightly snapshot of RPMs, which passed basic sanity by our 'oVirt System Tests' framework in the oVirt CI system. *Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro *Update frequency:* Every night *Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt- release41-snapshot.rpm *Who should use it? * oVirt users, developers or anyone who wants to try out oVirt latest bits right of the build oven! We trust our system tests, which already run more than 40 various tests such as 'add host', 'create VM', 'live migration' and more! *** Important note: the snapshot repositories are verified only in master currently, we might do the same for 4.1 soon, as we see no issues with master so far ** * *The above repos should suffice to most usres and developers, but if you feel its not enough and you still need a faster verified repo, look below! * *Advanced oVirt repositories* *Builds artifacts repo* *Desc:* This is a new feature from oVirt 'standard CI' project, where each 'build-artifacts' job is actually a yum repo as well. *Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_ build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ artifact/exported-artifacts ( example ) *Update frequency:* after each commit or 'ci please build' comment *Release rpm: *N/A *Who should use it? * oVirt developers who need latest RPMs from another oVirt project and cannot or need not wait for that project`s packages to pass OST". oVirt developers running manual OST job and need to test an open Gerrit patch, using the 'ci please build' command. *Tested repositories* *Desc:* The tested repositories hold all the oVIrt packages which passed CI ( similar to snapshot repos ) and retain also version history for X versions back. *Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * If you want to have latest and greatest oVirt packages and can't wait for the nightly repo. If you are testing upgrades or need more than one version of a pacakge in your repo. *Experimental repositories * *Desc:* Internal CI repos which are a part of the 'experimental' flow which runs OST on each built package. *Path:* http://resources.ovirt.org/repos/ovirt/experimental/ 4.1/latest.tested/rpm/el7/$distro *Update frequency:* after each 'build artifacts' job is triggered by any oVirt project and if the packages passed sanity checks *Release rpm: *N/A *Who should use it? * *No one other than internal CI jobs.* These repos are constantly refreshed and RPMs are being removed from them, so they are very prone to errors, please don't use them. I hope this makes a bit of order in all the repos and how to use them. If you still have questions, please don't hesitate to contact the infra team at infra(a)ovirt.org or just reply to this thread. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

moving disk from one storage domain to another
by Bill James 09 Apr '17

09 Apr '17

We are trying to convert our qa environment from local nfs to gluster. When I move a disk with a VM that is running on same server as the storage it fails. When I move a disk with VM running on a different system it works. VM running on same system as disk: 2017-04-06 13:31:00,588 ERROR (jsonrpc/6) [virt.vm] (vmId='e598485a-dc74-43f7-8447-e00ac44dae21') Unable to start replication for vda to {u'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volumeInfo': {'domainID': u'6affd8c3-2c 51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}, 'diskType': 'file', 'format': 'cow', 'cache': 'none', u'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', u'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753', u'poolID': u'8b6303b3-79c6-4633-ae21-71b15ed00675', u'device': 'disk', 'path': u'/rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'propagateErrors': u'off', 'volumeChain': [{'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/6756eb05-6803-42a7-a3a2-10233bf2ca8d', 'volumeID': u'6756eb05-6803-42a7-a3a2-10233bf2ca8d', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/6756eb05-6803-42a7-a3a2-10233bf2ca8d.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}, {'domainID': u'6affd8c3-2c51-4cd1-8300-bfbbb14edbe9', 'volType': 'path', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'volumeID': u'30fd46c9-c738-4b13-aeca-3dc9ffc677f5', 'leasePath': u'/rhev/data-center/mnt/glusterSD/ovirt1-ks.test.j2noc.com:_gv2/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5.lease', 'imageID': u'7ae9b3f7-3507-4469-a080-d0944d0ab753'}]} (vm:3594) Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 3588, in diskReplicateStart self._startDriveReplication(drive) File "/usr/share/vdsm/virt/vm.py", line 3713, in _startDriveReplication self._dom.blockCopy(drive.name, destxml, flags=flags) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 69, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 684, in blockCopy if ret == -1: raise libvirtError ('virDomainBlockCopy() failed', dom=self) libvirtError: internal error: unable to execute QEMU command 'drive-mirror': Could not open '/rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5': Permission denied [root@ovirt1 test vdsm]# ls -l /rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5 -rw-rw---- 2 vdsm kvm 197120 Apr 6 13:29 /rhev/data-center/8b6303b3-79c6-4633-ae21-71b15ed00675/6affd8c3-2c51-4cd1-8300-bfbbb14edbe9/images/7ae9b3f7-3507-4469-a080-d0944d0ab753/30fd46c9-c738-4b13-aeca-3dc9ffc677f5 Then if I try and rerun it it says, even though move failed: 2017-04-06 13:49:27,197 INFO (jsonrpc/1) [dispatcher] Run and protect: getAllTasksStatuses, Return response: {'allT asksStatus': {'078d962c-e682-40f9-a177-2a8b479a7d8b': {'code': 212, 'message': 'Volume already exists', 'taskState': 'finished', 'taskResult': 'cleanSuccess', 'taskID': '078d962c-e682-40f9-a177-2a8b479a7d8b'}}} (logUtils:52) So now I have to clean up the disks that it failed to move so I can migrate the VM and then move the disk again. Or so it seems. Failed move disks do exist in new location, even though it "failed". vdsm.log attached. ovirt-engine-tools-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64

4 4

Re: [ovirt-users] Hosts Network Management
by Charles Tassell 09 Apr '17

09 Apr '17

Hey Kai, Go into the Hosts tab, click on the host you want to add the bonded interface to then on the Network Interfaces tab in the bottom pane. Click on Setup Host Networks and drag an unused network adaptor over the one that you want to bond it with. A box will come up and let you configure bonding parameters like which mode to use. On 2017-04-09 04:17 AM, users-request(a)ovirt.org wrote: > Date: Sat, 8 Apr 2017 23:46:27 +0200 > From: Kai Wagner <kwagner(a)suse.com> > To: Ondrej Svoboda <osvoboda(a)redhat.com>, users(a)ovirt.org > Subject: Re: [ovirt-users] Hosts Network Management > Message-ID: <b38cc8d1-d7f3-0172-fc97-6cbf31e6a8f3(a)suse.com> > Content-Type: text/plain; charset="utf-8" > > I need to create a bonded device with lacp. How can I do this through > the UI? > > Sorry, maybe it's quite easy, but I don't know how to configure it. > > > On 04/07/2017 07:10 PM, Ondrej Svoboda wrote: >> Hello Kai, >> >> I'd like to know ? what is your initial problem that you cannot solve >> through the GUI? >> >> VDSM does use a custom comment in ifcfg files, but only to recognize >> them ? if they are unknown, it acquires the relevant network devices >> from NetworkManager. But VDSM is in charge of networking >> configuration, exclusively. >> >> If you need to add extra configuration parameters in ifcfg files, or >> modify them, you could write or use a VDSM hook to alter the ifcfg >> files as they are written. >> >> But perhaps it is better for us to know what problems you are having >> and whether they can be solved by available methods. >> >> Thank you, >> Ondra >> >> On Thu, Apr 6, 2017 at 12:14 PM, Kai Wagner <kwagner(a)suse.com >> <mailto:kwagner@suse.com>> wrote: >> >> Hi all, >> >> is it possible to set a comment at the beginning of a file for network >> files -> something like don't touch this anymore please? >> >> I want to configure my network stuff on the cli and not via the UI >> because I failed now a few times. >> >> Thx >> >> Kai >> >> >> -- >> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham >> Norton, HRB 21284 (AG N?rnberg) >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org <mailto:Users@ovirt.org> >> http://lists.ovirt.org/mailman/listinfo/users >> <http://lists.ovirt.org/mailman/listinfo/users> >> >>

1 0

Hosts Network Management
by Kai Wagner 08 Apr '17

08 Apr '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WIvTsgqFc0Vw6IGKvn67rP3OvSNrUQp2q Content-Type: multipart/mixed; boundary="crsmAHLwUdrTsU3RpOWU8fVd1rFuR7MjK"; protected-headers="v1" From: Kai Wagner <kwagner(a)suse.com> To: users(a)ovirt.org Message-ID: <e30a5560-e5e2-bb38-89d7-a55bc5630d0b(a)suse.com> Subject: Hosts Network Management --crsmAHLwUdrTsU3RpOWU8fVd1rFuR7MjK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, is it possible to set a comment at the beginning of a file for network files -> something like don't touch this anymore please? I want to configure my network stuff on the cli and not via the UI because I failed now a few times. Thx Kai --=20 SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton= , HRB 21284 (AG N=C3=BCrnberg) --crsmAHLwUdrTsU3RpOWU8fVd1rFuR7MjK-- --WIvTsgqFc0Vw6IGKvn67rP3OvSNrUQp2q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJY5hULAAoJEB6MkVYW48RuVrMH/3oAENmN3vKuQRdOHH/6wHKp RWUFeN4hlIdm15iO5PXaLyCHlc7EjnvA2j7z31Pt6jVsMCaZm9TRffMXSxKQ1kfF 4nUaFNJ09p2h4m2L4s8EgRoTd3jziKVGrljEicw9tKD2HJSgfI99+6IzBNLR/jmB GbKQbwmR9oXW3kT1vAQ6eJ34XsmYO4MDWSTb6vsyRCJs9T/MIwEXP/ShioRwQaNR aoCKZm9jrUuUIAvdteJ7nOKhDr1udQzjRzKudMaaP5pRRLtPvw3rMTLs2qWHwNnP lAKWDiZrq2qn9K26OwAr83lLj+Pc4bOZVImYbC9HU0OY20Y6xs2ZH+WShxT3z6s= =atZW -----END PGP SIGNATURE----- --WIvTsgqFc0Vw6IGKvn67rP3OvSNrUQp2q--

2 2

JavaAPI exporting VM
by David David 07 Apr '17

07 Apr '17

Hello. Can't reexport a VM if this VM is already present in the export domain With Java api: *VM vm = api.getVMs().get("vm01");StorageDomain exportDomain = api.getStorageDomains().get("export"); * *Action act = vm.exportVm(new Action() { { setExclusive(True); setDiscardSnapshots(True); setStorageDomain(exportDomain); }});* And following error is returned: Exception in thread "main" code : 409 reason: Conflict detail: Cannot export VM. VM with the same identifier already exists. at org.ovirt.engine.sdk.web.HttpProxy.execute(HttpProxy.java:120) at org.ovirt.engine.sdk.web.HttpProxyBroker.add(HttpProxyBroker.java:209) at org.ovirt.engine.sdk.web.HttpProxyBroker.action(HttpProxyBroker.java:153) at org.ovirt.engine.sdk.decorators.VM.exportVm(VM.java:784)

2 1

for some reason ovirtnode creates unecessary vg and lvs
by martin chamambo 07 Apr '17

07 Apr '17

I managed to configure the mail iscsi domain for my ovirt 4.1 engine and node , it connects to the storage initially and initialises the data center ,but after rebooting the node and engine , it creates unecessary vg and lvs like below 280246d3-ac7b-44ff-8c03-dc2bcb9edb70 d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 128.00m 2d57ab88-16e4-4007-9047-55fc4a35b534 d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 128.00m ids d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 128.00m inbox d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 128.00m leases d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 2.00g master d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 1.00g metadata d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 512.00m outbox d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 128.00m xleases d5104206-5863-4f9d-9ea7-2b140c97d65f -wi-a----- 1.00g whats the cause of this NB:mY ISCSI storage is on a centos 7 box

4 7

Host in connecting state and all data domains are red in ovirt 4.1
by gflwqs gflwqs 07 Apr '17

07 Apr '17

Hi list this morning i saw one of my 2 hosts were in connecting state. When i checked the /var/log/messages on the host i saw this happened: Apr 7 06:05:38 ovirt12 journal: ovirt-ha-broker ovirt_hosted_engine_ha.broker.submonitor_base.SubmonitorBase ERROR Error executing submonitor mgmt-bridge, args {'use_ssl': 'true', 'bridge_name': 'ovirtmgmt', 'address': '0'}#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitor_base.py", line 115, in _worker#012 self.action(self._options)#012 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors/mgmt_bridge.py", line 44, in action#012 caps = cli.getVdsCapabilities()#012 File "/usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py", line 167, in _callMethod#012 raise JsonRpcNoResponseError(method)#012JsonRpcNoResponseError: [-32605] No response for JSON-RPC Host.getCapabilities request. Apr 7 06:05:40 ovirt12 journal: vdsm vds.dispatcher ERROR SSL error receiving from <yajsonrpc.betterAsyncore.Dispatcher connected ('::1', 53454, 0, 0) at 0x7fcc685ce560>: unexpected eof Is this the cause of the problem? What has happened? How do i get out of this problem? Regards Christian

1 0

Upgrading libguestfs to import debian VM
by Simon Vincent 06 Apr '17

06 Apr '17

I find that running oVirt 4.1.1 I can not import any debian based VMs as virt-v2v/libguestfs is too old. This bug report https://bugzilla.redhat.com/show_bug.cgi?id=1362497 indicates that newer versions of libguestfs support importing debian and Ubuntu VMs. Are there any plans to include a newer version of libguestfs in oVirt soon? If I built a newer version of libguestfs on my ovirt-node would it break everything? Regards Simon

2 1

mount glusterfs from 127.0.0.1
by /dev/null 06 Apr '17

06 Apr '17

Hello all together, having a three node oVirt cluster for virtualization and gluster, each node providing bricks for a replica 3 volume, I would like to mount the volume from 127.0.0.1 to distribute i/o and to have a better failover situation. This leads to a volume having the same address in oVirt althoght it is addressed on different hosts. Is this common, supported, relyable and recommended? Thanks in advance! /dev/null -- Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber. For all your IT requirements visit: http://www.transtec.co.uk

2 3

New SAN Storage Domain: Cannot deactivate Logical Volume
by Николаев Алексей 06 Apr '17

06 Apr '17

3 8