Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3612

Maxscale zypper repository for SLES 15 broken

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: N/A
    • Component/s: Packaging
    • 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): 
      

        Attachments

          Activity

            People

            Assignee:
            dbart Daniel Bartholomew
            Reporter:
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration