This introduced the following change in behaviour:
when setting `masterport` in any section different than `main`(eg. agent), this is ignored and the default `serverport` value is used.
users that have `masterport` set in their configuration, in a different section than `main`(eg. agent), are also affected as Puppet will not pick up the value set for `masterport` and it will use the default `serverport` value.
Version `6.19.0` added the `serverport` config as an alias for `masterport`. That change introduced a regression where `masterport` was ignored and set to default value after upgrading to `6.19.0` whenever `masterport` was set in any other section of `puppet.conf` but `main`. This was fixed by making both `masterport` and `serverport` visible in the other sections.