Project

General

Profile

Bug #19329

Capsule server have lot issues after upgrade

Added by Mario Gamboa about 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Installer
Target version:
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

After upgrade one of my capsules i found some issues

To upgrade my capsule server i use the following command
foreman-installer --scenario foreman-proxy-content --upgrade --foreman-proxy-content-certs-tar "/root/katelloproxy00.tar" --certs-update-all --foreman-proxy-content-pulp-oauth-secret
"KPS4SwkDqbPNKPRqyCSrnr3bHGcDuCK1" --foreman-proxy-register-in-foreman "false" --certs-regenerate "true" --certs-deploy "true" -v

Because if i use without foreman proxy register parameter fail

This proxy have all this services Templates, Pulp Node, TFTP, DHCP, Puppet, Puppet CA, Logs, Dynflow, and SSH

after upgrade proxy need the following

need to verify

/etc/puppet/foreman.yaml
:url: "https://katellomain.example.com"
in this case the url was pointing to the proxy itself for this reason all the puppet agent fail also the puppet agent in the proxy fail after put the correct server works fine

after that try to provisioning a new machine and katello complains about can't get any ip available and give me 404 error

Checking

/etc/foreman-proxy/settings.yml
:trusted_hosts:
- proxy00.example.com

Found the only trusted server was currently the proxy and is not included the katellomain server in this case just add the katellomain server in trusted hosts

Next in
  1. Endpoint for reverse communication
    :foreman_url: https://proxy00.example.com

Also found the configuration change and was point to the proxy itself again solution replace for the good server

Checking also the dhcp configuration

/etc/foreman-proxy/settings.d/dhcp.yml

  1. Enable DHCP management
  2. Can be true, false, or http/https to enable just one of the protocols
    :enabled: false

the configuration was disable just enabled to working back

and finally all looks is working until the machine is try to register it is fail the issue was on the katello reverse proxy configuration

/etc/httpd/conf.d/28-katello-reverse-proxy.conf
  1. Proxy rules
    ProxyRequests Off
    ProxyPreserveHost Off
    ProxyPass / https://proxy00.example.com/
    ProxyPassReverse / /
    ProxyPassReverse / https://proxy00.example.com/

Also the configuration was change with the update put the proxy instead of the main katello server

after all this i make a restart of all the services

katello-service restart

Now all is ok apparently the upgrade process doesn't respect the configuration and make change to put the proxy itself in all the configurations

History

#1 Updated by Justin Sherrill about 5 years ago

  • Legacy Backlogs Release (now unused) changed from 226 to 228

#2 Updated by Justin Sherrill almost 5 years ago

Hi,

Are you still having this issue? Would you be able to test on 3.4 when it is released soon?

#3 Updated by Mario Gamboa almost 5 years ago

Hi there i saw the release of 3.4 i going to make the upgrade of katello 3.1 to 3.4 to see how this goes just a question about the proxy upgrade is good idea register again the proxy or is any change in the procedure of how we upgrade the proxy

#4 Updated by Justin Sherrill almost 5 years ago

You can just follow the upgrade docs for 3.4: https://theforeman.org/plugins/katello/3.4/upgrade/smart_proxy.html

#5 Updated by Mario Gamboa almost 5 years ago

Hi justin

that is the problem if we follow the instructions the proxy fail in register with katello server just remember this is a upgrade if i do a fresh install is ok all works as expected but upgrade is not working at all for example in the documentation never mention you need now to put the oath password with that the installer fail also i just try today upgrade from 3.1 to 3.4 and fail horrible but is i upgrade from 3.1 to 3.2 and after to 3.3 and after 3.4 some of the issues gone but i have the foreman-rake task no finish and crash and the installation is incomplete

If someone of the team can make a upgrade and see the same errors

#6 Updated by Mario Gamboa almost 5 years ago

i can just say this is all the issues present at this stage if you want to upgrade capsule server or katello from 3.1 to latest or a previous version

http://projects.theforeman.org/issues/19329
http://projects.theforeman.org/issues/19746
http://projects.theforeman.org/issues/19739

#7 Updated by Eric Helms almost 5 years ago

  • Legacy Backlogs Release (now unused) changed from 228 to 258

#8 Updated by Justin Sherrill almost 5 years ago

  • Status changed from New to Need more information

Can you upload a foreman-debug from one of your attempts when you went 3.1 -> 3.2 -> 3.3 -> 3.4.

FYI we usually test upgrading from two versions back (i.e. 3.3 -> 3.4 and 3.2 -> 3.4), we don't usually test anything further back than that.

#9 Updated by Justin Sherrill almost 5 years ago

  • Legacy Backlogs Release (now unused) changed from 258 to 166

#10 Updated by Eric Helms almost 5 years ago

  • Status changed from Need more information to Resolved

If you are still seeing this issue as of Katello 3.4, please re-open for us to consider.

Also available in: Atom PDF