BonsaiJoe
53 Posts
Quote from BonsaiJoe on November 23, 2018, 5:21 pm
Hi,
we try to update one cluster from 2.0 to 2.1 but the upgrade option is grayed out.
after some research we find that it looks like petasan checkes the installed kernel version for enable upgrading option, but cause of we have installed some kernel updates the option is grayed out.
So we removed linux-image-4.4.126-03-petasan, linux-image-4.4.126-04-petasan , linux-image-4.12.14-02-petasan and installed again the oldest version linux-image-4.4.92-09-petasan again but still no sucess.
the installer did a dpkg -l | grep petasan | grep -Ev "(config|stats)" | tr -s ' ' | cut -d ' ' -f3 for checking the installed kernel versions
this results in our case after deleting the newer kernels is:
4.4.92-09-petasan
2.0.0
20180416
any idea how to get this fixed for update 2.0 to 2.1?
thanks
Hi,
we try to update one cluster from 2.0 to 2.1 but the upgrade option is grayed out.
after some research we find that it looks like petasan checkes the installed kernel version for enable upgrading option, but cause of we have installed some kernel updates the option is grayed out.
So we removed linux-image-4.4.126-03-petasan, linux-image-4.4.126-04-petasan , linux-image-4.12.14-02-petasan and installed again the oldest version linux-image-4.4.92-09-petasan again but still no sucess.
the installer did a dpkg -l | grep petasan | grep -Ev "(config|stats)" | tr -s ' ' | cut -d ' ' -f3 for checking the installed kernel versions
this results in our case after deleting the newer kernels is:
4.4.92-09-petasan
2.0.0
20180416
any idea how to get this fixed for update 2.0 to 2.1?
thanks
admin
2,930 Posts
Quote from admin on November 26, 2018, 10:59 am
You are correct, the manual updates did hinder the auto update functions. I will log this as a bug for next release. I cannot think of an easy way to fix this one now.
You are correct, the manual updates did hinder the auto update functions. I will log this as a bug for next release. I cannot think of an easy way to fix this one now.
BonsaiJoe
53 Posts
Quote from BonsaiJoe on November 26, 2018, 3:23 pm
may do you have a bit more compley way to get this fixed 😉 cause as far as i can see we need to upgrade from 2.0 to 2.1 before we can upgrade to 2.2 so we need to find a soultion to get this cluster updated.
as far as i know the kernel that was by default installed was 4.4.92-09-petasan right ? so we are back to this kernel the only other update what is still installed is this petasan-firmware package
ii petasan-firmware 20180416 amd64 PetaSAN Linux kernel firmware
can we remove this without any problems when we are back from kernel 4.12.x to 4.4.x ? and does this may blocks the upgrade process ?
or you have more information what the installer exactly checks to alow the upgrade ?
thanks for your help
may do you have a bit more compley way to get this fixed 😉 cause as far as i can see we need to upgrade from 2.0 to 2.1 before we can upgrade to 2.2 so we need to find a soultion to get this cluster updated.
as far as i know the kernel that was by default installed was 4.4.92-09-petasan right ? so we are back to this kernel the only other update what is still installed is this petasan-firmware package
ii petasan-firmware 20180416 amd64 PetaSAN Linux kernel firmware
can we remove this without any problems when we are back from kernel 4.12.x to 4.4.x ? and does this may blocks the upgrade process ?
or you have more information what the installer exactly checks to alow the upgrade ?
thanks for your help
admin
2,930 Posts
Quote from admin on November 27, 2018, 10:09 am
Not something i can say that will work without looking into it. Give me a couple of days since it is busy now and i will try to find something, probably to upgrade directly to 2,2. i will let you know.
Not something i can say that will work without looking into it. Give me a couple of days since it is busy now and i will try to find something, probably to upgrade directly to 2,2. i will let you know.
protocol6v
85 Posts
Quote from protocol6v on December 5, 2018, 1:08 pm
I need help with this as well. Installed one of your custom kernels to take care of hotswap issues with LSI 9211-8i a while back, and this is preventing me from upgrading to 2.1 (And as a result, 2.2). This is a fairly large cluster with a decent workload that I really can't move off to do a full re-image, so really need a fix for this.
Thanks!
I need help with this as well. Installed one of your custom kernels to take care of hotswap issues with LSI 9211-8i a while back, and this is preventing me from upgrading to 2.1 (And as a result, 2.2). This is a fairly large cluster with a decent workload that I really can't move off to do a full re-image, so really need a fix for this.
Thanks!
admin
2,930 Posts
Quote from admin on December 6, 2018, 6:25 am
yes the manual updates did screw up the auto installer. It will be corrected soon, i need a couple of more days as we are working on the 2.3 release. This update will not be an official release and will be go through our full test cycle. It will support upgrading from both 2.0 and 2.1 to 2.2.
yes the manual updates did screw up the auto installer. It will be corrected soon, i need a couple of more days as we are working on the 2.3 release. This update will not be an official release and will be go through our full test cycle. It will support upgrading from both 2.0 and 2.1 to 2.2.
protocol6v
85 Posts
Quote from protocol6v on December 6, 2018, 5:40 pm
Just to clarify, are you going to build us an unofficial 2.2 installer? Or are we just waiting for 2.3 and upgrading directly? I wouldn't mind the latter, as long as the release is coming soon.
As usual though, keep up the good work!
Just to clarify, are you going to build us an unofficial 2.2 installer? Or are we just waiting for 2.3 and upgrading directly? I wouldn't mind the latter, as long as the release is coming soon.
As usual though, keep up the good work!
admin
2,930 Posts
Quote from admin on December 10, 2018, 3:57 pm
This 2.2 installer fixes the issue if you had done kernel upgrade manually. Also upgrades from 2.0/2.1
https://drive.google.com/file/d/1rZgpB7OGvGWQkhC780MGAbGb1VU8ioi8/view?usp=sharing
This 2.2 installer fixes the issue if you had done kernel upgrade manually. Also upgrades from 2.0/2.1
https://drive.google.com/file/d/1rZgpB7OGvGWQkhC780MGAbGb1VU8ioi8/view?usp=sharing
protocol6v
85 Posts
Quote from protocol6v on January 15, 2019, 2:52 pm
The custom upgrader worked perfectly, thank you.
The custom upgrader worked perfectly, thank you.
