Bug 1360938 - satellite-installer --scenario satellite --upgrade --verbose --noop always fails yet upgrade succeeds
Summary: satellite-installer --scenario satellite --upgrade --verbose --noop always fa...
Keywords:
Status: CLOSED DUPLICATE of bug 1362236
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-27 23:00 UTC by Paul Armstrong
Modified: 2016-08-12 23:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-12 23:43:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Failed --noop run (1.20 MB, text/plain)
2016-07-27 23:00 UTC, Paul Armstrong
no flags Details
failed 2 (1.20 MB, text/plain)
2016-07-27 23:01 UTC, Paul Armstrong
no flags Details
successful upgrade (1.41 MB, text/plain)
2016-07-27 23:02 UTC, Paul Armstrong
no flags Details

Description Paul Armstrong 2016-07-27 23:00:52 UTC
Created attachment 1184837 [details]
Failed --noop run

Description of problem:
satellite-installer --scenario satellite --upgrade --verbose --noop always fails yet running the upgrade itself succeeds.

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

How reproducible:
Ran --noop several times, upgraded once succeeded

Steps to Reproduce:
1. Fresh 6.1.9 installation
2. integrate with IdM realm
3. loaded manifests and content
4. ran upgrade

Actual results:
[ERROR 2016-07-27 16:47:01 main]  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[sat6.parmstrong.ca]: Could not evaluate: Proxy sat6.parmstrong.ca cannot be registered (Connection refused - connect(2)): N/A
[ INFO 2016-07-27 16:47:01 main] /usr/share/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
[ INFO 2016-07-27 16:47:01 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:7:in `raise_error'
[ INFO 2016-07-27 16:47:01 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:59:in `rescue in proxy'
[ INFO 2016-07-27 16:47:01 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:53:in `proxy'
[ INFO 2016-07-27 16:47:01 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:63:in `id'
[ INFO 2016-07-27 16:47:01 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v2.rb:67:in `exists?'
[ INFO 2016-07-27 16:47:01 main] /usr/share/ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve'


Expected results:

Success!

Additional info:
See attached files...

Comment 1 Paul Armstrong 2016-07-27 23:01:52 UTC
Created attachment 1184838 [details]
failed 2

Comment 2 Paul Armstrong 2016-07-27 23:02:35 UTC
Created attachment 1184839 [details]
successful upgrade

Comment 4 Chris Roberts 2016-08-12 23:43:43 UTC

*** This bug has been marked as a duplicate of bug 1362236 ***


Note You need to log in before you can comment on or make changes to this bug.