Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1359544 - [Docs][Install][Admin] remove fcoe link from 'Adding FCP Storage'
[Docs][Install][Admin] remove fcoe link from 'Adding FCP Storage'
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
4.0.0
Unspecified Unspecified
unspecified Severity unspecified
: ovirt-4.0.2
: 4.0.0
Assigned To: Julie
rhev-docs@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-24 19:54 EDT by Julie
Modified: 2016-07-27 20:48 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 20:48:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Docs
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Julie 2016-07-24 19:54:20 EDT
Based on some feedback from Marina that link to FCOE is causing confusion for customers. I believe it was mislinked in the first place and should be removed. 
FCOE is currently not supported. See RFE https://bugzilla.redhat.com/show_bug.cgi?id=1317452 for more information.
Comment 5 Marina 2016-07-25 17:52:15 EDT
The 3.5 guide is talking about FC storage and it should not link to FCOE.
As for 3.6, I am not sure, need to check the docs. Even if FCOE supported in 3.6, it should be referenced from the correct location and not from the section talking about plain FC.
Comment 6 Julie 2016-07-25 21:16:05 EDT
Hi Yaniv, 
  Thanks for bringing the bug up, and yep, that bug is currently covered by Release Notes. I'm just removing the mentioning of FCOE in the general FCP storage section. I have mentioned this to Lucy. Please let her know if specific instructions need to be added in the official docs about the hook.

Kind regards,
Julie

Note You need to log in before you can comment on or make changes to this bug.