Dependecy of a Package while petasan is upgrading from 2.6.1 to 2.8.1
Pages: 1 2
pradeep suresh
32 Posts
February 23, 2023, 8:14 amQuote from pradeep suresh on February 23, 2023, 8:14 amHello Admin,
While upgrading the petasan version from 2.6.1 to 2.8.1 encoutered this package dependency of grub-efi-amd64-bin where is throws below message
Petasan : Depends : grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed.
I did remove the package and reinstalled it and that dependency is resolved,
But my question is will this have any implications at the reboot. Since it is a package related to the GRUB ???
Thanks in advance.
Hello Admin,
While upgrading the petasan version from 2.6.1 to 2.8.1 encoutered this package dependency of grub-efi-amd64-bin where is throws below message
Petasan : Depends : grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed.
I did remove the package and reinstalled it and that dependency is resolved,
But my question is will this have any implications at the reboot. Since it is a package related to the GRUB ???
Thanks in advance.
admin
2,930 Posts
February 23, 2023, 12:35 pmQuote from admin on February 23, 2023, 12:35 pmHave you installed any additional software manually ?
Have you installed any additional software manually ?
pradeep suresh
32 Posts
February 24, 2023, 10:47 amQuote from pradeep suresh on February 24, 2023, 10:47 amNope, There were no softwares or applications installed manually. The only action i had performed was uncomment these below repository before the starting the upgrade of petasan.
# multiverse universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security multiverse
Thanks in advance.
Nope, There were no softwares or applications installed manually. The only action i had performed was uncomment these below repository before the starting the upgrade of petasan.
# multiverse universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security multiverse
Thanks in advance.
robindewolf
9 Posts
February 24, 2023, 6:53 pmQuote from robindewolf on February 24, 2023, 6:53 pmHello,
We are upgrading from version 2.7.1 to 2.8.x (following the update guide). We encounter the same issue while running the command 'apt install petasan'.
We performed the update on a test cluster first, this before we update our production cluster. We would like to clear this out before we update our production cluster.
Thanks!
root@PETATEST03:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Hit:4 https://archive.petasan.org/repo petasan-v2 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@PETATEST03:~# export DEBIAN_FRONTEND=noninteractive
root@PETATEST03:~# apt -o Dpkg::Options::="--force-confdef" upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
ceph ceph-base ceph-common ceph-mds ceph-mgr ceph-mgr-dashboard ceph-mon ceph-osd ceph-petasan libcephfs2 librados2 libradosstriper1 librbd1 librgw2
petasan-container-images petasan-stats-config python3-ceph-argparse python3-cephfs python3-rados python3-rbd python3-rgw radosgw rbd-mirror
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
root@PETATEST03:~# apt install petasan
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
petasan : Depends: grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed
E: Unable to correct problems, you have held broken packages.
Hello,
We are upgrading from version 2.7.1 to 2.8.x (following the update guide). We encounter the same issue while running the command 'apt install petasan'.
We performed the update on a test cluster first, this before we update our production cluster. We would like to clear this out before we update our production cluster.
Thanks!
root@PETATEST03:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Hit:4 https://archive.petasan.org/repo petasan-v2 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@PETATEST03:~# export DEBIAN_FRONTEND=noninteractive
root@PETATEST03:~# apt -o Dpkg::Options::="--force-confdef" upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
ceph ceph-base ceph-common ceph-mds ceph-mgr ceph-mgr-dashboard ceph-mon ceph-osd ceph-petasan libcephfs2 librados2 libradosstriper1 librbd1 librgw2
petasan-container-images petasan-stats-config python3-ceph-argparse python3-cephfs python3-rados python3-rbd python3-rgw radosgw rbd-mirror
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
root@PETATEST03:~# apt install petasan
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
petasan : Depends: grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed
E: Unable to correct problems, you have held broken packages.
admin
2,930 Posts
February 24, 2023, 9:32 pmQuote from admin on February 24, 2023, 9:32 pmFrom a system that has not upgraded, what is the output of the following:
dpkg -s grub-common | grep Version
apt-cache policy grub-common
apt list --upgradable | grep grub
From a system that has not upgraded, what is the output of the following:
dpkg -s grub-common | grep Version
apt-cache policy grub-common
apt list --upgradable | grep grub
robindewolf
9 Posts
February 24, 2023, 9:44 pmQuote from robindewolf on February 24, 2023, 9:44 pmdpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.18
Version table:
*** 2.02-2ubuntu8.18 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.02-2ubuntu8.17 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.18
Version table:
*** 2.02-2ubuntu8.18 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.02-2ubuntu8.17 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
admin
2,930 Posts
February 24, 2023, 10:01 pmQuote from admin on February 24, 2023, 10:01 pmStrange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Strange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
admin
2,930 Posts
February 24, 2023, 11:04 pmQuote from admin on February 24, 2023, 11:04 pmI installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
I installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
Last edited on February 24, 2023, 11:06 pm by admin · #8
robindewolf
9 Posts
February 25, 2023, 11:58 amQuote from robindewolf on February 25, 2023, 11:58 am
Quote from admin on February 24, 2023, 10:01 pm
Strange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Hi,
enclosed the result after running the apt update:
root@PETATEST02:~# dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
root@PETATEST02:~# apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.25
Version table:
2.02-2ubuntu8.25 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
*** 2.02-2ubuntu8.18 100
100 /var/lib/dpkg/status
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
root@PETATEST02:~# apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-efi-amd64-bin/bionic-updates 2.06-2ubuntu14.1 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc-bin/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
Quote from admin on February 24, 2023, 10:01 pm
Strange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Hi,
enclosed the result after running the apt update:
root@PETATEST02:~# dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
root@PETATEST02:~# apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.25
Version table:
2.02-2ubuntu8.25 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
*** 2.02-2ubuntu8.18 100
100 /var/lib/dpkg/status
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
root@PETATEST02:~# apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-efi-amd64-bin/bionic-updates 2.06-2ubuntu14.1 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc-bin/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
robindewolf
9 Posts
February 25, 2023, 12:12 pmQuote from robindewolf on February 25, 2023, 12:12 pm
Quote from admin on February 24, 2023, 11:04 pm
I installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
Hello,
I can confirm that the following sequence of commands worked for me on the test cluster (starting from version 2.7.1 and updating to 2.8.1).
apt update
apt install ca-certificates
apt update
export DEBIAN_FRONTEND=noninteractive
apt -o Dpkg::Options::="--force-confdef" upgrade
apt install petasan
Thanks for the assistance and the fix!
Quote from admin on February 24, 2023, 11:04 pm
I installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
Hello,
I can confirm that the following sequence of commands worked for me on the test cluster (starting from version 2.7.1 and updating to 2.8.1).
apt update
apt install ca-certificates
apt update
export DEBIAN_FRONTEND=noninteractive
apt -o Dpkg::Options::="--force-confdef" upgrade
apt install petasan
Thanks for the assistance and the fix!
Pages: 1 2
Dependecy of a Package while petasan is upgrading from 2.6.1 to 2.8.1
pradeep suresh
32 Posts
Quote from pradeep suresh on February 23, 2023, 8:14 amHello Admin,
While upgrading the petasan version from 2.6.1 to 2.8.1 encoutered this package dependency of grub-efi-amd64-bin where is throws below message
Petasan : Depends : grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed.
I did remove the package and reinstalled it and that dependency is resolved,But my question is will this have any implications at the reboot. Since it is a package related to the GRUB ???
Thanks in advance.
Hello Admin,
While upgrading the petasan version from 2.6.1 to 2.8.1 encoutered this package dependency of grub-efi-amd64-bin where is throws below message
Petasan : Depends : grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed.
I did remove the package and reinstalled it and that dependency is resolved,
But my question is will this have any implications at the reboot. Since it is a package related to the GRUB ???
Thanks in advance.
admin
2,930 Posts
Quote from admin on February 23, 2023, 12:35 pmHave you installed any additional software manually ?
Have you installed any additional software manually ?
pradeep suresh
32 Posts
Quote from pradeep suresh on February 24, 2023, 10:47 amNope, There were no softwares or applications installed manually. The only action i had performed was uncomment these below repository before the starting the upgrade of petasan.
# multiverse universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security multiverseThanks in advance.
Nope, There were no softwares or applications installed manually. The only action i had performed was uncomment these below repository before the starting the upgrade of petasan.
# multiverse universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-security multiverse
Thanks in advance.
robindewolf
9 Posts
Quote from robindewolf on February 24, 2023, 6:53 pmHello,
We are upgrading from version 2.7.1 to 2.8.x (following the update guide). We encounter the same issue while running the command 'apt install petasan'.
We performed the update on a test cluster first, this before we update our production cluster. We would like to clear this out before we update our production cluster.
Thanks!
root@PETATEST03:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease Hit:4 https://archive.petasan.org/repo petasan-v2 InRelease Reading package lists... Done Building dependency tree Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. root@PETATEST03:~# export DEBIAN_FRONTEND=noninteractive root@PETATEST03:~# apt -o Dpkg::Options::="--force-confdef" upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: ceph ceph-base ceph-common ceph-mds ceph-mgr ceph-mgr-dashboard ceph-mon ceph-osd ceph-petasan libcephfs2 librados2 libradosstriper1 librbd1 librgw2 petasan-container-images petasan-stats-config python3-ceph-argparse python3-cephfs python3-rados python3-rbd python3-rgw radosgw rbd-mirror 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. root@PETATEST03:~# apt install petasan Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: petasan : Depends: grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed E: Unable to correct problems, you have held broken packages.
Hello,
We are upgrading from version 2.7.1 to 2.8.x (following the update guide). We encounter the same issue while running the command 'apt install petasan'.
We performed the update on a test cluster first, this before we update our production cluster. We would like to clear this out before we update our production cluster.
Thanks!
root@PETATEST03:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease Hit:4 https://archive.petasan.org/repo petasan-v2 InRelease Reading package lists... Done Building dependency tree Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. root@PETATEST03:~# export DEBIAN_FRONTEND=noninteractive root@PETATEST03:~# apt -o Dpkg::Options::="--force-confdef" upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: ceph ceph-base ceph-common ceph-mds ceph-mgr ceph-mgr-dashboard ceph-mon ceph-osd ceph-petasan libcephfs2 librados2 libradosstriper1 librbd1 librgw2 petasan-container-images petasan-stats-config python3-ceph-argparse python3-cephfs python3-rados python3-rbd python3-rgw radosgw rbd-mirror 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. root@PETATEST03:~# apt install petasan Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: petasan : Depends: grub-efi-amd64-bin (= 2.04-2ubuntu26) but 2.06-2ubuntu14.1 is to be installed E: Unable to correct problems, you have held broken packages.
admin
2,930 Posts
Quote from admin on February 24, 2023, 9:32 pmFrom a system that has not upgraded, what is the output of the following:
dpkg -s grub-common | grep Version
apt-cache policy grub-common
apt list --upgradable | grep grub
From a system that has not upgraded, what is the output of the following:
dpkg -s grub-common | grep Version
apt-cache policy grub-common
apt list --upgradable | grep grub
robindewolf
9 Posts
Quote from robindewolf on February 24, 2023, 9:44 pmdpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.18
Version table:
*** 2.02-2ubuntu8.18 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.02-2ubuntu8.17 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.18
Version table:
*** 2.02-2ubuntu8.18 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.02-2ubuntu8.17 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
admin
2,930 Posts
Quote from admin on February 24, 2023, 10:01 pmStrange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Strange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
admin
2,930 Posts
Quote from admin on February 24, 2023, 11:04 pmI installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
I installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
robindewolf
9 Posts
Quote from robindewolf on February 25, 2023, 11:58 amQuote from admin on February 24, 2023, 10:01 pmStrange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Hi,
enclosed the result after running the apt update:
root@PETATEST02:~# dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
root@PETATEST02:~# apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.25
Version table:
2.02-2ubuntu8.25 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
*** 2.02-2ubuntu8.18 100
100 /var/lib/dpkg/status
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packagesroot@PETATEST02:~# apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-efi-amd64-bin/bionic-updates 2.06-2ubuntu14.1 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc-bin/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
Quote from admin on February 24, 2023, 10:01 pmStrange it does not show version 2.06 which was causing the conflict error.
what is the result of last command
apt list --upgradable | grep grub
if it is empty, make sure you first run
apt update
Hi,
enclosed the result after running the apt update:
root@PETATEST02:~# dpkg -s grub-common | grep Version
Version: 2.02-2ubuntu8.18
root@PETATEST02:~# apt-cache policy grub-common
grub-common:
Installed: 2.02-2ubuntu8.18
Candidate: 2.02-2ubuntu8.25
Version table:
2.02-2ubuntu8.25 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
*** 2.02-2ubuntu8.18 100
100 /var/lib/dpkg/status
2.02-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packagesroot@PETATEST02:~# apt list --upgradable | grep grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-efi-amd64-bin/bionic-updates 2.06-2ubuntu14.1 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub-pc-bin/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
grub2-common/bionic-updates,bionic-security 2.02-2ubuntu8.25 amd64 [upgradable from: 2.02-2ubuntu8.18]
robindewolf
9 Posts
Quote from robindewolf on February 25, 2023, 12:12 pmQuote from admin on February 24, 2023, 11:04 pmI installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
Hello,
I can confirm that the following sequence of commands worked for me on the test cluster (starting from version 2.7.1 and updating to 2.8.1).
apt update
apt install ca-certificates
apt update
export DEBIAN_FRONTEND=noninteractive
apt -o Dpkg::Options::="--force-confdef" upgrade
apt install petasanThanks for the assistance and the fix!
Quote from admin on February 24, 2023, 11:04 pmI installed an old 2.6 from iso and found the issue when trying to perform upgrade. It seems it is a certificate authority cert issue that needs to be updated. The existing CA package was dated 2018. It was preventing access to the PetaSAN https repository.
To fix:
apt install ca-certificates
Then do apt update to include the PetaSAN repository.
This only affects 2.X and not 3.X. If you confirm this fixes it, i will update the online upgrade document to include this step for 2.X. 3.X update does not rely on user typing commands but fetches an update script we post online, so we can include such fix transparently in future when certificates require updating.
Hello,
I can confirm that the following sequence of commands worked for me on the test cluster (starting from version 2.7.1 and updating to 2.8.1).
apt update
apt install ca-certificates
apt update
export DEBIAN_FRONTEND=noninteractive
apt -o Dpkg::Options::="--force-confdef" upgrade
apt install petasan
Thanks for the assistance and the fix!