[MXS-3612] Maxscale zypper repository for SLES 15 broken Created: 2021-05-06  Updated: 2021-07-26  Resolved: 2021-07-12

Status: Closed
Project: MariaDB MaxScale
Component/s: Packaging
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Daniel Bartholomew
Resolution: Done Votes: 0
Labels: None


 Description   

Setting up repositories with the repository setup script works fine:

ip-172-31-18-54:~ # ./mariadb_es_repo_setup --token="...token-uuid..." --apply  --mariadb-server-version="10.5"
 
[info] Repository file successfully written to /etc/zypp/repos.d/mariadb.repo
 
warning: Rebuilding outdated index databases
warning: Generating 18 missing index(es), please wait...

But when trying to install actual packages it turns out the signature of the Maxscale repositories repomd.xml file is not correct:

ip-172-31-18-54:~ # zypper install MariaDB-server MariaDB-backup
Refreshing service 'Basesystem_Module_x86_64'.
Refreshing service 'Containers_Module_x86_64'.
Refreshing service 'Desktop_Applications_Module_x86_64'.
Refreshing service 'Development_Tools_Module_x86_64'.
Refreshing service 'Legacy_Module_x86_64'.
Refreshing service 'Public_Cloud_Module_x86_64'.
Refreshing service 'Python_2_Module_x86_64'.
Refreshing service 'SUSE_Cloud_Application_Platform_Tools_Module_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_x86_64'.
Refreshing service 'Server_Applications_Module_x86_64'.
Refreshing service 'Web_and_Scripting_Module_x86_64'.
Retrieving repository 'MariaDB Enterprise Server' metadata ...............[done]
Building repository 'MariaDB Enterprise Server' cache ....................[done]
Retrieving repository 'MariaDB MaxScale' metadata ---------------------------[|]
Signature verification failed for file 'repomd.xml' from repository 'MariaDB MaxScale'.
 
    Note: Signing data enables the recipient to verify that no modifications
    occurred after the data were signed. Accepting data with no, wrong or
    unknown signature can lead to a corrupted system and in extreme cases even
    to a system compromise.
 
    Note: File 'repomd.xml' is the repositories master index file. It ensures
    the integrity of the whole repo.
 
    Warning: This file was modified after it has been signed. This may have been
    a malicious change, so it might not be trustworthy anymore! You should not
    continue unless you know it's safe.
 
Signature verification failed for file 'repomd.xml' from repository 'MariaDB MaxScale'. Continue? [yes/no] (no): 



 Comments   
Comment by Daniel Bartholomew [ 2021-05-07 ]

If the issue is that the repomd.xml file was modified but the signing step to update the signature file was not done then this is definitely something for the MaxScale project.

Comment by markus makela [ 2021-06-15 ]

dbart I'll assign this to you while Timofey is away. If you need us to change something on the MaxScale side, please let us know.

Comment by Daniel Bartholomew [ 2021-07-02 ]

I'm not getting this error any more in my testing. So I guess someone on the MaxScale team fixed the signing issue with the Maxscale repositories.

Comment by markus makela [ 2021-07-12 ]

Closing as Done since it now seems to work.

Generated at Thu Feb 08 04:22:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.