DaleCooper1
1 Copper

Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

Hi,

Im trying to downgrade the firmware on my Isilon cluster from 7.0.2.4 to 7.0.2.1.

I get the following error

/var/log/upgrade.log

update_engine_2013-10-23_21:34:11.txt

2013-10-23 21:34:13,282 INFO Update engine starts.

2013-10-23 21:34:29,554 INFO Got new version from source: 7.0.2.1 B_7_0_2_123(RELEASE) (0x70002500010007b)

2013-10-23 21:34:29,667 INFO Loading from cluster

2013-10-23 21:34:29,668 INFO Loading image finishes:localhost

2013-10-23 21:34:42,813 WARNING Abort from previous error. Update failed.

2013-10-23 21:34:42,814 INFO Update engine finishes.

2013-10-23 21:34:44,819 DEBUG Executing: /usr/bin/pkill -KILL -g 59736

2013-10-23 21:34:44,826 ERROR /usr/bin/pkill -KILL -g 59736[signaled:1 ]:

2013-10-23 21:34:44,827 ERROR Failed to run:/usr/bin/pkill -KILL -g 59736

First, is it possible to downgrade firmeare?

2nd is there somewhere I can get a more detailed error?

Thanks

Jim

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
christopher_ime
4 Beryllium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

If you are looking to preserve the data and configuration, then no there isn't a way to downgrade the cluster.  Also just to mention it for anyone that might be interested, there isn't any way to roll-back an upgrade either.

Any procedure to downgrade the cluster would be destructive as it basically requires reimaging the nodes.  The easiest way since the cluster is built already would be to upload the image file (.img) then kick off the reimage via the isi_reimage command.  This is the best argument for why you would decide to use isi_reimage over doing so individually via a USB thumb drive.  Then once finished, connect a null modem cable to the serial port of the first node and you'll be presented with the familiar initial setup menu and then you can rebuild the cluster.

0 Kudos
7 Replies
Highlighted
christopher_ime
4 Beryllium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

If you are looking to preserve the data and configuration, then no there isn't a way to downgrade the cluster.  Also just to mention it for anyone that might be interested, there isn't any way to roll-back an upgrade either.

Any procedure to downgrade the cluster would be destructive as it basically requires reimaging the nodes.  The easiest way since the cluster is built already would be to upload the image file (.img) then kick off the reimage via the isi_reimage command.  This is the best argument for why you would decide to use isi_reimage over doing so individually via a USB thumb drive.  Then once finished, connect a null modem cable to the serial port of the first node and you'll be presented with the familiar initial setup menu and then you can rebuild the cluster.

0 Kudos
Peter_Sero
4 Tellurium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

Jim, what is the issue with 7.0.2.4 on your cluster?

Thanks

-- Peter

0 Kudos
DaleCooper1
1 Copper

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

We were trying to use it with Vipr, and found and confirmed  that 7.0.2.4 has discovery issues. We were going to try and back rev it but now will put that on hold.

0 Kudos
Peter_Sero
4 Tellurium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

Thanks -- I assume "discovery" means on the control plane?

Where did you expect major benefits using Vipr with Isilon, for data or control?

0 Kudos
DaleCooper1
1 Copper

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

Actually we were going to use Vipr to enable Openstack Cinder and Swift on our Isilon cluster

0 Kudos
Peter_Sero
4 Tellurium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

Sounds great, good luck! Keep us posted on your findings, in particular

in case of creating "many small objects" using Swift...

0 Kudos
christopher_ime
4 Beryllium

Re: Downgrade firmware 7.0.2.4 to 7.0.2.1

Jump to solution

So just curious, did you also get feedback that suggests this won't also be an issue with v7.0.2.1 and was newly introduced after v7.0.2.1?  Just wondering.

0 Kudos