Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1531147 - Can't register RHSM or apply cfme updates through webui on IPV6 only appliance
Can't register RHSM or apply cfme updates through webui on IPV6 only appliance
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.8.0
Unspecified Unspecified
high Severity high
: GA
: 5.8.3
Assigned To: Brandon Dunne
luke couzens
webui:upgrade:black
: ZStream
Depends On: 1518695
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-04 11:34 EST by luke couzens
Modified: 2018-02-28 08:12 EST (History)
6 users (show)

See Also:
Fixed In Version: 5.8.3.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-28 08:12:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0374 normal SHIPPED_LIVE Important: Red Hat CloudForms security, bug fix, and enhancement update 2018-02-28 13:04:37 EST

  None (edit)
Description luke couzens 2018-01-04 11:34:59 EST
Description of problem:Can't register RHSM or apply cfme updates through webui on IPV6 only appliance


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


How reproducible:100%

Steps to Reproduce:
1.provision appliance in ipv6 env
2.configure database
3.add latest repos
4.configure ipv4 proxy
5.export https and http proxy settings
5.connect to ui
6.nav to configuration-settings-CFME Region-Red Hat Updates
7.Edit subscription
8.configure RHSM subscription with use of local proxy (https://localhost:3128)
9.validate settings
10.save settings
11.Register appliance

Actual results:
Last message says 'Registration failed'

evm.log
[----] E, [2017-11-29T03:14:13.002501 #19372:bd513c] ERROR -- : MIQ(MiqServer#register) Registration Failed

Expected results:
Registration completes successfully and updates found 


Additional info:
This bug relates to 1524580 and I would think its just a case of back porting the fix.
Comment 2 Dave Johnson 2018-01-05 09:58:17 EST
Adding blocker just to make sure we get the back port for 5.8.3
Comment 4 CFME Bot 2018-01-09 16:55:18 EST
New commit detected on ManageIQ/manageiq/fine:
https://github.com/ManageIQ/manageiq/commit/4a60e2d402875ebdb984d5ea52f46a3bb5480f63

commit 4a60e2d402875ebdb984d5ea52f46a3bb5480f63
Author:     Nick Carboni <ncarboni@redhat.com>
AuthorDate: Wed Dec 6 18:29:20 2017 -0500
Commit:     Satoe Imaishi <simaishi@redhat.com>
CommitDate: Tue Jan 9 16:08:51 2018 -0500

    Merge pull request #16610 from bdunne/subscription_manager_with_a_proxy
    
    Use LinuxAdmin::SubscriptionManager directly.
    (cherry picked from commit 1bfd713ca66128d1dc4254e35d69c8bbf7e57830)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1531147

 Gemfile                                    |  1 +
 app/models/miq_server/update_management.rb | 16 +++++++---------
 app/models/registration_system.rb          |  2 +-
 3 files changed, 9 insertions(+), 10 deletions(-)
Comment 5 CFME Bot 2018-01-10 17:11:12 EST
New commit detected on ManageIQ/manageiq/fine:
https://github.com/ManageIQ/manageiq/commit/e48ce4a982b0e609fb5ab03f9aec0f0a14d9b76d

commit e48ce4a982b0e609fb5ab03f9aec0f0a14d9b76d
Author:     Brandon Dunne <brandondunne@hotmail.com>
AuthorDate: Wed Jan 10 15:29:31 2018 -0500
Commit:     Brandon Dunne <brandondunne@hotmail.com>
CommitDate: Wed Jan 10 15:29:31 2018 -0500

    Use a special release of linux_admin with only this change
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1531147

 Gemfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 6 luke couzens 2018-01-16 12:47:13 EST
Verified in 5.8.3.1
Comment 9 errata-xmlrpc 2018-02-28 08:12:18 EST
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, 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-2018:0374

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