Bug 593824
Summary: | fcoe-utils should be upgraded to 1.0.14 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Yi Zou <yi.zou> | ||||
Component: | fcoe-utils | Assignee: | Jan Zeleny <jzeleny> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Miroslav Vadkerti <mvadkert> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.0 | CC: | ovasik, yi.zou | ||||
Target Milestone: | rc | Keywords: | OtherQA, Rebase | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | fcoe-utils-1.0.14-1.el6 | Doc Type: | Rebase: Bug Fixes and Enhancements | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-11-15 13:57:29 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: | 593827 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Yi Zou
2010-05-19 19:19:39 UTC
(In reply to comment #0) > Notes: > 1) Libhbalinux also needs updating, I will create a separate BZ for it shortly > after this. Bug 593827 has been created for libhbalinux. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. I'm waiting for approval of this rebase right now. In the meantime I was advised of missing man pages in fcoe-utils. Particularly for these utilities: /usr/sbin/fcnsq /usr/sbin/fcping /usr/sbin/fcrls Every utility in RHEL-6 should have its man page. Could you guys please make them? I'll probably have to create them anyway, but I prefer you making them because this way they'll most likely be more precise. What do you think? (In reply to comment #4) > I'm waiting for approval of this rebase right now. In the meantime I was > advised of missing man pages in fcoe-utils. Particularly for these utilities: > > /usr/sbin/fcnsq > /usr/sbin/fcping > /usr/sbin/fcrls > > Every utility in RHEL-6 should have its man page. Could you guys please make > them? I'll probably have to create them anyway, but I prefer you making them > because this way they'll most likely be more precise. What do you think? This would not block you getting your rpm updated, right? Meanwhile I will get man pages creation started for these tools, and post to open-fcoe.org later, then you can also review. No, it's not a blocker for now. But I think it will be an issue later. I will prepare new packages and those man pages can be added afterwards. The build is ready, switching to MODIFIED. Created attachment 423358 [details] Man page patches tar ball with patch series file included This tar ball is to address Bug 593824 and Bug 594173. It includes the following patches that are sent to open-fcoe.org and expected to be pulled in to fcoe-utils.git soon. eada1dc fcoe-utils/fcping: add man page for the fcping tool 45c5d35 fcoe-utils/fcnsq: add man page for the fcnsq tool d955332 fcoe-utils/fcrls: add man page for the fcrls tool 54d5e2b fcoe-utils/fcrls: rport in sysfs can be a link as well Links to the patch on mailing list: http://www.open-fcoe.org/pipermail/devel/2010-June/010350.html http://www.open-fcoe.org/pipermail/devel/2010-June/010349.html http://www.open-fcoe.org/pipermail/devel/2010-June/010351.html http://www.open-fcoe.org/pipermail/devel/2010-June/010352.html Links to open-fcoe.org patch work if you want to get then from there http://www.open-fcoe.org/patchwork/project/open-fcoe/list/ Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |