Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup Host Networks"
- Original Message - > From: "Alona Kaplan" > To: ov...@timmi.org > Cc: users@ovirt.org > Sent: Monday, February 1, 2016 6:27:15 PM > Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup Host > Networks" > > Hi Christoph, > > I think that I know what happened on your environment. > Since, as you said, the names of the nics were changed after reboot. Nic > names that previously were used for sriov nics, are now used for a regular > nics. > > As I see from looking at the results of your queries- > Previously - eth2, eth3, eth4 and eth5 were sriov nics. > Now after the reboot - eth1, eth3, eth4 and eth6 are sriov nics. > > Due to a bug (https://bugzilla.redhat.com/1303640), currently the engine > doesn't know how to deal with this situation and the data in the db gets > corrupted. > Until the bug is fixed, the way to fix it manually is to clean the host's > data from some tables and then refreshing the capabilities of the host. > > Please do the following - > If you didn't do the steps from the previous mail. Before doing the deleting step, please stop the VMs that run on this host (lxedna.voipfuture.com). If you already done the delete, anyway, please stop the VMs that run on this host (lxedna.voipfuture.com). You can re-run them only after you finish all the steps from the previous mail. > 1. delete from host_device where > host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > 2. delete from host_nic_vfs_config where nic_id in (select id from > vds_interface where vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'); > > After it, please do - > 1. select from host_device where > host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > 2. select from host_nic_vfs_config where nic_id in (select id from > vds_interface where vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'); > > Make sure both of the queries return empty values. > > Then click on the 'refresh host's capabilities' button. > > Please let me know if after doing so you manage to open the host's setup > network dialog. > > Thanks, > Alona. > > - Original Message - > > From: ov...@timmi.org > > To: "Alona Kaplan" > > Cc: "Martin Mucha" , users@ovirt.org > > Sent: Sunday, January 31, 2016 4:47:36 PM > > Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup Host > > Networks" > > > > Hi Alona, > > > > please find the requested output in the attachment. > > > > Best regards > > Christoph > > > > Am 31.01.2016 um 15:09 schrieb Alona Kaplan: > > > Hi Christoph, > > > > > > Please send me also the output of the following- > > > > > > On the host (The problematic host is - 'lxedna.voipfuture.com', right?)- > > > 1. vdsClient -s 0 getVdsCapabilities > > > 2. vdsClient -s 0 hostdevListByCaps > > > > > > On the DB- > > > 1. select * from vds_interface where > > > vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > > > 2. select * from host_device where > > > host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > > > 3. select * from host_nic_vfs_config; > > > > > > Thanks, > > > Alona. > > > > > > - Original Message - > > >> From: ov...@timmi.org > > >> To: "Alona Kaplan" , "Martin Mucha" > > >> > > >> Cc: users@ovirt.org > > >> Sent: Friday, January 29, 2016 9:25:53 AM > > >> Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup > > >> Host Networks" > > >> > > >> Hi Alona, > > >> > > >> here are my answers. > > >> > > >> 1. no, but I did that just now and it does not change the behavior. > > >> 2. the host is up > > >> 3. it is in the attachment > > >> > > >> Best regards > > >> Christoph > > >> > > >> Am 28.01.2016 um 15:47 schrieb Alona Kaplan: > > >>> Hi Christoph, > > >>> > > >>> I have some questions/requests- > > >>> > > >>> 1. After the reboot and the rewiring you did- did you press manually on > > >>> the > > >>> Host's 'Refresh Capabilities' button (it is part of the Host's actions > > >>> in > > >>> the host's main tab)? > > >>> If not, please do it and let me know if after doing it you manage to > > >>> open > > >>> the 'setup networks' dialog or still get the same error. > > >>> 2. What is the status of your host? Up/Maintenance/some thing else? > > >>> 3. Please attach the full log of your engine. > > >>> > > >>> Thanks, > > >>> Alona. > > >>> > > >>> - Original Message - > > From: "Martin Mucha" > > To: ov...@timmi.org > > Cc: users@ovirt.org > > Sent: Thursday, January 28, 2016 11:46:30 AM > > Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup > > Host Networks" > > > > ok, thanks. Just o inform you — so far it seems there is inconsistency > > in > > assumptions of what can be nullable and what can not. We just need to > > decide > > which approach is correct and fix rest. > > M. > > > > - Original Message - > > > Hi Martin, > > > > > > please let me know I can help. > > > > > > Best regards > > > Christoph > > > > > > Am 28.01
[ovirt-users] Migrate Hosted Engine to new iSCSI san with new IP/Target
In a hosted-engine deployment has anyone had to migrate to a new iSCSI SAN? I can not figure out how to move the engine(s) to a new iSCSI target.. The SAN’s can fully replicate to one another and I can move the LUN to the other device but don’t see how to stop the engine and change the settings for it’s iSCSI target to another IP/IQN. Any direction would be greatly appreciated - I am looking for any method to get this done, we have to retire the old SAN - Thanks.___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Best backup solution for oVirt
Hi all, Could anyone please suggest me best backup and recovery solution for oVirt setup. Both third party commercial and Opensource / Built-in solution. -- With Regards, RK, +91 9840483044 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Storage network clarification
Thanks I will add those steps to my notes and try again some time in the future. Trying to move storage network functions from ovirtmgmt to a dedicated logical network for an existing gluster volume did not go well for me. I did not put much effort into recovering, but I lost the storage domain completely. I did not collect any logs because I was pressed for time. I am finding it easier to manage gluster outside of ovirt for now. Without knowing how VDSM is going to try to approach a task it becomes more time consuming (and sometimes destructive) to work with VDSM than to just do things manually. On Tue, Jan 19, 2016 at 12:44 AM, Sahina Bose wrote: > > > On 01/19/2016 12:37 PM, Nicolas Ecarnot wrote: >> >> Hi Sahina, >> >> Le 19/01/2016 07:02, Sahina Bose a écrit : >>> >>> The steps to make sure gluster uses separate network for data traffic : >>> >>> 1. Create a logical network (non-VM), and mark it's role as "Gluster" >>> 2. After adding the host via the ovirtmgmt hostname/ ip address, assign >>> this gluster network to your interface (with the storage sub-net) >>> This step will initiate a peer probe of the host with this additonal >>> ip address. >>> >>> 3. When creating a volume after an interface/bond is tagged with gluster >>> network, the bricks are added using the gluster n/w's ip address. Now >>> when clients connect to the volume, traffic is routed via your gluster >>> network that's used by bricks. >> >> >> Does that mean that there's no way to reach this goal with an existing >> volume, previously created, and that was (alas) using the management >> network? > > > > There's some ongoing work to replace network used by brick - > http://review.gluster.org/#/c/12250/ and https://gerrit.ovirt.org/#/c/51685/ > [+Kaushal, Anuradha for further inputs and if there's any manual workaround > possible] > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] howto change hosted-engine config memory
I am trying to change memory of my hosted engine. I am running oVirt 3.6 with CentOS 6 Hosts with hosted engine on nfs3 1. I put hosted-engine to maintenance, shutdown vm 2. update /etc/ovirt-hosted-engine/vm.conf 3. restart vm disable maintenance Memory is still old value. How can I change the hosted engine VM? I did found: http://www.ovirt.org/Features/Hosted_Engine_configuration_on_shared_storage When I check /etc/ovirt-hosted-engine/hosted-engine.conf there is no "conf_volume_UUID" entry. Do I need to create a shared config volume entry ( conf_volume_UUID ), so I can edit hosted engine VM? If so, how can this be done? I did try to rerun engine-setup, but this did not trigger anything. Kind regards, Paul Groeneweg Pazion ***disclaimer*** "This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation." -- Met vriendelijke groeten, Paul Groeneweg Pazion Webdevelopment - Hosting - Apps T +31 26 3020038 M +31 614 277 577 E p...@pazion.nl ***disclaimer*** "This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation." ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Cannot add new host
On Mon, Feb 1, 2016 at 7:10 PM, Marcelo Leandro wrote: > I copied wrong. > the authorityInfoAccess is not empty. > yes, i followed correctly. > > attached cert.conf. > Ok, thanks. But keyUsage = critical,${ENV::OVIRT_KU} extendedKeyUsage = ${ENV::OVIRT_EKU} still looks strage. Can you please check what you had before the migration? > > thanks > > > > 2016-02-01 14:25 GMT-03:00 Simone Tiraboschi : > > Thanks Marcelo, > > unfortunately I can confirm you that it's broken: ${ENV::OVIRT_EKU} > didn't > > get correctly replaced and authorityInfoAccess is empty. > > Now we need to understand why it got generated this way, maybe something > > went wrong in the backup and restore procedure. > > Did you correctly followed this? > > > http://www.ovirt.org/User:Adrian15/oVirt_engine_migration#Restore_Certificates > > > > thanks, > > Simone > > > > > > On Mon, Feb 1, 2016 at 5:49 PM, Marcelo Leandro > > wrote: > >> > >> Hello simone, > >> > >> yes, > >> it's here: > >> > >> RANDFILE = .rnd > >> > >> [req] > >> > >> default_bits = rsa:2048 > >> default_keyfile = keys/cert.pem > >> distinguished_name = req_distinguished_name > >> attributes = req_attributes > >> x509_extensions = v3_ca > >> > >> [req_attributes] > >> > >> [v3_ca] > >> > >> subjectKeyIdentifier = hash > >> authorityInfoAccess = > >> > >> caIssuers;URI: > http://srv-ovirt01:80/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA > >> authorityKeyIdentifier = keyid:always,issuer:always > >> basicConstraints = CA:false > >> keyUsage = critical,digitalSignature,keyEncipherment > >> extendedKeyUsage = critical,serverAuth,clientAuth > >> > >> [custom] > >> subjectKeyIdentifier = hash > >> authorityInfoAccess = > >> > >> caIssuers;URI: > http://srv-ovirt01:80/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA > >> authorityKeyIdentifier = keyid:always,issuer:always > >> basicConstraints = CA:false > >> keyUsage = critical,${ENV::OVIRT_KU} > >> extendedKeyUsage = ${ENV::OVIRT_EKU} > >> > >> [req_distinguished_name] > >> > >> > >> Thanks. > >> > >> 2016-02-01 11:49 GMT-03:00 Simone Tiraboschi : > >> > > >> > On Mon, Feb 1, 2016 at 3:30 PM, Marcelo Leandro < > marcelol...@gmail.com> > >> > wrote: > >> >> > >> >> ERROR: on line 27 of config file 'cert.conf' > >> >> 139871306037152:error:0E065068:configuration file > >> >> routines:STR_COPY:variable has no value:conf_def.c:618:line 27 > >> >> Cannot sign certificate > >> > > >> > > >> > This looks strange; can you please share the content of > >> > /etc/pki/ovirt-engine/cert.conf ? > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
Nir - At this time I cant do anything. I succesfully upgraded the CentOS 6.7 engine VM to 3.6 but after migrating it to a new node packet loss on the VM is significant. I was able to finally get access to the VM by running SSH client command with -C and running 'service ovirt-engine stop' of which the packet loss went away. What can I do? What can I send to attach here? As of now I cannot add any new systems because the ovirt-engine is pretty much dead. I am learning towards my only option is to rebuild everything on CentOS 7. Is it possible for me to configure an EL7 hosted engine along side the EL6's while I migrate and upgrade?or should I just restart from scratch? On Mon, Feb 1, 2016 at 3:14 PM, Charles Kozler wrote: > Thank you. I am in the process of upgrading my nodes to 7 although since > the upgrade of my engine to ovirt 3.6 the network on the VM itself has > become very instable. Ping packets are unresponsive from time to time and I > cannot get a reliable SSH connection. My guess is something inside ovirt > 3.6 does not like to run on a 3.5 node (expected I guess) and something is > occurring inside of the brains somewhere. My hope now is to get my EL7 node > up and running and hopefully join it to my cluster then start my hosted > engine there > > On Mon, Feb 1, 2016 at 3:12 PM, Nir Soffer wrote: > >> On Mon, Feb 1, 2016 at 7:52 PM, Charles Kozler >> wrote: >> > Sorry to be clear..the only way to resolve the memory leak I am facing >> now >> > is to upgrade to el7? >> >> If you want to use official packages, yes. >> >> But this is free software, so *you* are free to build your own package. >> >> The patches you need are in the ovirt-3.5 branch: >> https://github.com/oVirt/vdsm/tree/ovirt-3.5 >> >> You clone vdsm, checkout this branch, and build it. But you will have to >> support >> it yourself, because we are focusing on refining 3.6 and working on 4.0. >> >> Unless you cannot upgrade to el 7 or fedora >= 22, I recommend to upgrade >> your >> hosts and use official packages. >> >> > >> > Also the engine can stay running on el6 yes? >> Yes >> >> > I successfully upgraded my >> > engine to ovirt 3.6 in el6. Do I need to make my engine vm el7 too? >> No. >> >> Nir >> > >> > On Feb 1, 2016 12:49 PM, "Charles Kozler" wrote: >> >> >> >> So I will still have the memory leak? >> >> >> >> On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" >> wrote: >> >>> >> >>> >> >>> >> >>> On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler >> >>> wrote: >> >> So what about the bug that I hit for vdsm as listed above by Nir? >> Will I >> have that patch to avoid the memory leak or no? Upgrading an entire >> node to >> centos 7 is not actually feasible and was previously outlined above >> that I >> just needed to upgrade to ovirt 3.6 and no mention of OS change ... >> >>> >> >>> >> >>> You cannot install VDSM from 3.6 on el6: >> >>> >> >>> >> http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar >> >>> and there is no plan for a 3.5.8. >> >>> >> >>> >> >> On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" >> wrote: >> > >> > >> > >> > On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler < >> char...@fixflyer.com> >> > wrote: >> >> >> >> Sandro / Nir - >> >> >> >> I followed your steps plus >> >> >> >> >> >> >> http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL >> >> >> >> Engine upgraded fine but then when I got to upgrading a node I did: >> >> >> >> $ yum install >> >> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm >> >> $ yum update -y >> >> >> >> And then rebooted the node. I noticed libvirt was updated by a .1 >> >> release number but vdsm (where the memory leak issue I thought >> was?) was not >> >> upgraded. In fact, very little of ovirt packages on the node were >> noticeably >> >> not updated >> >> >> > >> > We are not building vdsm for el6 in 3.6, you need also to upgrade to >> > el7 if you want that. >> > >> >> >> >> Updated node received the following updated packages during the >> >> install: >> >> >> >> http://pastebin.ca/3362714 >> >> >> >> Note specifically the only packages updated via the ovirt3.6 >> >> repository was ioprocess, otopi, ovirt-engine-sdk-python, >> ovirt-host-deploy, >> >> ovirt-release36, and python-ioprocess. I had expected to see some >> packages >> >> like vdsm and the likes updated - or was this not the case? >> >> >> >> Upgraded node: >> >> >> >> [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm >> >> vdsm-4.16.30-0.el6.x86_64 >> >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >> >> vdsm-cli-4.16.30-0.el6.noarch >> >> vdsm-yajsonrpc-4.16.30-0.el6.noarch >> >> vdsm-jsonrpc-4.16.30-0.el6.noarch >> >> vdsm-xmlrpc-4.16.30-0.el6.noarch >> >> vdsm-python-4.16.30-0.el6.noarch >> >> >> >> Nonu
Re: [ovirt-users] [3.6] Delete node
Hi Mario, On 02/01/2016 02:12 PM, [Syci] Mario Montes wrote: Hi, yes I put on maintenance first, but the option is disable. The node is fail. I need delete force. Looks like your host is in fail not in maintenance, you can force it with the below commands and later remove it. step#1 On Engine machine: $ su - postgres $ psql -d engine engine# update vds_dynamic set status=2 where vds_id in (select vds_id from vds_static where vds_name LIKE '%THE_NODE_HOST_NAME%'); step#2 Go back to admin portal, your host will be in maint. and you should be able to remove it. Please keep the list in the reply for other people might help and provide the logs from engine/vdsm. *De: *"Douglas Schilling Landgraf" *Para: *"[Syci] Mario Montes" , "users" *Enviados: *Lunes, 1 de Febrero 2016 19:07:23 *Asunto: *Re: [ovirt-users] [3.6] Delete node Hi, On 02/01/2016 01:54 PM, [Syci] Mario Montes wrote: Hello, I need delete one node, but the option "Delete" is not active. How I do it? Have you tried to put the host into maintenance first? http://www.ovirt.org/OVirt_Administration_Guide#Removing_a_Host ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
Thank you. I am in the process of upgrading my nodes to 7 although since the upgrade of my engine to ovirt 3.6 the network on the VM itself has become very instable. Ping packets are unresponsive from time to time and I cannot get a reliable SSH connection. My guess is something inside ovirt 3.6 does not like to run on a 3.5 node (expected I guess) and something is occurring inside of the brains somewhere. My hope now is to get my EL7 node up and running and hopefully join it to my cluster then start my hosted engine there On Mon, Feb 1, 2016 at 3:12 PM, Nir Soffer wrote: > On Mon, Feb 1, 2016 at 7:52 PM, Charles Kozler > wrote: > > Sorry to be clear..the only way to resolve the memory leak I am facing > now > > is to upgrade to el7? > > If you want to use official packages, yes. > > But this is free software, so *you* are free to build your own package. > > The patches you need are in the ovirt-3.5 branch: > https://github.com/oVirt/vdsm/tree/ovirt-3.5 > > You clone vdsm, checkout this branch, and build it. But you will have to > support > it yourself, because we are focusing on refining 3.6 and working on 4.0. > > Unless you cannot upgrade to el 7 or fedora >= 22, I recommend to upgrade > your > hosts and use official packages. > > > > > Also the engine can stay running on el6 yes? > Yes > > > I successfully upgraded my > > engine to ovirt 3.6 in el6. Do I need to make my engine vm el7 too? > No. > > Nir > > > > On Feb 1, 2016 12:49 PM, "Charles Kozler" wrote: > >> > >> So I will still have the memory leak? > >> > >> On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" > wrote: > >>> > >>> > >>> > >>> On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler > >>> wrote: > > So what about the bug that I hit for vdsm as listed above by Nir? > Will I > have that patch to avoid the memory leak or no? Upgrading an entire > node to > centos 7 is not actually feasible and was previously outlined above > that I > just needed to upgrade to ovirt 3.6 and no mention of OS change ... > >>> > >>> > >>> You cannot install VDSM from 3.6 on el6: > >>> > >>> > http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar > >>> and there is no plan for a 3.5.8. > >>> > >>> > > On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" > wrote: > > > > > > > > On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler > > > wrote: > >> > >> Sandro / Nir - > >> > >> I followed your steps plus > >> > >> > >> > http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL > >> > >> Engine upgraded fine but then when I got to upgrading a node I did: > >> > >> $ yum install > >> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm > >> $ yum update -y > >> > >> And then rebooted the node. I noticed libvirt was updated by a .1 > >> release number but vdsm (where the memory leak issue I thought > was?) was not > >> upgraded. In fact, very little of ovirt packages on the node were > noticeably > >> not updated > >> > > > > We are not building vdsm for el6 in 3.6, you need also to upgrade to > > el7 if you want that. > > > >> > >> Updated node received the following updated packages during the > >> install: > >> > >> http://pastebin.ca/3362714 > >> > >> Note specifically the only packages updated via the ovirt3.6 > >> repository was ioprocess, otopi, ovirt-engine-sdk-python, > ovirt-host-deploy, > >> ovirt-release36, and python-ioprocess. I had expected to see some > packages > >> like vdsm and the likes updated - or was this not the case? > >> > >> Upgraded node: > >> > >> [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm > >> vdsm-4.16.30-0.el6.x86_64 > >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch > >> vdsm-cli-4.16.30-0.el6.noarch > >> vdsm-yajsonrpc-4.16.30-0.el6.noarch > >> vdsm-jsonrpc-4.16.30-0.el6.noarch > >> vdsm-xmlrpc-4.16.30-0.el6.noarch > >> vdsm-python-4.16.30-0.el6.noarch > >> > >> Nonupgraded node > >> > >> [compute[root@node01 ~]$ rpm -qa | grep -i vdsm > >> vdsm-cli-4.16.30-0.el6.noarch > >> vdsm-jsonrpc-4.16.30-0.el6.noarch > >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch > >> vdsm-xmlrpc-4.16.30-0.el6.noarch > >> vdsm-yajsonrpc-4.16.30-0.el6.noarch > >> vdsm-4.16.30-0.el6.x86_64 > >> vdsm-python-4.16.30-0.el6.noarch > >> > >> Also, the docs stated that the engine VM would migrate to the > freshly > >> upgraded node since it would have a higher number but it did not > >> > >> So I cant really confirm whether or not my issue will be resolved? > Or > >> that if the node was actually updated properly? > >> > >> Please advise on how to confirm > >> > >> Thank you! > >> > >> On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler > >> wrote: > >>> > >>> Thanks Sandro. Should cl
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
On Mon, Feb 1, 2016 at 7:52 PM, Charles Kozler wrote: > Sorry to be clear..the only way to resolve the memory leak I am facing now > is to upgrade to el7? If you want to use official packages, yes. But this is free software, so *you* are free to build your own package. The patches you need are in the ovirt-3.5 branch: https://github.com/oVirt/vdsm/tree/ovirt-3.5 You clone vdsm, checkout this branch, and build it. But you will have to support it yourself, because we are focusing on refining 3.6 and working on 4.0. Unless you cannot upgrade to el 7 or fedora >= 22, I recommend to upgrade your hosts and use official packages. > > Also the engine can stay running on el6 yes? Yes > I successfully upgraded my > engine to ovirt 3.6 in el6. Do I need to make my engine vm el7 too? No. Nir > > On Feb 1, 2016 12:49 PM, "Charles Kozler" wrote: >> >> So I will still have the memory leak? >> >> On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" wrote: >>> >>> >>> >>> On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler >>> wrote: So what about the bug that I hit for vdsm as listed above by Nir? Will I have that patch to avoid the memory leak or no? Upgrading an entire node to centos 7 is not actually feasible and was previously outlined above that I just needed to upgrade to ovirt 3.6 and no mention of OS change ... >>> >>> >>> You cannot install VDSM from 3.6 on el6: >>> >>> http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar >>> and there is no plan for a 3.5.8. >>> >>> On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" wrote: > > > > On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler > wrote: >> >> Sandro / Nir - >> >> I followed your steps plus >> >> >> http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL >> >> Engine upgraded fine but then when I got to upgrading a node I did: >> >> $ yum install >> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm >> $ yum update -y >> >> And then rebooted the node. I noticed libvirt was updated by a .1 >> release number but vdsm (where the memory leak issue I thought was?) was >> not >> upgraded. In fact, very little of ovirt packages on the node were >> noticeably >> not updated >> > > We are not building vdsm for el6 in 3.6, you need also to upgrade to > el7 if you want that. > >> >> Updated node received the following updated packages during the >> install: >> >> http://pastebin.ca/3362714 >> >> Note specifically the only packages updated via the ovirt3.6 >> repository was ioprocess, otopi, ovirt-engine-sdk-python, >> ovirt-host-deploy, >> ovirt-release36, and python-ioprocess. I had expected to see some >> packages >> like vdsm and the likes updated - or was this not the case? >> >> Upgraded node: >> >> [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm >> vdsm-4.16.30-0.el6.x86_64 >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >> vdsm-cli-4.16.30-0.el6.noarch >> vdsm-yajsonrpc-4.16.30-0.el6.noarch >> vdsm-jsonrpc-4.16.30-0.el6.noarch >> vdsm-xmlrpc-4.16.30-0.el6.noarch >> vdsm-python-4.16.30-0.el6.noarch >> >> Nonupgraded node >> >> [compute[root@node01 ~]$ rpm -qa | grep -i vdsm >> vdsm-cli-4.16.30-0.el6.noarch >> vdsm-jsonrpc-4.16.30-0.el6.noarch >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >> vdsm-xmlrpc-4.16.30-0.el6.noarch >> vdsm-yajsonrpc-4.16.30-0.el6.noarch >> vdsm-4.16.30-0.el6.x86_64 >> vdsm-python-4.16.30-0.el6.noarch >> >> Also, the docs stated that the engine VM would migrate to the freshly >> upgraded node since it would have a higher number but it did not >> >> So I cant really confirm whether or not my issue will be resolved? Or >> that if the node was actually updated properly? >> >> Please advise on how to confirm >> >> Thank you! >> >> On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler >> wrote: >>> >>> Thanks Sandro. Should clarify my storage is external on a redundant >>> SAN. The steps I was concerned about was the actual upgrade. I tried to >>> upgrade before and it brought my entire stack crumbling down so I'm >>> hesitant. This bug seems like a huge bug that should at least somehow >>> backported if at all possible because, to me, it renders the entire >>> 3.5.6 >>> branch unusable as no VMs can be deployed since OOM will eventually kill >>> them. In any case that's just my opinion and I'm a new user to ovirt. >>> The >>> docs I followed originally got me going how I need and somehow didn't >>> work >>> for 3.6 in the same fashion so naturally I'm hesitant to upgrade but >>> clearly >>> have no option if I want to continue my infrastructure on ovirt. Thank >>> you >>> again
Re: [ovirt-users] Mixing CPU types
Though our new oVirt setup is better in most ways, cross-CPU-type migration is one of the features I miss from Proxmox. KVM supports mixed-CPU migration for a while now, even between AMD and Intel. http://www.linux-kvm.org/page/Migration I'm using a bunch of re-purposed servers with a mix of AMD and Intel. I separate them into clusters, as noted, but it sure would be nice to be able to live migrate between them. :) -- Matthew Trent Network Engineer Lewis County IT Services > Hi Rene, > > Thank you very much for coming back to me. > > That's perfect then and answers my questions exactly. > > Much appreciated. > > Regards. > >Neil Wilson. > > >On Wed, Jan 27, 2016 at 1:57 PM, René Koch wrote: >> >> Hi Neil, >> >> You can mix cpu types (but not AMD and Intel) if you leave the cluster >> level at the lowest cpu level. >> I personally don't mix cpu levels if possible, but instead create own >> clusters for each cpu type in order to be able to use the newest cpu >> features... >> >> >> Regards, >> René >> >> >> On 01/27/2016 12:53 PM, Neil wrote: >> >> Hi guys, >> >> I currently have an oVirt 3.5 cluster with Sandy Bridge Xeon CPU's, and I >> need to add a new host for more RAM and vCPU's, however the new Xeon e5 >> cpu's are Haswell based. >> >> Can I mix CPU types (Haswell and Sandy Bridge) in my cluster and will I be >> able to migrate between my hosts? >> >> I'm guessing that for this to work I'll need to leave my "CPU type" set to >> Sandy Bridge, will the Haswell based CPU be compatible with my cluster, but >> just run without any Haswell type features? >> >> Apologies if this is a dumb question or if it's been answered before. >> >> Thank you. >> >> Regards. >> >> Neil Wilson >> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [3.6] Delete node
Hi, On 02/01/2016 01:54 PM, [Syci] Mario Montes wrote: Hello, I need delete one node, but the option "Delete" is not active. How I do it? Have you tried to put the host into maintenance first? http://www.ovirt.org/OVirt_Administration_Guide#Removing_a_Host ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] [3.6] Delete node
Hello, I need delete one node, but the option "Delete" is not active. How I do it? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
Sorry to be clear..the only way to resolve the memory leak I am facing now is to upgrade to el7? Also the engine can stay running on el6 yes? I successfully upgraded my engine to ovirt 3.6 in el6. Do I need to make my engine vm el7 too? On Feb 1, 2016 12:49 PM, "Charles Kozler" wrote: > So I will still have the memory leak? > On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" wrote: > >> >> >> On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler >> wrote: >> >>> So what about the bug that I hit for vdsm as listed above by Nir? Will I >>> have that patch to avoid the memory leak or no? Upgrading an entire node to >>> centos 7 is not actually feasible and was previously outlined above that I >>> just needed to upgrade to ovirt 3.6 and no mention of OS change ... >>> >> >> You cannot install VDSM from 3.6 on el6: >> >> http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar >> and there is no plan for a 3.5.8. >> >> >> >>> On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" >>> wrote: >>> On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler wrote: > Sandro / Nir - > > I followed your steps plus > > http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL > > Engine upgraded fine but then when I got to upgrading a node I did: > > $ yum install > http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm > $ yum update -y > > And then rebooted the node. I noticed libvirt was updated by a .1 > release number but vdsm (where the memory leak issue I thought was?) was > not upgraded. In fact, very little of ovirt packages on the node were > noticeably not updated > > We are not building vdsm for el6 in 3.6, you need also to upgrade to el7 if you want that. > Updated node received the following updated packages during the > install: > > http://pastebin.ca/3362714 > > Note specifically the only packages updated via the ovirt3.6 > repository > was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, > ovirt-release36, and python-ioprocess. I had expected to see some packages > like vdsm and the likes updated - or was this not the case? > > Upgraded node: > > [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm > vdsm-4.16.30-0.el6.x86_64 > vdsm-python-zombiereaper-4.16.30-0.el6.noarch > vdsm-cli-4.16.30-0.el6.noarch > vdsm-yajsonrpc-4.16.30-0.el6.noarch > vdsm-jsonrpc-4.16.30-0.el6.noarch > vdsm-xmlrpc-4.16.30-0.el6.noarch > vdsm-python-4.16.30-0.el6.noarch > > Nonupgraded node > > [compute[root@node01 ~]$ rpm -qa | grep -i vdsm > vdsm-cli-4.16.30-0.el6.noarch > vdsm-jsonrpc-4.16.30-0.el6.noarch > vdsm-python-zombiereaper-4.16.30-0.el6.noarch > vdsm-xmlrpc-4.16.30-0.el6.noarch > vdsm-yajsonrpc-4.16.30-0.el6.noarch > vdsm-4.16.30-0.el6.x86_64 > vdsm-python-4.16.30-0.el6.noarch > > Also, the docs stated that the engine VM would migrate to the freshly > upgraded node since it would have a higher number but it did not > > So I cant really confirm whether or not my issue will be resolved? Or > that if the node was actually updated properly? > > Please advise on how to confirm > > Thank you! > > On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler > wrote: > >> Thanks Sandro. Should clarify my storage is external on a redundant >> SAN. The steps I was concerned about was the actual upgrade. I tried to >> upgrade before and it brought my entire stack crumbling down so I'm >> hesitant. This bug seems like a huge bug that should at least somehow >> backported if at all possible because, to me, it renders the entire 3.5.6 >> branch unusable as no VMs can be deployed since OOM will eventually kill >> them. In any case that's just my opinion and I'm a new user to ovirt. The >> docs I followed originally got me going how I need and somehow didn't >> work >> for 3.6 in the same fashion so naturally I'm hesitant to upgrade but >> clearly have no option if I want to continue my infrastructure on ovirt. >> Thank you again for taking the time out to assist me, I truly appreciate >> it. I will try an upgrade next week and pray it all goes well :-) >> On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" >> wrote: >> >>> >>> >>> On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler < >>> char...@fixflyer.com> wrote: >>> Sandro - Do you have available documentation that can support upgrading self hosted? I followed this http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ Would it be as easy as installing the RPM and then running yum upgrade? >>> Note that mentioned article describes an unsupported hyperconverged >>> setup run
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
So I will still have the memory leak? On Feb 1, 2016 12:39 PM, "Simone Tiraboschi" wrote: > > > On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler > wrote: > >> So what about the bug that I hit for vdsm as listed above by Nir? Will I >> have that patch to avoid the memory leak or no? Upgrading an entire node to >> centos 7 is not actually feasible and was previously outlined above that I >> just needed to upgrade to ovirt 3.6 and no mention of OS change ... >> > > You cannot install VDSM from 3.6 on el6: > > http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar > and there is no plan for a 3.5.8. > > > >> On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" wrote: >> >>> >>> >>> On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler >>> wrote: >>> Sandro / Nir - I followed your steps plus http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL Engine upgraded fine but then when I got to upgrading a node I did: $ yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm $ yum update -y And then rebooted the node. I noticed libvirt was updated by a .1 release number but vdsm (where the memory leak issue I thought was?) was not upgraded. In fact, very little of ovirt packages on the node were noticeably not updated >>> We are not building vdsm for el6 in 3.6, you need also to upgrade to el7 >>> if you want that. >>> >>> Updated node received the following updated packages during the install: http://pastebin.ca/3362714 Note specifically the only packages updated via the ovirt3.6 repository was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, ovirt-release36, and python-ioprocess. I had expected to see some packages like vdsm and the likes updated - or was this not the case? Upgraded node: [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm vdsm-4.16.30-0.el6.x86_64 vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-cli-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch Nonupgraded node [compute[root@node01 ~]$ rpm -qa | grep -i vdsm vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch vdsm-4.16.30-0.el6.x86_64 vdsm-python-4.16.30-0.el6.noarch Also, the docs stated that the engine VM would migrate to the freshly upgraded node since it would have a higher number but it did not So I cant really confirm whether or not my issue will be resolved? Or that if the node was actually updated properly? Please advise on how to confirm Thank you! On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler wrote: > Thanks Sandro. Should clarify my storage is external on a redundant > SAN. The steps I was concerned about was the actual upgrade. I tried to > upgrade before and it brought my entire stack crumbling down so I'm > hesitant. This bug seems like a huge bug that should at least somehow > backported if at all possible because, to me, it renders the entire 3.5.6 > branch unusable as no VMs can be deployed since OOM will eventually kill > them. In any case that's just my opinion and I'm a new user to ovirt. The > docs I followed originally got me going how I need and somehow didn't work > for 3.6 in the same fashion so naturally I'm hesitant to upgrade but > clearly have no option if I want to continue my infrastructure on ovirt. > Thank you again for taking the time out to assist me, I truly appreciate > it. I will try an upgrade next week and pray it all goes well :-) > On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" > wrote: > >> >> >> On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler < >> char...@fixflyer.com> wrote: >> >>> Sandro - >>> >>> Do you have available documentation that can support upgrading self >>> hosted? I followed this >>> http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ >>> >>> Would it be as easy as installing the RPM and then running yum >>> upgrade? >>> >>> >> Note that mentioned article describes an unsupported hyperconverged >> setup running NFS over Gluster. >> That said, >> 1) put the hosted-engine storage domain into global maintenance mode >> 2) upgrade the engine VM >> 3) select the first host to upgrade and put it under maintenance from >> the engine, wait for the engine vm to migrate if needed. >> 4) yum upgrade the first host and wait until ovirt-ha-agent completes >> 5) exit global and local maintenance mode >> 6) repeat 3-5 on a
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
On Mon, Feb 1, 2016 at 6:33 PM, Charles Kozler wrote: > So what about the bug that I hit for vdsm as listed above by Nir? Will I > have that patch to avoid the memory leak or no? Upgrading an entire node to > centos 7 is not actually feasible and was previously outlined above that I > just needed to upgrade to ovirt 3.6 and no mention of OS change ... > You cannot install VDSM from 3.6 on el6: http://www.ovirt.org/OVirt_3.6_Release_Notes#RHEL_6.7_-_CentOS_6.7_and_similar and there is no plan for a 3.5.8. > On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" wrote: > >> >> >> On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler >> wrote: >> >>> Sandro / Nir - >>> >>> I followed your steps plus >>> >>> http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL >>> >>> Engine upgraded fine but then when I got to upgrading a node I did: >>> >>> $ yum install >>> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm >>> $ yum update -y >>> >>> And then rebooted the node. I noticed libvirt was updated by a .1 >>> release number but vdsm (where the memory leak issue I thought was?) was >>> not upgraded. In fact, very little of ovirt packages on the node were >>> noticeably not updated >>> >>> >> We are not building vdsm for el6 in 3.6, you need also to upgrade to el7 >> if you want that. >> >> >>> Updated node received the following updated packages during the install: >>> >>> http://pastebin.ca/3362714 >>> >>> Note specifically the only packages updated via the ovirt3.6 repository >>> was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, >>> ovirt-release36, and python-ioprocess. I had expected to see some packages >>> like vdsm and the likes updated - or was this not the case? >>> >>> Upgraded node: >>> >>> [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm >>> vdsm-4.16.30-0.el6.x86_64 >>> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >>> vdsm-cli-4.16.30-0.el6.noarch >>> vdsm-yajsonrpc-4.16.30-0.el6.noarch >>> vdsm-jsonrpc-4.16.30-0.el6.noarch >>> vdsm-xmlrpc-4.16.30-0.el6.noarch >>> vdsm-python-4.16.30-0.el6.noarch >>> >>> Nonupgraded node >>> >>> [compute[root@node01 ~]$ rpm -qa | grep -i vdsm >>> vdsm-cli-4.16.30-0.el6.noarch >>> vdsm-jsonrpc-4.16.30-0.el6.noarch >>> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >>> vdsm-xmlrpc-4.16.30-0.el6.noarch >>> vdsm-yajsonrpc-4.16.30-0.el6.noarch >>> vdsm-4.16.30-0.el6.x86_64 >>> vdsm-python-4.16.30-0.el6.noarch >>> >>> Also, the docs stated that the engine VM would migrate to the freshly >>> upgraded node since it would have a higher number but it did not >>> >>> So I cant really confirm whether or not my issue will be resolved? Or >>> that if the node was actually updated properly? >>> >>> Please advise on how to confirm >>> >>> Thank you! >>> >>> On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler >>> wrote: >>> Thanks Sandro. Should clarify my storage is external on a redundant SAN. The steps I was concerned about was the actual upgrade. I tried to upgrade before and it brought my entire stack crumbling down so I'm hesitant. This bug seems like a huge bug that should at least somehow backported if at all possible because, to me, it renders the entire 3.5.6 branch unusable as no VMs can be deployed since OOM will eventually kill them. In any case that's just my opinion and I'm a new user to ovirt. The docs I followed originally got me going how I need and somehow didn't work for 3.6 in the same fashion so naturally I'm hesitant to upgrade but clearly have no option if I want to continue my infrastructure on ovirt. Thank you again for taking the time out to assist me, I truly appreciate it. I will try an upgrade next week and pray it all goes well :-) On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" wrote: > > > On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler > wrote: > >> Sandro - >> >> Do you have available documentation that can support upgrading self >> hosted? I followed this >> http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ >> >> Would it be as easy as installing the RPM and then running yum >> upgrade? >> >> > Note that mentioned article describes an unsupported hyperconverged > setup running NFS over Gluster. > That said, > 1) put the hosted-engine storage domain into global maintenance mode > 2) upgrade the engine VM > 3) select the first host to upgrade and put it under maintenance from > the engine, wait for the engine vm to migrate if needed. > 4) yum upgrade the first host and wait until ovirt-ha-agent completes > 5) exit global and local maintenance mode > 6) repeat 3-5 on all the other hosts > 7) once all hosts are updated you can increase the cluster > compatibility level to 3.6. At this point the engine will trigger the > auto-import of the hosted-engine storage domain. > > Simone, Roy, can you confir
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
So what about the bug that I hit for vdsm as listed above by Nir? Will I have that patch to avoid the memory leak or no? Upgrading an entire node to centos 7 is not actually feasible and was previously outlined above that I just needed to upgrade to ovirt 3.6 and no mention of OS change ... On Feb 1, 2016 12:30 PM, "Simone Tiraboschi" wrote: > > > On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler > wrote: > >> Sandro / Nir - >> >> I followed your steps plus >> >> http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL >> >> Engine upgraded fine but then when I got to upgrading a node I did: >> >> $ yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm >> $ yum update -y >> >> And then rebooted the node. I noticed libvirt was updated by a .1 release >> number but vdsm (where the memory leak issue I thought was?) was not >> upgraded. In fact, very little of ovirt packages on the node were >> noticeably not updated >> >> > We are not building vdsm for el6 in 3.6, you need also to upgrade to el7 > if you want that. > > >> Updated node received the following updated packages during the install: >> >> http://pastebin.ca/3362714 >> >> Note specifically the only packages updated via the ovirt3.6 repository >> was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, >> ovirt-release36, and python-ioprocess. I had expected to see some packages >> like vdsm and the likes updated - or was this not the case? >> >> Upgraded node: >> >> [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm >> vdsm-4.16.30-0.el6.x86_64 >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >> vdsm-cli-4.16.30-0.el6.noarch >> vdsm-yajsonrpc-4.16.30-0.el6.noarch >> vdsm-jsonrpc-4.16.30-0.el6.noarch >> vdsm-xmlrpc-4.16.30-0.el6.noarch >> vdsm-python-4.16.30-0.el6.noarch >> >> Nonupgraded node >> >> [compute[root@node01 ~]$ rpm -qa | grep -i vdsm >> vdsm-cli-4.16.30-0.el6.noarch >> vdsm-jsonrpc-4.16.30-0.el6.noarch >> vdsm-python-zombiereaper-4.16.30-0.el6.noarch >> vdsm-xmlrpc-4.16.30-0.el6.noarch >> vdsm-yajsonrpc-4.16.30-0.el6.noarch >> vdsm-4.16.30-0.el6.x86_64 >> vdsm-python-4.16.30-0.el6.noarch >> >> Also, the docs stated that the engine VM would migrate to the freshly >> upgraded node since it would have a higher number but it did not >> >> So I cant really confirm whether or not my issue will be resolved? Or >> that if the node was actually updated properly? >> >> Please advise on how to confirm >> >> Thank you! >> >> On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler >> wrote: >> >>> Thanks Sandro. Should clarify my storage is external on a redundant SAN. >>> The steps I was concerned about was the actual upgrade. I tried to upgrade >>> before and it brought my entire stack crumbling down so I'm hesitant. This >>> bug seems like a huge bug that should at least somehow backported if at all >>> possible because, to me, it renders the entire 3.5.6 branch unusable as no >>> VMs can be deployed since OOM will eventually kill them. In any case that's >>> just my opinion and I'm a new user to ovirt. The docs I followed originally >>> got me going how I need and somehow didn't work for 3.6 in the same fashion >>> so naturally I'm hesitant to upgrade but clearly have no option if I want >>> to continue my infrastructure on ovirt. Thank you again for taking the time >>> out to assist me, I truly appreciate it. I will try an upgrade next week >>> and pray it all goes well :-) >>> On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" >>> wrote: >>> On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler wrote: > Sandro - > > Do you have available documentation that can support upgrading self > hosted? I followed this > http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ > > Would it be as easy as installing the RPM and then running yum upgrade? > > Note that mentioned article describes an unsupported hyperconverged setup running NFS over Gluster. That said, 1) put the hosted-engine storage domain into global maintenance mode 2) upgrade the engine VM 3) select the first host to upgrade and put it under maintenance from the engine, wait for the engine vm to migrate if needed. 4) yum upgrade the first host and wait until ovirt-ha-agent completes 5) exit global and local maintenance mode 6) repeat 3-5 on all the other hosts 7) once all hosts are updated you can increase the cluster compatibility level to 3.6. At this point the engine will trigger the auto-import of the hosted-engine storage domain. Simone, Roy, can you confirm above steps? Maybe also you can update http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine > Thanks > > On Fri, Jan 22, 2016 at 4:42 PM, Sandro Bonazzola > wrote: > >> >> Il 22/Gen/2016 22:31, "Charles Kozler" ha >> scritto: >> > >> > Hi Nir - >> > >> > do you have a r
Re: [ovirt-users] Debian porting
I take a time for analyzing all that was told, I think I can't say anything before my first try running it on debian. Maybe I do it on weekend but I'll pay attention about everything had been said. On Mon, Feb 1, 2016 at 10:09 AM, Milan Zamazal wrote: > Nir Soffer writes: > > > If you must avoid /rhev/data-center, move it to /run/vdsm/data-center, > > but note that future version of vdsm may move it to /run/vdsm/storage, > > or another location, so old debain code will not be compatible with > > new debian code :-) > > > > It would be easier to support vdsm if the runtime configuration is the > > same on all platforms. > > Thank you for explanation of the issue. I think we can go with > /run/vdsm/data-center for now. There's no hurry about final decision, > it would be nice to have the upstream decision about the future location > before the next Debian freeze, which is going to happen sometimes in > fall. > -- contatos: Celular: ( 99 ) 99143-5954 - Vivo skype: lucasd3castro ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
On Mon, Feb 1, 2016 at 5:40 PM, Charles Kozler wrote: > Sandro / Nir - > > I followed your steps plus > > http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL > > Engine upgraded fine but then when I got to upgrading a node I did: > > $ yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm > $ yum update -y > > And then rebooted the node. I noticed libvirt was updated by a .1 release > number but vdsm (where the memory leak issue I thought was?) was not > upgraded. In fact, very little of ovirt packages on the node were > noticeably not updated > > We are not building vdsm for el6 in 3.6, you need also to upgrade to el7 if you want that. > Updated node received the following updated packages during the install: > > http://pastebin.ca/3362714 > > Note specifically the only packages updated via the ovirt3.6 repository > was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, > ovirt-release36, and python-ioprocess. I had expected to see some packages > like vdsm and the likes updated - or was this not the case? > > Upgraded node: > > [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm > vdsm-4.16.30-0.el6.x86_64 > vdsm-python-zombiereaper-4.16.30-0.el6.noarch > vdsm-cli-4.16.30-0.el6.noarch > vdsm-yajsonrpc-4.16.30-0.el6.noarch > vdsm-jsonrpc-4.16.30-0.el6.noarch > vdsm-xmlrpc-4.16.30-0.el6.noarch > vdsm-python-4.16.30-0.el6.noarch > > Nonupgraded node > > [compute[root@node01 ~]$ rpm -qa | grep -i vdsm > vdsm-cli-4.16.30-0.el6.noarch > vdsm-jsonrpc-4.16.30-0.el6.noarch > vdsm-python-zombiereaper-4.16.30-0.el6.noarch > vdsm-xmlrpc-4.16.30-0.el6.noarch > vdsm-yajsonrpc-4.16.30-0.el6.noarch > vdsm-4.16.30-0.el6.x86_64 > vdsm-python-4.16.30-0.el6.noarch > > Also, the docs stated that the engine VM would migrate to the freshly > upgraded node since it would have a higher number but it did not > > So I cant really confirm whether or not my issue will be resolved? Or that > if the node was actually updated properly? > > Please advise on how to confirm > > Thank you! > > On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler > wrote: > >> Thanks Sandro. Should clarify my storage is external on a redundant SAN. >> The steps I was concerned about was the actual upgrade. I tried to upgrade >> before and it brought my entire stack crumbling down so I'm hesitant. This >> bug seems like a huge bug that should at least somehow backported if at all >> possible because, to me, it renders the entire 3.5.6 branch unusable as no >> VMs can be deployed since OOM will eventually kill them. In any case that's >> just my opinion and I'm a new user to ovirt. The docs I followed originally >> got me going how I need and somehow didn't work for 3.6 in the same fashion >> so naturally I'm hesitant to upgrade but clearly have no option if I want >> to continue my infrastructure on ovirt. Thank you again for taking the time >> out to assist me, I truly appreciate it. I will try an upgrade next week >> and pray it all goes well :-) >> On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" wrote: >> >>> >>> >>> On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler >>> wrote: >>> Sandro - Do you have available documentation that can support upgrading self hosted? I followed this http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ Would it be as easy as installing the RPM and then running yum upgrade? >>> Note that mentioned article describes an unsupported hyperconverged >>> setup running NFS over Gluster. >>> That said, >>> 1) put the hosted-engine storage domain into global maintenance mode >>> 2) upgrade the engine VM >>> 3) select the first host to upgrade and put it under maintenance from >>> the engine, wait for the engine vm to migrate if needed. >>> 4) yum upgrade the first host and wait until ovirt-ha-agent completes >>> 5) exit global and local maintenance mode >>> 6) repeat 3-5 on all the other hosts >>> 7) once all hosts are updated you can increase the cluster compatibility >>> level to 3.6. At this point the engine will trigger the auto-import of the >>> hosted-engine storage domain. >>> >>> Simone, Roy, can you confirm above steps? Maybe also you can update >>> http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine >>> >>> >>> Thanks On Fri, Jan 22, 2016 at 4:42 PM, Sandro Bonazzola wrote: > > Il 22/Gen/2016 22:31, "Charles Kozler" ha > scritto: > > > > Hi Nir - > > > > do you have a release target date for 3.5.8? Any estimate would help. > > > > There won't be any supported release after 3.5.6. Please update to > 3.6.2 next week > > > If its not VDSM, what is it exactly? Sorry, I understood from the > ticket it was something inside vdsm, was I mistaken? > > > > CentOS 6 is the servers. 6.7 to be exact > > > > I have done all forms of flushing that I can (page cache, inodes, > dentry's, etc) and as well moved VM's
Re: [ovirt-users] memory leak in 3.5.6 - not vdsm
Sandro / Nir - I followed your steps plus http://www.ovirt.org/OVirt_3.6_Release_Notes#Fedora_.2F_CentOS_.2F_RHEL Engine upgraded fine but then when I got to upgrading a node I did: $ yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm $ yum update -y And then rebooted the node. I noticed libvirt was updated by a .1 release number but vdsm (where the memory leak issue I thought was?) was not upgraded. In fact, very little of ovirt packages on the node were noticeably not updated Updated node received the following updated packages during the install: http://pastebin.ca/3362714 Note specifically the only packages updated via the ovirt3.6 repository was ioprocess, otopi, ovirt-engine-sdk-python, ovirt-host-deploy, ovirt-release36, and python-ioprocess. I had expected to see some packages like vdsm and the likes updated - or was this not the case? Upgraded node: [compute[root@node02 yum.repos.d]$ rpm -qa | grep -i vdsm vdsm-4.16.30-0.el6.x86_64 vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-cli-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch Nonupgraded node [compute[root@node01 ~]$ rpm -qa | grep -i vdsm vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch vdsm-4.16.30-0.el6.x86_64 vdsm-python-4.16.30-0.el6.noarch Also, the docs stated that the engine VM would migrate to the freshly upgraded node since it would have a higher number but it did not So I cant really confirm whether or not my issue will be resolved? Or that if the node was actually updated properly? Please advise on how to confirm Thank you! On Sat, Jan 23, 2016 at 12:55 AM, Charles Kozler wrote: > Thanks Sandro. Should clarify my storage is external on a redundant SAN. > The steps I was concerned about was the actual upgrade. I tried to upgrade > before and it brought my entire stack crumbling down so I'm hesitant. This > bug seems like a huge bug that should at least somehow backported if at all > possible because, to me, it renders the entire 3.5.6 branch unusable as no > VMs can be deployed since OOM will eventually kill them. In any case that's > just my opinion and I'm a new user to ovirt. The docs I followed originally > got me going how I need and somehow didn't work for 3.6 in the same fashion > so naturally I'm hesitant to upgrade but clearly have no option if I want > to continue my infrastructure on ovirt. Thank you again for taking the time > out to assist me, I truly appreciate it. I will try an upgrade next week > and pray it all goes well :-) > On Jan 23, 2016 12:40 AM, "Sandro Bonazzola" wrote: > >> >> >> On Fri, Jan 22, 2016 at 10:53 PM, Charles Kozler >> wrote: >> >>> Sandro - >>> >>> Do you have available documentation that can support upgrading self >>> hosted? I followed this >>> http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ >>> >>> Would it be as easy as installing the RPM and then running yum upgrade? >>> >>> >> Note that mentioned article describes an unsupported hyperconverged setup >> running NFS over Gluster. >> That said, >> 1) put the hosted-engine storage domain into global maintenance mode >> 2) upgrade the engine VM >> 3) select the first host to upgrade and put it under maintenance from the >> engine, wait for the engine vm to migrate if needed. >> 4) yum upgrade the first host and wait until ovirt-ha-agent completes >> 5) exit global and local maintenance mode >> 6) repeat 3-5 on all the other hosts >> 7) once all hosts are updated you can increase the cluster compatibility >> level to 3.6. At this point the engine will trigger the auto-import of the >> hosted-engine storage domain. >> >> Simone, Roy, can you confirm above steps? Maybe also you can update >> http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine >> >> >> >>> Thanks >>> >>> On Fri, Jan 22, 2016 at 4:42 PM, Sandro Bonazzola >>> wrote: >>> Il 22/Gen/2016 22:31, "Charles Kozler" ha scritto: > > Hi Nir - > > do you have a release target date for 3.5.8? Any estimate would help. > There won't be any supported release after 3.5.6. Please update to 3.6.2 next week > If its not VDSM, what is it exactly? Sorry, I understood from the ticket it was something inside vdsm, was I mistaken? > > CentOS 6 is the servers. 6.7 to be exact > > I have done all forms of flushing that I can (page cache, inodes, dentry's, etc) and as well moved VM's around to other nodes and nothing changes the memory. How can I find the leak? Where is the leak? RES shows the following of which, the totals dont add up to 20GB > >PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND > 19044 qemu 20 0 8876m 4.0g 5680 S 3.6 12
Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup Host Networks"
Hi Christoph, I think that I know what happened on your environment. Since, as you said, the names of the nics were changed after reboot. Nic names that previously were used for sriov nics, are now used for a regular nics. As I see from looking at the results of your queries- Previously - eth2, eth3, eth4 and eth5 were sriov nics. Now after the reboot - eth1, eth3, eth4 and eth6 are sriov nics. Due to a bug (https://bugzilla.redhat.com/1303640), currently the engine doesn't know how to deal with this situation and the data in the db gets corrupted. Until the bug is fixed, the way to fix it manually is to clean the host's data from some tables and then refreshing the capabilities of the host. Please do the following - 1. delete from host_device where host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; 2. delete from host_nic_vfs_config where nic_id in (select id from vds_interface where vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'); After it, please do - 1. select from host_device where host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; 2. select from host_nic_vfs_config where nic_id in (select id from vds_interface where vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'); Make sure both of the queries return empty values. Then click on the 'refresh host's capabilities' button. Please let me know if after doing so you manage to open the host's setup network dialog. Thanks, Alona. - Original Message - > From: ov...@timmi.org > To: "Alona Kaplan" > Cc: "Martin Mucha" , users@ovirt.org > Sent: Sunday, January 31, 2016 4:47:36 PM > Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup Host > Networks" > > Hi Alona, > > please find the requested output in the attachment. > > Best regards > Christoph > > Am 31.01.2016 um 15:09 schrieb Alona Kaplan: > > Hi Christoph, > > > > Please send me also the output of the following- > > > > On the host (The problematic host is - 'lxedna.voipfuture.com', right?)- > > 1. vdsClient -s 0 getVdsCapabilities > > 2. vdsClient -s 0 hostdevListByCaps > > > > On the DB- > > 1. select * from vds_interface where > > vds_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > > 2. select * from host_device where > > host_id='b3b01963-caf8-4f01-bfcc-57e6d33e7dc4'; > > 3. select * from host_nic_vfs_config; > > > > Thanks, > > Alona. > > > > - Original Message - > >> From: ov...@timmi.org > >> To: "Alona Kaplan" , "Martin Mucha" > >> > >> Cc: users@ovirt.org > >> Sent: Friday, January 29, 2016 9:25:53 AM > >> Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup > >> Host Networks" > >> > >> Hi Alona, > >> > >> here are my answers. > >> > >> 1. no, but I did that just now and it does not change the behavior. > >> 2. the host is up > >> 3. it is in the attachment > >> > >> Best regards > >> Christoph > >> > >> Am 28.01.2016 um 15:47 schrieb Alona Kaplan: > >>> Hi Christoph, > >>> > >>> I have some questions/requests- > >>> > >>> 1. After the reboot and the rewiring you did- did you press manually on > >>> the > >>> Host's 'Refresh Capabilities' button (it is part of the Host's actions in > >>> the host's main tab)? > >>> If not, please do it and let me know if after doing it you manage to open > >>> the 'setup networks' dialog or still get the same error. > >>> 2. What is the status of your host? Up/Maintenance/some thing else? > >>> 3. Please attach the full log of your engine. > >>> > >>> Thanks, > >>> Alona. > >>> > >>> - Original Message - > From: "Martin Mucha" > To: ov...@timmi.org > Cc: users@ovirt.org > Sent: Thursday, January 28, 2016 11:46:30 AM > Subject: Re: [ovirt-users] OVirt 3.6.2 -> NPE while clicking on "Setup > Host Networks" > > ok, thanks. Just o inform you — so far it seems there is inconsistency > in > assumptions of what can be nullable and what can not. We just need to > decide > which approach is correct and fix rest. > M. > > - Original Message - > > Hi Martin, > > > > please let me know I can help. > > > > Best regards > > Christoph > > > > Am 28.01.2016 um 09:04 schrieb Martin Mucha: > >> I think this issue is real and it seems to be caused by unboxing of > >> nullvalued integer obtained from function > >> org.ovirt.engine.core.common.businessentities.HostDevice#getTotalVirtualFunctions > >> > >> M. > >> > >> - Original Message - > >>> Hi List, > >>> > >>> I update my OVirt 3.6.1 installation to 3.6.2 this morning. > >>> After the reboot of the server the interface numbering wasn't the > >>> same > >>> so I had to change some cable to have them connected to the right > >>> configuration. > >>> > >>> Everything looks OK but I receive a null pointer exception while > >>> clicking on "Setup Host Networks" of my engine/host server. > >>> > >>> Any help is more then welcome!! > >>> > >>> Best regards >
Re: [ovirt-users] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
Hi again, There is no new memory banks created, example : before adding memory to the Cento7.2 VM I have 4 directories under /sys/devices/system/memory memory0 to memory3 and their status was online. I augmented the memory from 512 to 1024 the were no new memoryX added and I had the error mentioned above: VDSM Noveria command failed: unsupported configuration: unknown device type 'memory' Failed to hot set memory to VM ipaClient. Underlying error message: unsupported configuration: unknown device type 'memory' both for Centos6 and Centos7 I stopped the VM Centos7, I added augmented the memory again, then started the VM, now I have new memoryX directories under /sys/devices/system/memory memory4 to memory7 2016-02-01 15:17 GMT+01:00 Yaniv Dary : > Try: > >1. Look for memory that appears offline. > >Run this command to check the state of the memory: > >grep line /sys/devices/system/memory/*/state > >2. When memory appears offline, run this command to set it to online: > >echo online >/sys/devices/system/memory/memory[number]/state > > > Yaniv Dary > Technical Product Manager > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A, 4th floor > Ra'anana, Israel 4350109 > > Tel : +972 (9) 7692306 > 8272306 > Email: yd...@redhat.com > IRC : ydary > > > On Mon, Feb 1, 2016 at 3:46 PM, wodel youchi > wrote: > >> What do mean? >> I have to use RHEL7? What about Centos7 is this unavailable? >> >> Regards. >> >> 2016-02-01 14:12 GMT+01:00 Yaniv Dary : >> >>> You need to use EL7 guest. >>> >>> Yaniv Dary >>> Technical Product Manager >>> Red Hat Israel Ltd. >>> 34 Jerusalem Road >>> Building A, 4th floor >>> Ra'anana, Israel 4350109 >>> >>> Tel : +972 (9) 7692306 >>> 8272306 >>> Email: yd...@redhat.com >>> IRC : ydary >>> >>> >>> On Mon, Feb 1, 2016 at 1:16 PM, wodel youchi >>> wrote: >>> Hi, I tried with the Centos6x64 VM, I didn't work, in ovirt's webui I have this error : VDSM Noveria command failed: unsupported configuration: unknown device type 'memory' Failed to hot set memory to VM mail10. Underlying error message: unsupported configuration: unknown device type 'memory' Looking into /sys/devices/system/memory there is no new memory banks added. But, I tested with another VM, Centos7x64 which I updated with latest packages : CentOS Linux release 7.2.1511 (Core) I tried to add memory, but I had the same error on ovirt's webui, I did not work neither with el6x64 or el7x64 and /sys/devices/system/memory didn't change, there are no new entries Regards 2016-02-01 10:30 GMT+01:00 Nathanaël Blanchet : > Hi, > > the hot add features starts working out of the box from centos 7.2 > guest. > On previous el7.x, two ways to do that: > > 5.2. How to online memory > > Even if the memory is hot-added, it is not at ready-to-use state. > For using newly added memory, you have to "online" the memory block. > > For onlining, you have to write "online" to the memory block's state > file as: > > % echo online > /sys/devices/system/memory/memoryXXX/state > > or to be active at boot, add this udev rule in > /lib/udev/rules.d/55-ovirt-guest-agent.rules : > > SUBSYSTEM=="memory", ACTION=="add", TEST=="state", > ATTR{state}=="offline", ATTR{state}="online" > > I can't tell you if this works on el6 guest, but why not testing for > us ;) > > Le 01/02/2016 10:04, wodel youchi a écrit : > > Hi, > > I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my > purpose is to test it. > > I am using a simple Desktop : > - one cpu core i5 3550 with 4 cores > - 2x4 Go of RAM > > I installed a Centos 6x64 VM with all updates + ovirt guest agent. > > I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't > work I had to shutdown the VM for the change to take effect. > > Hot plug memory does it have something to do with the underneath > hardware? > or does it depend on the guest OS? > or something else? > > > Regards. > > > ___ > Users mailing > listUsers@ovirt.orghttp://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 14blanc...@abes.fr > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listin
Re: [ovirt-users] Cannot add new host
On Mon, Feb 1, 2016 at 3:30 PM, Marcelo Leandro wrote: > ERROR: on line 27 of config file 'cert.conf' > 139871306037152:error:0E065068:configuration file > routines:STR_COPY:variable has no value:conf_def.c:618:line 27 > Cannot sign certificate > This looks strange; can you please share the content of /etc/pki/ovirt-engine/cert.conf ? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Cannot add new host
Hello, i restored the backup a new server, but i have problem for add a new host. I realized this procedure: http://www.ovirt.org/User:Adrian15/oVirt_engine_migration engine.log: 2016-02-01 11:15:42,218 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-8) Unable to get value of property: vdsName for class org.ovirt.engine.core.common.businessentities.VdsStatic 2016-02-01 11:15:42,229 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-8) Unable to get value of property: vdsName for class org.ovirt.engine.core.common.businessentities.VdsStatic 2016-02-01 11:15:42,236 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (ajp--127.0.0.1-8702-8) [56ddaf28] Running command: InstallVdsCommand internal: false. Entities affected : ID: a5495397-eab7-413e-8d4c-7c5f6518dff7 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN 2016-02-01 11:15:42,254 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-8) Unable to get value of property: vdsName for class org.ovirt.engine.core.common.businessentities.VdsStatic 2016-02-01 11:15:42,260 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-8) Unable to get value of property: vdsName for class org.ovirt.engine.core.common.businessentities.VdsStatic 2016-02-01 11:15:42,270 INFO [org.ovirt.engine.core.bll.InstallVdsInternalCommand] (ajp--127.0.0.1-8702-8) [56ddaf28] Lock Acquired to object EngineLock [exclusiveLocks= key: a5495397-eab7-413e-8d4c-7c5f6518dff7 value: VDS , sharedLocks= ] 2016-02-01 11:15:42,278 INFO [org.ovirt.engine.core.bll.InstallVdsInternalCommand] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Running command: InstallVdsInternalCommand internal: true. Entities affected : ID: a5495397-eab7-413e-8d4c-7c5f6518dff7 Type: VDS 2016-02-01 11:15:42,279 INFO [org.ovirt.engine.core.bll.InstallVdsInternalCommand] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Before Installation host a5495397-eab7-413e-8d4c-7c5f6518dff7, srv-qemu02.hybriddc.com.br 2016-02-01 11:15:42,280 WARN [org.ovirt.engine.core.bll.InstallVdsInternalCommand] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Installation of Host srv-qemu02.hybriddc.com.br will ignore Firewall Override option, since it is not supported for Host type oVirtNode 2016-02-01 11:15:42,283 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] START, SetVdsStatusVDSCommand(HostName = srv-qemu02.hybriddc.com.br, HostId = a5495397-eab7-413e-8d4c-7c5f6518dff7, status=Installing, nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 6b3cfef9 2016-02-01 11:15:42,291 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-8) [56ddaf28] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to verify Power Management configuration for Host srv-qemu02.hybriddc.com.br. 2016-02-01 11:15:42,296 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] FINISH, SetVdsStatusVDSCommand, log id: 6b3cfef9 2016-02-01 11:15:42,330 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-8) [56ddaf28] Correlation ID: 56ddaf28, Call Stack: null, Custom Event ID: -1, Message: Host srv-qemu02.hybriddc.com.br configuration was updated by admin@internal. 2016-02-01 11:15:42,456 INFO [org.ovirt.engine.core.bll.InstallerMessages] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Installation srv-qemu02.hybriddc.com.br: Connected to host srv-qemu02.hybriddc.com.br with SSH key fingerprint: 70:a0:87:eb:25:ac:91:29:f3:ee:a5:a3:a8:48:c5:5c 2016-02-01 11:15:42,472 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Correlation ID: 56ddaf28, Call Stack: null, Custom Event ID: -1, Message: Installing Host srv-qemu02.hybriddc.com.br. Connected to host srv-qemu02.hybriddc.com.br with SSH key fingerprint: 70:a0:87:eb:25:ac:91:29:f3:ee:a5:a3:a8:48:c5:5c. 2016-02-01 11:15:42,536 INFO [org.ovirt.engine.core.bll.VdsDeploy] (org.ovirt.thread.pool-8-thread-16) [56ddaf28] Installation of srv-qemu02.hybriddc.com.br. Executing command via SSH umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/setup DIALOG/dialect=str:machine DIALOG/customization=bool:True < /var/cache/ovirt-engine/ovirt-host-deploy.tar 2016-02-01 11:15:42,537 INFO [org.ovirt.engine.core.utils.archivers.tar.CachedTar] (org.ovirt.thread.pool-8-thread-16) Tarball '/var/cache/ovirt-engine/ovirt-host-deploy.tar' refresh 2016-02-01 11:15:42,573 INFO [org.ovirt.engine.core.uutils.ssh.SSHDialog] (org.ovirt.thread.pool-8-thread-16) SSH execute r...@srv-qemu02.hybriddc.com.br 'umask 0077; MYTMP="$(TMPDIR="${OVIR
Re: [ovirt-users] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
Try: 1. Look for memory that appears offline. Run this command to check the state of the memory: grep line /sys/devices/system/memory/*/state 2. When memory appears offline, run this command to set it to online: echo online >/sys/devices/system/memory/memory[number]/state Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Mon, Feb 1, 2016 at 3:46 PM, wodel youchi wrote: > What do mean? > I have to use RHEL7? What about Centos7 is this unavailable? > > Regards. > > 2016-02-01 14:12 GMT+01:00 Yaniv Dary : > >> You need to use EL7 guest. >> >> Yaniv Dary >> Technical Product Manager >> Red Hat Israel Ltd. >> 34 Jerusalem Road >> Building A, 4th floor >> Ra'anana, Israel 4350109 >> >> Tel : +972 (9) 7692306 >> 8272306 >> Email: yd...@redhat.com >> IRC : ydary >> >> >> On Mon, Feb 1, 2016 at 1:16 PM, wodel youchi >> wrote: >> >>> Hi, >>> >>> I tried with the Centos6x64 VM, I didn't work, in ovirt's webui I have >>> this error : >>> >>> VDSM Noveria command failed: unsupported configuration: unknown device >>> type 'memory' >>> Failed to hot set memory to VM mail10. Underlying error message: >>> unsupported configuration: unknown device type 'memory' >>> >>> Looking into /sys/devices/system/memory there is no new memory banks >>> added. >>> >>> But, I tested with another VM, Centos7x64 which I updated with latest >>> packages : CentOS Linux release 7.2.1511 (Core) >>> >>> I tried to add memory, but I had the same error on ovirt's webui, I did >>> not work neither with el6x64 or el7x64 >>> >>> and /sys/devices/system/memory didn't change, there are no new entries >>> >>> Regards >>> >>> 2016-02-01 10:30 GMT+01:00 Nathanaël Blanchet : >>> Hi, the hot add features starts working out of the box from centos 7.2 guest. On previous el7.x, two ways to do that: 5.2. How to online memory Even if the memory is hot-added, it is not at ready-to-use state. For using newly added memory, you have to "online" the memory block. For onlining, you have to write "online" to the memory block's state file as: % echo online > /sys/devices/system/memory/memoryXXX/state or to be active at boot, add this udev rule in /lib/udev/rules.d/55-ovirt-guest-agent.rules : SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", ATTR{state}="online" I can't tell you if this works on el6 guest, but why not testing for us ;) Le 01/02/2016 10:04, wodel youchi a écrit : Hi, I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose is to test it. I am using a simple Desktop : - one cpu core i5 3550 with 4 cores - 2x4 Go of RAM I installed a Centos 6x64 VM with all updates + ovirt guest agent. I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work I had to shutdown the VM for the change to take effect. Hot plug memory does it have something to do with the underneath hardware? or does it depend on the guest OS? or something else? Regards. ___ Users mailing listUsers@ovirt.orghttp://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 14blanc...@abes.fr ___ 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] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
What do mean? I have to use RHEL7? What about Centos7 is this unavailable? Regards. 2016-02-01 14:12 GMT+01:00 Yaniv Dary : > You need to use EL7 guest. > > Yaniv Dary > Technical Product Manager > Red Hat Israel Ltd. > 34 Jerusalem Road > Building A, 4th floor > Ra'anana, Israel 4350109 > > Tel : +972 (9) 7692306 > 8272306 > Email: yd...@redhat.com > IRC : ydary > > > On Mon, Feb 1, 2016 at 1:16 PM, wodel youchi > wrote: > >> Hi, >> >> I tried with the Centos6x64 VM, I didn't work, in ovirt's webui I have >> this error : >> >> VDSM Noveria command failed: unsupported configuration: unknown device >> type 'memory' >> Failed to hot set memory to VM mail10. Underlying error message: >> unsupported configuration: unknown device type 'memory' >> >> Looking into /sys/devices/system/memory there is no new memory banks >> added. >> >> But, I tested with another VM, Centos7x64 which I updated with latest >> packages : CentOS Linux release 7.2.1511 (Core) >> >> I tried to add memory, but I had the same error on ovirt's webui, I did >> not work neither with el6x64 or el7x64 >> >> and /sys/devices/system/memory didn't change, there are no new entries >> >> Regards >> >> 2016-02-01 10:30 GMT+01:00 Nathanaël Blanchet : >> >>> Hi, >>> >>> the hot add features starts working out of the box from centos 7.2 guest. >>> On previous el7.x, two ways to do that: >>> >>> 5.2. How to online memory >>> >>> Even if the memory is hot-added, it is not at ready-to-use state. >>> For using newly added memory, you have to "online" the memory block. >>> >>> For onlining, you have to write "online" to the memory block's state >>> file as: >>> >>> % echo online > /sys/devices/system/memory/memoryXXX/state >>> >>> or to be active at boot, add this udev rule in >>> /lib/udev/rules.d/55-ovirt-guest-agent.rules : >>> >>> SUBSYSTEM=="memory", ACTION=="add", TEST=="state", >>> ATTR{state}=="offline", ATTR{state}="online" >>> >>> I can't tell you if this works on el6 guest, but why not testing for us >>> ;) >>> >>> Le 01/02/2016 10:04, wodel youchi a écrit : >>> >>> Hi, >>> >>> I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose >>> is to test it. >>> >>> I am using a simple Desktop : >>> - one cpu core i5 3550 with 4 cores >>> - 2x4 Go of RAM >>> >>> I installed a Centos 6x64 VM with all updates + ovirt guest agent. >>> >>> I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work >>> I had to shutdown the VM for the change to take effect. >>> >>> Hot plug memory does it have something to do with the underneath >>> hardware? >>> or does it depend on the guest OS? >>> or something else? >>> >>> >>> Regards. >>> >>> >>> ___ >>> Users mailing >>> listUsers@ovirt.orghttp://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 14blanc...@abes.fr >>> >>> >>> ___ >>> 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] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
You need to use EL7 guest. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Mon, Feb 1, 2016 at 1:16 PM, wodel youchi wrote: > Hi, > > I tried with the Centos6x64 VM, I didn't work, in ovirt's webui I have > this error : > > VDSM Noveria command failed: unsupported configuration: unknown device > type 'memory' > Failed to hot set memory to VM mail10. Underlying error message: > unsupported configuration: unknown device type 'memory' > > Looking into /sys/devices/system/memory there is no new memory banks added. > > But, I tested with another VM, Centos7x64 which I updated with latest > packages : CentOS Linux release 7.2.1511 (Core) > > I tried to add memory, but I had the same error on ovirt's webui, I did > not work neither with el6x64 or el7x64 > > and /sys/devices/system/memory didn't change, there are no new entries > > Regards > > 2016-02-01 10:30 GMT+01:00 Nathanaël Blanchet : > >> Hi, >> >> the hot add features starts working out of the box from centos 7.2 guest. >> On previous el7.x, two ways to do that: >> >> 5.2. How to online memory >> >> Even if the memory is hot-added, it is not at ready-to-use state. >> For using newly added memory, you have to "online" the memory block. >> >> For onlining, you have to write "online" to the memory block's state file >> as: >> >> % echo online > /sys/devices/system/memory/memoryXXX/state >> >> or to be active at boot, add this udev rule in >> /lib/udev/rules.d/55-ovirt-guest-agent.rules : >> >> SUBSYSTEM=="memory", ACTION=="add", TEST=="state", >> ATTR{state}=="offline", ATTR{state}="online" >> >> I can't tell you if this works on el6 guest, but why not testing for us ;) >> >> Le 01/02/2016 10:04, wodel youchi a écrit : >> >> Hi, >> >> I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose >> is to test it. >> >> I am using a simple Desktop : >> - one cpu core i5 3550 with 4 cores >> - 2x4 Go of RAM >> >> I installed a Centos 6x64 VM with all updates + ovirt guest agent. >> >> I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work I >> had to shutdown the VM for the change to take effect. >> >> Hot plug memory does it have something to do with the underneath hardware? >> or does it depend on the guest OS? >> or something else? >> >> >> Regards. >> >> >> ___ >> Users mailing >> listUsers@ovirt.orghttp://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 14blanc...@abes.fr >> >> >> ___ >> 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] Debian porting
Nir Soffer writes: > If you must avoid /rhev/data-center, move it to /run/vdsm/data-center, > but note that future version of vdsm may move it to /run/vdsm/storage, > or another location, so old debain code will not be compatible with > new debian code :-) > > It would be easier to support vdsm if the runtime configuration is the > same on all platforms. Thank you for explanation of the issue. I think we can go with /run/vdsm/data-center for now. There's no hurry about final decision, it would be nice to have the upstream decision about the future location before the next Debian freeze, which is going to happen sometimes in fall. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
Hi, I tried with the Centos6x64 VM, I didn't work, in ovirt's webui I have this error : VDSM Noveria command failed: unsupported configuration: unknown device type 'memory' Failed to hot set memory to VM mail10. Underlying error message: unsupported configuration: unknown device type 'memory' Looking into /sys/devices/system/memory there is no new memory banks added. But, I tested with another VM, Centos7x64 which I updated with latest packages : CentOS Linux release 7.2.1511 (Core) I tried to add memory, but I had the same error on ovirt's webui, I did not work neither with el6x64 or el7x64 and /sys/devices/system/memory didn't change, there are no new entries Regards 2016-02-01 10:30 GMT+01:00 Nathanaël Blanchet : > Hi, > > the hot add features starts working out of the box from centos 7.2 guest. > On previous el7.x, two ways to do that: > > 5.2. How to online memory > > Even if the memory is hot-added, it is not at ready-to-use state. > For using newly added memory, you have to "online" the memory block. > > For onlining, you have to write "online" to the memory block's state file > as: > > % echo online > /sys/devices/system/memory/memoryXXX/state > > or to be active at boot, add this udev rule in > /lib/udev/rules.d/55-ovirt-guest-agent.rules : > > SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", > ATTR{state}="online" > > I can't tell you if this works on el6 guest, but why not testing for us ;) > > Le 01/02/2016 10:04, wodel youchi a écrit : > > Hi, > > I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose is > to test it. > > I am using a simple Desktop : > - one cpu core i5 3550 with 4 cores > - 2x4 Go of RAM > > I installed a Centos 6x64 VM with all updates + ovirt guest agent. > > I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work I > had to shutdown the VM for the change to take effect. > > Hot plug memory does it have something to do with the underneath hardware? > or does it depend on the guest OS? > or something else? > > > Regards. > > > ___ > Users mailing listUsers@ovirt.orghttp://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 14blanc...@abes.fr > > > ___ > 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] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
Hi, the hot add features starts working out of the box from centos 7.2 guest. On previous el7.x, two ways to do that: 5.2. How to online memory Even if the memory is hot-added, it is not at ready-to-use state. For using newly added memory, you have to "online" the memory block. For onlining, you have to write "online" to the memory block's state file as: % echo online > /sys/devices/system/memory/memoryXXX/state or to be active at boot, add this udev rule in /lib/udev/rules.d/55-ovirt-guest-agent.rules : SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", ATTR{state}="online" I can't tell you if this works on el6 guest, but why not testing for us ;) Le 01/02/2016 10:04, wodel youchi a écrit : Hi, I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose is to test it. I am using a simple Desktop : - one cpu core i5 3550 with 4 cores - 2x4 Go of RAM I installed a Centos 6x64 VM with all updates + ovirt guest agent. I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work I had to shutdown the VM for the change to take effect. Hot plug memory does it have something to do with the underneath hardware? or does it depend on the guest OS? or something else? Regards. ___ 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] [FC22] testing oVirt 3.6.2 : Hot plug memory not working
Hi, I am using oVirt 3.6.2 on FC22 box, all-in-one installation, my purpose is to test it. I am using a simple Desktop : - one cpu core i5 3550 with 4 cores - 2x4 Go of RAM I installed a Centos 6x64 VM with all updates + ovirt guest agent. I tried to augment the memory from 1024 to 1536 (+512Mo) it didn't work I had to shutdown the VM for the change to take effect. Hot plug memory does it have something to do with the underneath hardware? or does it depend on the guest OS? or something else? Regards. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users