Bug 750712

Summary: NFS4.1: parse RECLAIM_COMPLETE opcode
Product: Red Hat Enterprise Linux 6 Reporter: Karel Srot <ksrot>
Component: wiresharkAssignee: Peter Hatina <phatina>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: low Docs Contact:
Priority: medium    
Version: 6.2CC: dapospis, rvokal, tsmetana
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: wireshark-1.8.8-5.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 07:28:50 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: 947781, 960054    

Description Karel Srot 2011-11-02 06:46:00 UTC
Description of problem:

We need to bring in the patch for 
    https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4469
to be able to parse RECLAIM_COMPLETE opocode

See https://bugzilla.redhat.com/show_bug.cgi?id=746839
comments #c18, #c19, #c23


Version-Release number of selected component (if applicable):
wireshark-1.2.15-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. use pcap from upstream report
2.
3.
  
Actual results:
RECLAIM-COMPLETE opcode is not parsed

Comment 3 Suzanne Logcher 2012-02-14 23:19:26 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 10 errata-xmlrpc 2013-11-21 07:28:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1569.html