Hi Guru, Thanks. Please see inline,
1. > The difference is usually the options provided to ./configure. When you > install OVS via 'yum install' or 'apt-get install', etc the configure options > are usually: > ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc > --enable-ssl Aaah, ok. If my memory serves me right, then I used ./configure --with-linux=/lib/modules/`uname -r`/build Is this where the problem lies in? 2. > But if you follow INSTALL.md, it asks you to choose how you want to configure > it, but many people doing it as a one off thing, ignore the subtleties > involved. Yeah, Likely. Could you please point out what ./configure option I should have used while upgrading? I wish the section about upgrading in INSTALL.md spelled out the subtleties involved (with ./configure options etc.) in step 2 versus just "Install the new Open vSwitch release." 3. Also, are there any particular steps to remove the previous OVS version (once upgrade succeeded) ? Cheers, Rajiv > On Mar 29, 2016, at 12:01 PM, Guru Shetty <g...@ovn.org> wrote: > > > >> On 28 March 2016 at 18:42, Richa <ric...@nc.rr.com> wrote: >> Hi Guru, >> >> Thanks for quick reply. Yes, you guessed it right - I do have ovs2.4.0 and >> 2.5.0. >> >> I expected new version to take over, as I followed the "upgrading" steps >> described here - >> >> https://github.com/openvswitch/ovs/blob/master/INSTALL.md >> >> I guess I must have missed something in those steps. > The difference is usually the options provided to ./configure. When you > install OVS via 'yum install' or 'apt-get install', etc the configure options > are usually: > ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc > --enable-ssl > > But if you follow INSTALL.md, it asks you to choose how you want to configure > it, but many people doing it as a one off thing, ignore the subtleties > involved. > > > >> Cheers, >> R >> >>> On Mar 28, 2016, at 1:46 PM, Guru Shetty <g...@ovn.org> wrote: >>> >>> >>> >>>> On 27 March 2016 at 21:52, Richa <ric...@nc.rr.com> wrote: >>>> >>>> I upgraded OVS from 2.4.0 to 2.5.0 following the FAQ, but ended up with >>>> this confusing state. Is it a bug or installation issue? >>>> >>>> Would appreciate any help. >>>> >>>> >>>> RI@NRVPerf:~$ sudo ovs-vsctl show | grep version >>>> ovs_version: "2.4.0" >>>> RI@NRVPerf:~$ >>>> RI@NRVPerf:~$ ovs-vsctl --version >>>> ovs-vsctl (Open vSwitch) 2.5.0 >>>> Compiled Mar 26 2016 04:33:59 >>>> DB Schema 7.12.1 >>>> RI@NRVPerf:~$ >>> >>> You are running one command as 'sudo' and another without it. So my >>> educated guess is that you have 2 different version of ovs installed on the >>> same machine. >>> >>> What does find / -name ovs-vsctl say? Does it give 2 copies. If that is the >>> case, you will have to uninstall one of them. >>> >>>> >>>> >>>> Cheers, >>>> R >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@openvswitch.org >>>> http://openvswitch.org/mailman/listinfo/discuss >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss