Pmm-upgrade + yum files

FYI: You make it really really difficult to use the pmm-upgrade script for those of us that are behind a proxy.

Please make the upgrade process honor the proxy config in the yum.config file… else it seems to get stuck in a loop

as well as it seems like on oracle 9 it does not like the async line in the yum files. Once it starts the upgrade it appears that if it fails it just starts over and over and over and over again

This was from 2.38.1

Starting "yum update --assumeyes pmm-update" ...
PostgreSQL YUM repository - x86_64              0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'percona-ppg-11':
  - Curl error (56): Failure when receiving data from the peer for [Recv failure: Connection reset by peer]
Error: Failed to download metadata for repo 'percona-ppg-11': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
time="2023-09-01T20:18:29Z" level=fatal msg="Update failed: `yum update --assumeyes pmm-update` failed: exit status 1"
ProjectName: pmm-update
Version: 2.39.0
PMMVersion: 2.39.0
Timestamp: 2023-08-10 10:05:17 (UTC)
FullCommit: a657accbb0fb96f0a099218efd4bfecc97eb216e
Starting "yum --verbose info installed pmm-update" ...
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, groups-manager, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync, system-upgrade
YUM version: 4.14.0
cachedir: /var/cache/dnf
Unknown configuration option: async = 1 in /etc/yum.repos.d/percona-ppg-11.repo
Unknown configuration option: async = 1 in /etc/yum.repos.d/percona-ppg-14.repo

Minor other item that might catch some people off guard as well it appears the ldap.toml files are wiped out (I “assumed” that it would follow the same aspect as the grafana.ini files and updated the one in /etc/grafana and not /usr/share/grafana/conf/ this may just be me being stupid though)

Hi @meyerder .
Thanks for letting us know and highlighting the problem.
Are you using AMI/OVF or docker versions of pmm-server?