Bug 179642
Summary: | Applet cannot connect to RHN for several days | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Ian Laurie <nixuser> |
Component: | rhn-applet | Assignee: | Robin Norwood <robin.norwood> |
Status: | CLOSED WONTFIX | QA Contact: | Brandon Perkins <bperkins> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 18:47:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ian Laurie
2006-02-01 20:35:22 UTC
I got this connecting again, but not clear how I did it. It was a sequence something like this: 1. Right click the applet, but the configuration option greyed out. 2. Select run up2date as that is not greyed out. 3. For a short time the applet is no longer in error mode as it is trying to check in, it can't, but until it works that out the configuration option isn't greyed out any longer, so I selected it. 4. As I don't use a proxy there is nothing to configure so I just hit "forward" a few times and then "apply". 5. It started connecting again. I've never had it configured to use a proxy. For some reason it is as if the config file got corrupted, but I cannot imagine how. User bnackash's account has been closed This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |