On Thu, Nov 12, 2015 at 9:03 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl&gt; wrote: > I have finished the upgrade to 3.6. > I received a lot (every 3 seconds ) of the following messages in the > logs after upgrading the hosts: > > vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback > (most recent call last):#012 File > "/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py", line 501, in > _serveRequest#012 res = method(**params)#012 File > "/usr/share/vdsm/rpc/Bridge.py", line 291, in _dynamicMethod#012 return > self._fixupRet(className, methodName, ret)#012 File > "/usr/share/vdsm/rpc/Bridge.py", line 235, in _fixupRet#012 > self._typeFixup('return', retType, result)#012 File > "/usr/share/vdsm/rpc/Bridge.py", line 215, in _typeFixup#012 if k in > item:#012TypeError: argument of type 'NoneType' is not iterable > > I restarted ovirt-ha-agent ovirt-ha-broker and vdsmd. > After I rebooted all hosts ( migrating VMS from one to another ) the > message finally disappeared. > > Then I tried to set compatibility Version to 3.6, but without luck. I > have put hosted engine back in global maintenance, but I can't find out why > it fails. The message says "Error while executing action: Cannot change > Cluster Compatibility Version to higher version when there are active Hosts > with lower version. > -Please move Hosts with lower version to maintenance first." > > I have installed ovirt-release36 on hosted engine and hosts. > I have updated hosted engine with engine-setup. > I ran yum update on all hosts. > What do I need to do to set compatibility version to 3.6? > Please check the software tab in the host panel for each of your host, if the upgrade has been performed you should see something like 'VDSM Version: vdsm-4.17.10.1-0.el7.centos', if vdsm is still at 4.16.z that host is still on 3.5. > And how can I enable repository for hosted engine? ( through WEB UI > change is not saved ). > > > > Best Regards, > Paul Groeneweg > > -- > Met vriendelijke groeten, > > Paul Groeneweg > Pazion > Webdevelopment - Hosting - Apps > > T +31 26 3020038 > M +31 614 277 577 > E paul(a)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(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > --

On Thu, Nov 12, 2015 at 9:52 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl&gt; wrote: > That looks like the issue... > > I am running Centos 6 and I read > https://bugzilla.redhat.com/show_bug.cgi?id=1206231 > Is it possible to build the packages form source or is my only option > upgrading to Centos7? > 3.6 compatibility level requires el7 hosts; we didn't built vdsm for el6 and I don't think it will just about rebuild. So you can upgrade your hosts to el7 to gain the new 3.6 features or you can remain at 3.5 compatibility level. > > Can I have a mix of Centos 6 and 7 in my DC/Cluster? ( otherwise I need > to upgrade/migrate all VMS? ) > The point is not about upgrading your VMs but about your hosts. You'll cluster could not be upgrade to 3.6 level till you have one active host with vdsm 4.16.z > > Met vriendelijke groeten, > Paul Groeneweg > > > Op do 12 nov. 2015 om 09:38 schreef Simone Tiraboschi < > stirabos(a)redhat.com&gt;: > >> On Thu, Nov 12, 2015 at 9:03 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl >> > wrote: >> >>> I have finished the upgrade to 3.6. >>> I received a lot (every 3 seconds ) of the following messages in the >>> logs after upgrading the hosts: >>> >>> vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback >>> (most recent call last):#012 File >>> "/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py", line 501, in >>> _serveRequest#012 res = method(**params)#012 File >>> "/usr/share/vdsm/rpc/Bridge.py", line 291, in _dynamicMethod#012 return >>> self._fixupRet(className, methodName, ret)#012 File >>> "/usr/share/vdsm/rpc/Bridge.py", line 235, in _fixupRet#012 >>> self._typeFixup('return', retType, result)#012 File >>> "/usr/share/vdsm/rpc/Bridge.py", line 215, in _typeFixup#012 if k in >>> item:#012TypeError: argument of type 'NoneType' is not iterable >>> >>> I restarted ovirt-ha-agent ovirt-ha-broker and vdsmd. >>> After I rebooted all hosts ( migrating VMS from one to another ) the >>> message finally disappeared. >>> >>> Then I tried to set compatibility Version to 3.6, but without luck. I >>> have put hosted engine back in global maintenance, but I can't find out why >>> it fails. The message says "Error while executing action: Cannot change >>> Cluster Compatibility Version to higher version when there are active Hosts >>> with lower version. >>> -Please move Hosts with lower version to maintenance first." >>> >>> I have installed ovirt-release36 on hosted engine and hosts. >>> I have updated hosted engine with engine-setup. >>> I ran yum update on all hosts. >>> What do I need to do to set compatibility version to 3.6? >>> >> >> Please check the software tab in the host panel for each of your host, >> if the upgrade has been performed you should see something like 'VDSM >> Version: vdsm-4.17.10.1-0.el7.centos', if vdsm is still at 4.16.z that host >> is still on 3.5. >> >> >>> And how can I enable repository for hosted engine? ( through WEB UI >>> change is not saved ). >>> >>> >>> >>> Best Regards, >>> Paul Groeneweg >>> >>> -- >>> Met vriendelijke groeten, >>> >>> Paul Groeneweg >>> Pazion >>> Webdevelopment - Hosting - Apps >>> >>> T +31 26 3020038 >>> M +31 614 277 577 >>> E paul(a)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(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> -- > Met vriendelijke groeten, > > Paul Groeneweg > Pazion > Webdevelopment - Hosting - Apps > > T +31 26 3020038 > M +31 614 277 577 > E paul(a)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." > --

