Details
Description
User impact: in case of any error with storing config it;s very hard for the user to know what to do when they fixed the config file problem
Proposed solution: The Error message should suggest to user use `--force` flag if they need to force this action
Original report:
If PMM cannot write the config file, then it should have NOT succeeded in registering with the server. Otherwise, how do you fix this situation? There is no config file now.
[[email protected] ~]$ pmm-admin config --server-url https://pmm:yk%[email protected]:8443 --server-insecure-tls Checking local pmm-agent status... pmm-agent is running. Registering pmm-agent on PMM Server... Registered. Failed to write configuration file /usr/local/percona/pmm2/config/pmm-agent.yaml: open /usr/local/percona/pmm2/config/pmm-agent.yaml: permission denied. [[email protected] ~]$ sudo pmm-admin config --server-url https://pmm:yk%[email protected]:8443 --server-insecure-tls Checking local pmm-agent status... pmm-agent is running. Registering pmm-agent on PMM Server... Failed to register pmm-agent on PMM Server: Node with name "percona-pxc8-1" already exists..
----------
Attachments
Issue Links
- duplicates
-
PMM-8140 PMM registers even if permissions denied
-
- Done
-