Bug 641113
| Summary: | snmpd always returns an incorrect sysObjectID of ".1.3" or ".0.1" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jeff Gehlbach <jeffg> |
| Component: | net-snmp | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0 | CC: | jsafrane, rrivera, rvokal |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 640848 | Environment: | |
| Last Closed: | 2011-05-19 14:13:25 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 652223 | ||
|
Description
Jeff Gehlbach
2010-10-07 19:09:39 UTC
See Bug 640848 (comment number 5) for a patch that corrects this problem in Fedora 13 for release 12 of the same upstream version of this package; there's also a discussion of the reasoning for including and excluding what I did in that patch. I'm checking now whether the same patch applies cleanly to package release 23. Verified that my proposed patch for Bug 640848 also applies cleanly and fixes the problem against release 23 of this package as included in RHEL6 beta 2. Rather than attach that patch separately to this report (in case the patch should be obsoleted), please see Attachment 452222 [details]. Setting this bug's Version to 6.0 -- not sure how it became set to 6.1, perhaps a mistake on my part. The report is actually filed against 6.0 beta 2. It's conceivable that the severity should also be bumped, as this problem renders many (most?) SNMP-based management platforms unable to identify a RHEL6 system as such, but I'm too new here to go mucking with that field. In any case, I'd love to see this bug get the same kind of attention that its Fedora cousin (bug 640848) has seen. Thanks for keeping it FaiF! -jeff Hi Jan, Congratulations to you and the whole RHEL team on getting 6.0 out the door :) Can you explain to me the disposition of this bug? I see that a copy of it got nominated for inclusion in ZStream; does that mean that the fix will never be included in the updates repo for non-ZStream RHN? Sorry if that seems a stupid question; I'm just not that familiar with how the various streams fit together. Thanks, -jeff (In reply to comment #12) > Can you explain to me the disposition of this bug? I see that a copy of it got > nominated for inclusion in ZStream; does that mean that the fix will never be > included in the updates repo for non-ZStream RHN? Sorry if that seems a stupid > question; I'm just not that familiar with how the various streams fit together. Don't worry, the streams fit together very well and every customer gets all the updates in 6.1 at the latest. And this one should be released even earlier (and for everybody). Thank you, Jan! An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0729.html |