[katello] Portal conflict while upgrading

When I upgraded to Katello 3.1, from 3.0, the installer (it appears via
puppet) keeps changing the foreman proxy tls port from whatever it was set
to in settings.yml to 8443.

That port conflicts with the default candlepin port which causes the
upgrade to have an error because the proxy can't start with the address
already in use.

Am I missing something that needs to change so I don't run into this every
time I upgrade? I'm currently facing the same issue trying to upgrade from
3.1 to 3.2.

Thank you,
Peter

I finally got this figured out. Somehow, my katello-answers.yaml file had
been modified. When I got that fixed, the upgrade completed successfully.

··· On Wed, Oct 26, 2016 at 1:53 PM, Peter Kirby wrote:

When I upgraded to Katello 3.1, from 3.0, the installer (it appears via
puppet) keeps changing the foreman proxy tls port from whatever it was set
to in settings.yml to 8443.

That port conflicts with the default candlepin port which causes the
upgrade to have an error because the proxy can’t start with the address
already in use.

Am I missing something that needs to change so I don’t run into this every
time I upgrade? I’m currently facing the same issue trying to upgrade from
3.1 to 3.2.

Thank you,
Peter