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 1883093 - installer-upgrade failed with error "Could not evaluate: Proxy XYZ.com cannot be retrieved: unknown error (response 500)"
Summary: installer-upgrade failed with error "Could not evaluate: Proxy XYZ.com cannot...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.8.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.8.0
Assignee: Eric Helms
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-28 05:13 UTC by Devendra Singh
Modified: 2020-10-27 13:09 UTC (History)
8 users (show)

Fixed In Version: satellite-installer-6.8.0.11-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:09:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:09:24 UTC

Description Devendra Singh 2020-09-28 05:13:14 UTC 
Description of problem: installer-upgrade failed with error "Could not evaluate: Proxy XYZ.com cannot be retrieved: unknown error (response 500)"


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

How reproducible:
always (for one customer database)

Steps to Reproduce:
1. Restore the satellite 6.7 using customer provided backup 
2. Perform upgrade from 6.7 to 6.8
3. Upgrade job fail in the "installer-upgrade" phase with error "Could not evaluate: Proxy XYZ.com cannot be retrieved: unknown error (response 500)"

Actual results:
Satellite upgrade failed

Expected results:
Satellite upgrade should be successful.

Additional info:
Comment 2 Justin Sherrill 2020-09-28 19:33:11 UTC 
Imaanpreet Kaur on the performance team hit this with a fresh install.  Re-running the installer resolved it
Comment 3 Devendra Singh 2020-09-30 06:00:43 UTC 
(In reply to Justin Sherrill from comment #2)
> Imaanpreet Kaur on the performance team hit this with a fresh install. 
> Re-running the installer resolved it

Right, I tried it again and it completed successfully.
Comment 9 Mike McCune 2020-10-06 17:29:26 UTC 
Imaan and Jan,

once you re-run 'satellite-installer' does it complete properly? If so, can you then proceed with performance and scale testing? I'm trying to ensure you aren't blocked from your work and have a workaround that you can recover from this situation.
Comment 16 Devendra Singh 2020-10-09 06:31:07 UTC 
Failed QA 

Tested on 6.8.0 Snap19

/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[XYZ.com]: Could not evaluate: Proxy XYZ.com cannot be retrieved: unknown error (response 500)
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in `proxy'
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:13:in `id'
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:17:in `exists?'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property/ensure.rb:82:in `retrieve'
Comment 17 Mike McCune 2020-10-09 16:49:14 UTC 
Devendra, any time you hit this, can you get us the reproducing host that it occurs on please?
Comment 18 Devendra Singh 2020-10-09 17:11:30 UTC 
(In reply to Mike McCune from comment #17)
> Devendra, any time you hit this, can you get us the reproducing host that it
> occurs on please?

I have shared the details on email.
Comment 19 Mike McCune 2020-10-09 20:02:30 UTC 
Eric, looks like changes to /etc/foreman-installer/scenarios.d/satellite-answers.yaml are not getting picked up during upgrade as it lands as an .rpmnew file:

#  grep timeout /etc/foreman-installer/scenarios.d/satellite-answers.yaml

# grep timeout /etc/foreman-installer/scenarios.d/satellite-answers.yaml.rpmnew 
  passenger_start_timeout: 600

this is causing the upgrade test to fail.
Comment 24 Devendra Singh 2020-10-19 11:12:59 UTC 
Verified on 6.8.0 Snap20.

Verification points:

1- Install Satellite on 3 servers and didn't see this problem.
2- didn't see the problem with the customer DB upgrade (Tested with 4 DB).
Comment 27 errata-xmlrpc 2020-10-27 13:09:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366
Note You need to log in before you can comment on or make changes to this bug.