We have currently a bug with SuSE Liberty Linux and EFI boot, but only a lite subscription. That has no support, which is fine but is there still a way to report the bug? Other users would also benefit.
Some of the EFi systems will fail to boot after the first yum update
because the provided shim-x64
package removes the shim*.efi
files from EFI/centos/
inside the EFI partition. Copying those files from EFI/redhat
to EFI/centos
makes the system bootable again.
I too would like to know an answer to this. Same situation, have a lite subscription and I am seeing checksum errors on mirror sync which I suspect are due to metadata on the repo being incorrect.
W, [2024-10-07T11:11:21.367585 #11672] WARN -- : × bind-lite-devel-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.374102 #11672] WARN -- : × bind-libs-lite-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.377064 #11672] WARN -- : × bind-pkcs11-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.378400 #11672] WARN -- : × bind-pkcs11-utils-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.384181 #11672] WARN -- : × bind-sdb-chroot-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.390344 #11672] WARN -- : × bind-sdb-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.391426 #11672] WARN -- : × bind-utils-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.400482 #11672] WARN -- : × bind-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.479580 #11672] WARN -- : × bind-pkcs11-libs-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
Edit:
I attempted to clear and resync the mirrors to see if this would clear things up. It has not:
rmt-cli repos disable 6747 6748 6986 6987
rmt-cli repos clean
rmt-cli repos enable 6747 6748 6986 6987
rmt-cli sync
rmt-cli mirror
Exaclt the same error as @JKWMoore reported. Unfortunately, in the same boat being a lite user with no support.
Slightly frustrated as what is the point of paying for the repository if you can use it due to checksum issues. Hope someone from Suse sees this and fixes the issue.
@JKWMoore @sp-de-nrw @sp-de-nrw Hi, have you logged into SUSE Customer Center and opened a Support Request there?
While I’ve purchased extended CentOS support, I’m unable to submit a support ticket due to the lack of paid support. This is frustrating, especially since the issue is related to SUSE. It seems that the only solution is to either buy additional support or deal with the problem.
Same situation as Zulu says above. I’m unable to submit a support ticket due to having a Lite subscription.
i.e
@JKWMoore @Zulu @sp-de-nrw I guess you could try Bugzilla then… https://bugzilla.suse.com/
1231501 – rmt-cli mirror failing raised.
I’m hoping for the best, but I’m not expecting much.
N.b. I now see the mirror working correctly.
SuSE maintains community support channels, such as the openSUSE Forums and the openSUSE Bugzilla. While openSUSE is the community branch and distinct from SuSE Liberty Linux, SuSE engineers monitor these forums, and related issues are sometimes resolved in both community and enterprise versions.
Whilst the openSUSE project is sponsored by SUSE openSUSE is independent from SUSE - SUSE are not responsible for openSUSE resources such as their Forums or Bugzilla. I’ll also note that these SUSE Forums are not the official route to SUSE support - instead you should open a support case via the SUSE Customer Center.
I would if I could.
The lite subscription causes this tiny detail in the customer portal and hence the question in this thread: “You are not currently entitled to use the support system.”
It is disabled caused by the lite subscription (in our case).
Yes I saw your earlier post but wanted to provide the correct information and general procedure. I did previously flag this thread to a SUSE contact and will ask the question about support for Liberty Lite.