Bug 1038390 - snmp auth cannot work with new passwd and still work with old passwd
Summary: snmp auth cannot work with new passwd and still work with old passwd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Ryan Barry
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 03:26 UTC by haiyang,dong
Modified: 2016-02-10 19:39 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 12:30:13 UTC
oVirt Team: Node

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 27650 0 master MERGED Fix SNMP Never

Description haiyang,dong 2013-12-05 03:26:52 UTC 
Description of problem:
Using edit-node to install ovirt-node-plugin-snmp-3.0.3-1.fc19.noarch.rpm into 
ovirt-node-iso-3.0.3-1.1.fc19.iso,then clean install ovirt-node-iso-3.0.3-1.1.snmp.fc19.iso.
Configure network up and enable snmp and configure snmp password with "redhat123".
check that snmp auth work with snmp password "redhat123"
Then configure snmp with new snmp password with "redhat1234", but check that:
snmp auth cannot work with new passwd "redhat1234" and still work with old passwd "redhat123"


Version-Release number of selected component (if applicable):
ovirt-node-iso-3.0.3-1.1.fc19.iso
ovirt-node-plugin-snmp-3.0.3-1.fc19.noarch.rpm

How reproducible:
100%

Steps to Reproduce:

Actual results:


Expected results:

Additional info:
Comment 1 Sandro Bonazzola 2014-03-04 09:28:31 UTC 
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 2 Sandro Bonazzola 2014-10-17 12:30:13 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.