-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
None
-
False
-
sat-rocket
-
None
-
None
-
None
-
None
Description of problem:
After upgrading to Satellite 6.16, the customer started facing issues when connecting through the capsules.
The workaround was the change below
From
# grep " /rhsm" -r /etc/httpd/conf* /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPass /rhsm h2://sat02.king.lab/rhsm disablereuse=on retry=0 /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPassReverse /rhsm h2://sat02.king.lab/rhsm
To
# grep " /rhsm" -r /etc/httpd/conf* /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPass /rhsm https://sat02.king.lab/rhsm disablereuse=on retry=0 /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPassReverse /rhsm https://sat02.king.lab/rhsm
How reproducible:
Not reproducible
Is this issue a regression from an earlier version:
Steps to Reproduce:
1.
2.
3.
Actual behavior:
After some troubleshooting, the customer made the change, and everything worked as expected.
I checked in both versions, 6.15 and 6.17, and I didn't find any difference
Here, we can see a Capsule on 6.15
# rpm -q satellite-capsule satellite-capsule-6.15.5.2-1.el8sat.noarch # grep " /rhsm" -r /etc/httpd/conf* /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPass /rhsm h2://fqdn.here/rhsm disablereuse=on retry=0 /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPassReverse /rhsm h2://fqdn.here/rhsm
And here, a Capsule on 6.17
# rpm -q satellite-capsule satellite-capsule-6.17.4-1.el9sat.noarch # grep " /rhsm" -r /etc/httpd/conf* /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPass /rhsm h2://fqdn.here/rhsm disablereuse=on retry=0 /etc/httpd/conf.d/10-rhsm-pulpcore-https-443.conf: ProxyPassReverse /rhsm h2://fqdn.here/rhsm
Expected behavior:
Everything should still working after the upgade.
Business Impact / Additional info: