Ocata -> Pike overcloud upgrade: panko api haproxy backend is configured to listen on a different port than what's configured in the panko api container after upgrade:
[root@overcloud-controller-0 heat-admin]# grep -A6 panko /etc/haproxy/haproxy.cfg
listen panko
bind 10.0.0.12:8779 transparent
bind 172.16.18.25:13779 transparent ssl crt /etc/pki/tls/private/overcloud_endpoint.pem
http-request set-header X-Forwarded-Proto https if { ssl_fc }
http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
option httpchk
server overcloud-controller-0.internalapi.localdomain 192.168.0.15:8779 check fall 5 inter 2000 rise 2
[root@overcloud-controller-0 heat-admin]# docker exec -it panko_api cat /etc/httpd/conf.d/10-panko_wsgi.conf
# ************************************
# Vhost template in module puppetlabs-apache
# Managed by Puppet
# ************************************
<VirtualHost 192.168.0.15:8977>
ServerName overcloud-controller-0.internalapi.localdomain
## Vhost docroot
DocumentRoot "/var/www/cgi-bin/panko"
## Directories, there should at least be a declaration for /var/www/cgi-bin/panko
<Directory "/var/www/cgi-bin/panko">
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Require all granted
</Directory>
## Logging
ErrorLog "/var/log/httpd/panko_wsgi_error.log"
ServerSignature Off
CustomLog "/var/log/httpd/panko_wsgi_access.log" combined
SetEnvIf X-Forwarded-Proto https HTTPS=1
WSGIApplicationGroup %{GLOBAL}
WSGIDaemonProcess panko display-name=panko_wsgi group=panko processes=1 threads=2 user=panko
WSGIProcessGroup panko
WSGIScriptAlias / "/var/www/cgi-bin/panko/app"
</VirtualHost>
The ports in:
server overcloud-controller-0.internalapi.localdomain 192.168.0.15:8779 check fall 5 inter 2000 rise 2
and
<VirtualHost 192.168.0.15:8977>
don't match
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE