Bug 767547

Summary: hrSystemDate timzeone sign is incorrect
Product: Red Hat Enterprise Linux 6 Reporter: Arjen Heidinga <dexter>
Component: net-snmpAssignee: Jan Safranek <jsafrane>
Status: CLOSED WORKSFORME QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2CC: dexter
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-14 15:18:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Arjen Heidinga 2011-12-14 10:50:59 UTC 
The fix as stated in Bug 683680 did not fix this issue, sadly:

[nagios@bigbrother ~]$  snmpwalk -c public -v 1 leeuwarden 1.3.6.1.2.1.25.1.2
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2011-12-14,11:43:22.0,+1:0

[nagios@bigbrother ~]$  snmpwalk -c public -v 2c lipwig 1.3.6.1.2.1.25.1.2
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2011-12-14,11:43:27.0,-1:0

'Leeuwarden' is still a rhel 5.7 box.
Comment 2 Jan Safranek 2011-12-14 11:16:35 UTC 
I am not sure I understand. Which one of the two snmpwalk above is wrong?
leeuwarden or lipwig? What OS is on lipwig? What net-snmp version and release
is running on both of them?

BTW, the bug #683680 you are referring to was fixed in snmpd daemon, not
snmpwalk.
Comment 3 Arjen Heidinga 2011-12-14 12:07:34 UTC 
excuse me, you are right.
the snmpd-daemon reports the timezone wrong in rhel 6.2. There was a report, which is closed now.
lipwig is rhel 6. snmpwalk only shows the difference between what it is (lipwig) and what is should be (leeuwarden).
Comment 4 Jan Safranek 2011-12-14 12:34:41 UTC 
So, is there a bug? What net-snmp version and release (rpm -q net-snmp) is running on leeuwarden and and what on lipwig?
Comment 5 Arjen Heidinga 2011-12-14 13:03:18 UTC 
Yes, there is a bug. snmpd reports the tomezone wrong. It reports -1 instead of +1. /etc/localtime is correct symlink to Europe/Amsterdam on both machines, date reports correct timezone. 


[arjenh@lipwig ~]$ rpm -qa |grep snmp
net-snmp-libs-5.5-31.el6.x86_64
net-snmp-5.5-31.el6.x86_64
[arjenh@lipwig ~]$ date
Wed Dec 14 14:00:55 CET 2011

[arjenh@leeuwarden ~]$ rpm -qa |grep snmp
net-snmp-libs-5.3.2.2-14.el5_7.1
net-snmp-5.3.2.2-14.el5_7.1
[arjenh@leeuwarden ~]$ date
Wed Dec 14 14:00:52 CET 2011
Comment 6 Jan Safranek 2011-12-14 13:27:53 UTC 
(In reply to comment #5)
> Yes, there is a bug. snmpd reports the tomezone wrong. It reports -1 instead of
> +1. /etc/localtime is correct symlink to Europe/Amsterdam on both machines,
> date reports correct timezone. 
> 
> [arjenh@lipwig ~]$ rpm -qa |grep snmp
> net-snmp-libs-5.5-31.el6.x86_64
> net-snmp-5.5-31.el6.x86_64

Please update to net-snmp-5.5-37, released in RHEL 6.2. This bug should be fixed there.
Comment 7 Arjen Heidinga 2011-12-14 15:08:26 UTC 
Yes it is. Sorry, i assumed that version was installed.
Problem only existed between keyboard and chair....