Bug 839952
| Summary: | NOCpulse throws error every 15minutes if "eth0" is not a device | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Ken Hitchcock <ken.hitchcock> |
| Component: | Monitoring | Assignee: | Milan Zázrivec <mzazrivec> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan Hutař <jhutar> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 541 | CC: | aladke, chwilk, cperry, jhutar, mhuth, mminar, mmraka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | perl-NOCpulse-Gritch-1.27.9-3 MessageQueue-3.26.7-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-21 09:17:05 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 818987, 819027 | ||
|
Description
Ken Hitchcock
2012-07-13 09:38:30 UTC
Please submit a support request, so that we can correctly triage, replicate, track and associate with your company/organization. Regards, Cliff This issue has been fixed in Spacewalk 1.6 via bug 768188. Hi Clifford, My company is a Red Hat partner but for some reason i don't have the permission to create support tickets. I tend to install Satellite quite a bit for customers so i do come across different environments and sometimes uncover bugs. Do i have to go through support every time? Hi Michael, Can you confirm The fixes for Spacewalk will work on satellite 5.4.1 and will not void support from Red Hat? Thanks Ken (In reply to comment #3) > Hi Clifford, > > My company is a Red Hat partner but for some reason i don't have the > permission to create support tickets. > > I tend to install Satellite quite a bit for customers so i do come across > different environments and sometimes uncover bugs. Do i have to go through > support every time? > If you want the issue to be formally tracked, yes. Customer reported issues are of higher regard than 'random' untriaged/replicated and GSS reviewed/escalated bug reports. In this case, we had validation of this bug/issue from Spacewalk and we knew that we had fixed it. > Hi Michael, > > Can you confirm The fixes for Spacewalk will work on satellite 5.4.1 and > will not void support from Red Hat? Totally unsupported (by Red Hat Support and the Satellite Engineering team) if you manually apply fixes to the current 5.4.1 code base - there has been a lot of other changes. We have formal processes, where customers can work with Support for triage/escalation, where needed, to get fixes back-ported to earlier products (though today 5.4.1 is current, 5.5 is to be GA'd soon, fall/autumn 2012). Regards, Clifford Satellite Engineering Manager > > Thanks > Ken This issue is resolved with the release of RHN Satellite 5.5. As of September 20th 2012, RHN Satellite 5.5 has been generally available. Release Notes and other 5.5 documentation can be found here: https://access.redhat.com/knowledge/docs/Red_Hat_Network_Satellite/ The associated Errata for the 5.5 release are: 5.5 Satellite GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1296.html 5.5 Upgrade Errata - http://rhn.redhat.com/errata/RHEA-2012-1298.html 5.5 RHN Proxy GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1297.html 5.5 RHN Tools GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1299.html Regards, Clifford - Engineering Manager, Satellite How about a work-around or patch for those of us who have to go through a long change-management process for something as major as a minor number upgrade? I'm about to hunt down the script or binary myself and hack it by hand, but I would have expected to find something of use in this thread. Hello Chandler, in the upstream bugzilla (referenced in comment #2) there's list of commits fixing the bug. To see patches just put commit SHA IDs into google search. *** Bug 875600 has been marked as a duplicate of this bug. *** |