On Thu, Nov 12, 2015 at 10:40 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl&gt; wrote: > OK, I understand, I would need to upgrade my Hosts to go to 3.6. > > I think I read somewhere I can't mix EL6 and EL7 hosts in the same > cluster, is this true? > > You can have a mix of EL6 and EL7 hosts with 3.5 cluster compatibility in place. But you have to notice that you can do live migrations in direction EL6 --> EL7 but not the reverse. SO you have to care about this for your migration strategy. Probably bettere to update at least two hosts to EL7 before beginning to place critical VMs on them. HIH, Gianluca

On Thu, Nov 12, 2015 at 10:44 AM, Gianluca Cecchi < gianluca.cecchi(a)gmail.com&gt; wrote: > On Thu, Nov 12, 2015 at 10:40 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl > > wrote: > >> OK, I understand, I would need to upgrade my Hosts to go to 3.6. >> >> I think I read somewhere I can't mix EL6 and EL7 hosts in the same >> cluster, is this true? >> >> > You can have a mix of EL6 and EL7 hosts with 3.5 cluster compatibility in > place. > But you have to notice that you can do live migrations in direction EL6 > --> EL7 but not the reverse. > SO you have to care about this for your migration strategy. > Probably bettere to update at least two hosts to EL7 before beginning to > place critical VMs on them. > HIH, > Gianluca > Opsss, perhaps I'm wro and you have to create a different cluster in the same datacenter and progressively migrate VMs from hosts in first cluster to hosts in second cluster. At least so it was in 3.5.1.... did it change? See http://lists.ovirt.org/pipermail/users/2015-May/032818.html and bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1150191

On Thu, Nov 12, 2015 at 10:52 AM, Paul Groeneweg | Pazion <paul(a)pazion.nl&gt; wrote: > Hmm, that would be a pity, then I also need a second shared storage. > > Anyone tested mixed el6 and el7 cluster on 3.5.5 or 3.6 ? > > > Actually you attach a storage domain to a Data Center object, not to a Cluster object. I hope that two different clusters inside the same datacenter can consume the same storage domains concurrently, isn't it? Gianluca

I have finished the upgrade to 3.6.

I received a lot (every 3 seconds ) of the following messages in the logs after upgrading the hosts: vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback (most recent call last):#012 File "/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py", line 501, in _serveRequest#012 res = method(**params)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 291, in _dynamicMethod#012 return self._fixupRet(className, methodName, ret)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 235, in _fixupRet#012 self._typeFixup('return', retType, result)#012 File "/usr/share/vdsm/rpc/Bridge.py", line 215, in _typeFixup#012 if k in item:#012TypeError: argument of type 'NoneType' is not iterable I restarted ovirt-ha-agent ovirt-ha-broker and vdsmd. After I rebooted all hosts ( migrating VMS from one to another ) the message finally disappeared.

Then I tried to set compatibility Version to 3.6, but without luck. I have put hosted engine back in global maintenance, but I can't find out why it fails. The message says "Error while executing action: Cannot change Cluster Compatibility Version to higher version when there are active Hosts with lower version. -Please move Hosts with lower version to maintenance first."

I have installed ovirt-release36 on hosted engine and hosts. I have updated hosted engine with engine-setup. I ran yum update on all hosts. What do I need to do to set compatibility version to 3.6? And how can I enable repository for hosted engine? ( through WEB UI change is not saved ).

--