Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1349415 - Capsule upgrade fails with Proxy cannot be registered (422 Unprocessable Entity)
Summary: Capsule upgrade fails with Proxy cannot be registered (422 Unprocessable Entity)
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks: 1335807
TreeView+ depends on / blocked
 
Reported: 2016-06-23 12:35 UTC by Lukas Pramuk
Modified: 2016-07-27 13:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 13:56:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lukas Pramuk 2016-06-23 12:35:40 UTC 
Description of problem:
Capsule upgrade fails with Proxy cannot be registered (422 Unprocessable Entity)

Version-Release number of selected component (if applicable):
Satellite 6.2.0 Snap17

How reproducible:
always

Steps to Reproduce:
1. Re-register Capsule after upgrading Satellite to 6.2
# subscription-manager register --force --activationkey ak_rhel7 --org Default_Organization

2. Upgrade capsule packages
# yum update 

3. Generate capsule certs on Satellite and copy them to Capsule
# ssh $SAT capsule-certs-generate --capsule-fqdn $(hostname) --certs-tar $(hostname).tar
# scp $SAT:$(hostname).tar .

4. Upgrade Capsule <- THIS FAILS
# satellite-installer --upgrade --certs-tar $(hostname).tar
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: update_http_conf...
Upgrade Step: migrate_pulp...
Upgrade Step: fix_pulp_httpd_conf...
Upgrade Step: start_httpd...
Upgrade Step: start_qpidd...
Upgrade Step: start_pulp...
Upgrade Step: remove_nodes_importers...
Upgrade Step: Running installer...
Installing             --- /etc/foreman-proxy/settings.d/pulpnode.ymlstr201 [99%] [....................................  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Failed to call refresh: Proxy <CAPSULE_FQDN> cannot be registered (422 Unprocessable Entity): Unable to communicate with the Capsule: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([Errno::EHOSTUNREACH]: No route to host - connect(2) for "<CAPSULE_FQDN>" port...) for Capsule https://<CAPSULE_FQDN>:9090/features Please check the Capsule is configured and running on the host.
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<CAPSULE_FQDN>]: Proxy <CAPSULE_FQDN> cannot be registered (422 Unprocessable Entity): Unable to communicate with the Capsule: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([Errno::EHOSTUNREACH]: No route to host - connect(2) for "<CAPSULE_FQDN>" port...) for Capsule https://<CAPSULE_FQDN>:9090/features Please check the Capsule is configured and running on the host.
Installing             Done                                               [100%] [....................................]
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/capsule.log
Upgrade Step: restart_services...

5. Check from outside of capsule open ports
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
443/tcp  open  https
3128/tcp open  squid-http
7911/tcp open  unknown
8000/tcp open  http-alt
8443/tcp open  https-alt
9090/tcp open  zeus-admin

6. Disable fw 
# iptables -F ; ip6tables -F


7. Re-run capsule upgrade successfully
# satellite-installer --upgrade --certs-tar $(hostname).tar
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: update_http_conf...
Upgrade Step: migrate_pulp...
Upgrade Step: fix_pulp_httpd_conf...
Upgrade Step: start_httpd...
Upgrade Step: start_qpidd...
Upgrade Step: start_pulp...
Upgrade Step: remove_nodes_importers...
Upgrade Step: Running installer...
Installing             Done                                               [100%] [...........................................................................................]
  The full log is at /var/log/foreman-installer/capsule.log
Upgrade Step: restart_services...
Katello upgrade completed!


Actual results:
capsule upgrade fails possibly due to firewall

Expected results:
capsule upgrade is successful
Comment 2 Sachin Ghai 2016-06-23 13:01:07 UTC 
Any new port needs to be opened on capsule to communicate with Sat server??
Comment 4 Lukas Pramuk 2016-06-23 14:23:07 UTC 
Not a bug? I came along rhel7 capsule 6.1 instance and it hasn't FW properly setup. hmm..
Comment 5 Bryan Kearney 2016-07-26 15:25:24 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 6 Bryan Kearney 2016-07-26 15:27:50 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 8 Lukas Pramuk 2016-07-27 13:56:14 UTC 
It wasn't reproduced in next snaps.
Note You need to log in before you can comment on or make changes to this bug.