Bug 1270204
Summary: | Crash report on system after registering from "Register Now" rhsm-icon | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Rehana <redakkan> |
Component: | subscription-manager | Assignee: | Chris Snyder <csnyder> |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | bcourt, crog, stoner |
Target Milestone: | rc | Keywords: | Regression, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 11:51:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rehana
2015-10-09 09:26:14 UTC
A crash report is being generated but it appears that no functionality of subscription-manager is being blocked. Due to the crash report being generated however this should be fixed as it will generate many customer support calls. commit 071bd32f484ba5cf42d197282612365e10933a64 Author: Christopher Snyder <csnyder> Date: Fri Oct 9 11:24:01 2015 -0400 1270204: Crash report no longer sent when widget is none In master as of the above commit I saw the same issue as reported here on subscription-manager-1.15.9-14.el7.x86_64 Tested on RHEL-7.2-Snapshot-5.0: [root@dhcp129-21 ~]# rpm -qa | grep subscription subscription-manager-initial-setup-addon-1.15.9-15.el7.x86_64 subscription-manager-1.15.9-15.el7.x86_64 subscription-manager-gui-1.15.9-15.el7.x86_64 Waited for the rhsm-icon to appear and clicked the Register button. I then registered the system when the subman gui appeared as normal. There was no crash report or any other ABRT error. 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://rhn.redhat.com/errata/RHBA-2015-2122.html |