Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-3096

Uninstall and repair do not reset configuration

    XMLWordPrintable

    Details

    • Type: Admin & Maintenance Task
    • Status: New
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: 1.14.1
    • Fix Version/s: None
    • Component/s: PMM Client
    • Labels:

      Description

      The uninstall action and potentially repair too would be expected to reset the configuration to "not configured", but they do not seem to do this.

      In the scenario where a node was configured for a now inaccessible IP address for PMM server, you are unable to clear its configuration without using `configure` once more.

      Repair will fail as it can't access PMM and uninstall will say that all is OK if there aren't any services.

      # pmm-admin --version
      1.14.1
      
      # pmm-admin list                                                                                                                                                           
      Unable to connect to PMM server by address: 192.168.121.90:8443
      Get https://192.168.121.90:8443/qan-api/ping: dial tcp 192.168.121.90:8443: connect: connection refused
      
      * Check if the configured address is correct.
      * If server is running on non-default port, ensure it was specified along with the address.
      * If server is enabled for SSL or self-signed SSL, enable the corresponding option.
      * You may also check the firewall settings.
      
      # pmm-admin uninstall                                                                                                                                                      
      OK, no services found.
      
      # pmm-admin repair
      Unable to connect to PMM server by address: 192.168.121.90:8443
      Get https://192.168.121.90:8443/qan-api/ping: dial tcp 192.168.121.90:8443: connect: connection refused
      
      * Check if the configured address is correct.
      * If server is running on non-default port, ensure it was specified along with the address.
      * If server is enabled for SSL or self-signed SSL, enable the corresponding option.
      * You may also check the firewall settings.
      

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ceri.williams Ceri Williams
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: