Wireless Access

Reply
New Contributor

upgrade to 8.2.3 failed

has anyone upgraded to 8.2.3? 

our upgrade failed (from version 8.2.2.1) - we have done this multiple times in the past almost everytime without any problem.. 

(tried both ways download the tar file and put it in the root folder and also let airwave download) 

diskspace is sufficient (was a problem on a previous upgrade so we remove all unnecessary old images befor upgrading) 

 

STEP 1: Moving old version aside.

STEP 2: Unpacking upgrade package.
Error: Unpacking upgrade package failed.
Restoring previous version...
Use of uninitialized value $new_repo in concatenation (.) or string at /root/AMP-8.2.3-amp_upgrade line 738, <STDIN> line 1.
Use of uninitialized value $new_repo in concatenation (.) or string at /root/AMP-8.2.3-amp_upgrade line 739, <STDIN> line 1.
Use of uninitialized value $new_repo in concatenation (.) or string at /root/AMP-8.2.3-amp_upgrade line 740, <STDIN> line 1.
Use of uninitialized value $new_repo in concatenation (.) or string at /root/AMP-8.2.3-amp_upgrade line 740, <STDIN> line 1.
/bin/mv: cannot move `/root/' to a subdirectory of itself, `/root/_new'
Use of uninitialized value $new_repo in concatenation (.) or string at /root/AMP-8.2.3-amp_upgrade line 748, <STDIN> line 1.
Previous version restored.
git/mercury/scripts/nightly_backup
git/mercury/Makefile.dev
git/mercury/version.txt
svn/mercury/
/bin/tar: svn/mercury: Cannot mkdir: No such file or directory
svn/mercury/scripts/
/bin/tar: svn/mercury/scripts: Cannot mkdir: No such file or directory
svn/mercury/scripts/amp_upgrade
/bin/tar: svn/mercury/scripts/amp_upgrade: Cannot open: No such file or directory
/bin/tar: Exiting with failure status due to previous errors

Guru Elite

Re: upgrade to 8.2.3 failed

Did you check the MD5 of that file after you downloaded it?


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor

Re: upgrade to 8.2.3 failed

hi colin 

 

yes we did check md5 it matches

best

marko 

 

Guru Elite

Re: upgrade to 8.2.3 failed

If you have not already, please open a TAC case to get that resolved. It could be a specific issue with your setup or configuration...


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor I

Re: upgrade to 8.2.3 failed

Are you doing this from a 172 network by any chance? If so Aruba created a new interface on Airwave 8.2.3. Theres a new interface called “docker0” and has a subnet/route mapped to it. The route tied to it is 172.17.0.0 send out docker0 interface. 

If this is your case down the interface. “ifconfig docker0 down”.

Contributor II

Re: upgrade to 8.2.3 failed

We encounter the same issue upgrading our AMP to 8.2.3 from 8.2.2.1.

 

  • Checked the /root directory and found that we have both SVN and GIT folder present and Airwave was trying to use SVN folder instead of GIT
  • Moved the SVN folder to /tmp directory
  • Went to the path /root/git/mercury and ran make to recompile the script

Please Create a case and escalate to level 3.

 

Steps above Credit to Vishnu Suresh Mannil of Aruba ecalation team 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: