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

Rebuild Replica fails when using MaxScale encrypted password for Monitor

    XMLWordPrintable

Details

    • Bug
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • 22.08.17, 23.02.14, 23.08.10, 24.02.6, 25.01.3
    • 22.08.18
    • None
    • None

    Description

      Rebuild Replica fails when using MaxScale encrypted password for Monitor.

      If you use the following Monitor configuration using an encrypted password

      [Monitor]
      type=monitor
      module=mariadbmon
      servers=ub01,ub01g
      user=mxs_user
      password=53183D571DCCDBC5E9A8D68267D7CBE5290B3D07BCE65A98F1B53
      ssh_user=msa
      ssh_keyfile=/tmp/id_rsa
      ssh_check_host_key=off
      

      When you try to rebuild a replica, on the source node the mariabackup command is sent the encrypted password value, causing the process to fail.

      If you use the below Monitor configuration when you try to rebuild a replica, it sends the plain text password, and this let's the mariabackup command succeed

      [Monitor]
      type=monitor
      module=mariadbmon
      servers=db1,db2
      user=m_user
      password=plain_text_password
      ssh_user=msa
      ssh_keyfile=/tmp/id_rsa
      ssh_check_host_key=off
      

      Can we allow for encrypted passwords to be used for the Rebuild Replica process and have the correct version (plain text) sent to the mariabackup?

      Attachments

        Issue Links

          Activity

            People

              esa.korhonen Esa Korhonen
              kyle.hutchinson Kyle Hutchinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.