Wireless Access

Reply
MVP

Upgrade path

I've been making my upgrades in lockstep with new releases - usually within hours of the code publication.

 

This time we've had several high-profile projects all at once, and I haven't had time to squeeze in the 7.6.5 to 7.7.0 upgrade.

Now 7.7.1 is out and I'm preparing to upgrade.

 

I'm probably just going to do it in steps with a backup in the middle, but is it OK to go straight from 7.6.5 to 7.7.1?

 

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it

Re: Upgrade path

Yes, upgrade to 7.7.1 should be just fine.

 

Moderator

Re: Upgrade path

You can upgrade directly to 7.7.1 from 7.6.5.  In fact, you should be able to upgrade to 7.7.1 from as far back as 2 full releases (currently meaning 7.5.x) with the only requirement being that the OS needs to be Cent6.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
MVP

Re: Upgrade path

I know I've read that previously -- if fact I may have told someone that -- I've just never tried and suddenly got cold feet.

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
MVP

Re: Upgrade path

Of course I had to open my big mouth!

 

I got my first error on upgrade:

tsdb-server: unrecognized service

Upgrade aborted.
Please contact Aruba Networks Support at
1-800-WiFi-LAN or support@arubanetworks.com
DISABLED - 2!!
svn: The path '/root/svn/mercury' appears to be part of a Subversion 1.7 or greater
working copy.  Please upgrade your Subversion client to use this
working copy.

 On my way to TAC...

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Moderator

Re: Upgrade path

Subversion was upgraded, but that should be a seamless upgrade.  Try running 'svn upgrade' and then after that re-issue the start_amp_upgrade command.  Once the upgrade goes through, you can do 'amp_enable -now'.

 

Make sure you're in /root/svn/mercury when giving the 'svn upgrade' command.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
MVP

Re: Upgrade path

"svn upgrade" is an "Unknown command"

Update perhaps?

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
MVP

Re: Upgrade path

The rest of the original error:

STEP 5: Installing upgrade.
tsdb-server: unrecognized service
	glibc = 2.12-1.80.el6_3.5 is needed by (installed) glibc-devel-2.12-1.80.el6_3.5.x86_64
make[3]: *** [security_patches] Error 4
make[3]: Leaving directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
make[2]: *** [perllib] Error 2
make[2]: Leaving directory `/root/svn/mercury/src'
make[1]: *** [src_install] Error 2
make[1]: Leaving directory `/root/svn/mercury'
make: *** [upgrade] Error 2
make: Leaving directory `/root/svn/mercury'
tsdb-server: unrecognized service

 

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
MVP

Re: Upgrade path

subversion is at 1.6.11

 

did it miss an RPM?

 

[root@airwave mercury]# svn --version
svn, version 1.6.11 (r934486)
   compiled Jun 23 2012, 00:44:03

 

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Moderator

Re: Upgrade path

Looks like it missed a package.

 

This should do the trick

# yum install glibc

 

Then double check to verify the rpm package is there:

# rpm -qa | grep -i glibc


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: