FCoE is supported in RHV via a custom property https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/administration_guide/index#How_to_Set_Up_RHVM_to_Use_FCoE we should verify that it is as good in rhv-4.4-el8.
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops
This bug is depends on bug 1575930 fix. bug 1575930 impact is that VLAN tagged setups will not see the FCOE backend after reboot. This will affect installing RHEL/RHV from FCOE backend and also using FCEO as a storage domain.
Until we have the HW to due it(which we currently do not have) I'm marking this as QA_NACK.
(In reply to Avihai from comment #6) > Until we have the HW to due it(which we currently do not have) I'm marking > this as QA_NACK. Could you rather move this to COND_NAK instead of NAK? Do we have any chance of OTHER_QA?
Avihai, it is not clear which HW you are missing, how much it costs, and if you already applied to get it.
Created attachment 1650431 [details] engine vdsm logs and video capture of move fcoe assigned logical network to another port
Verified with the original scenario which is to run a VM on FCoE storage -> VM runs. Also tested basic live/cold snapshot creation on that VM. Tested on the rhv-4.4.0-13: vdsm-hook-fcoe-4.40.0-164.git38a19bb.el8ev.noarch fcoe-utils-1.0.32-6.el8.x86_64 vdsm-4.40.0-164.git38a19bb.el8ev.x86_64 ovirt engine 4.4.0-0.13.master.el7
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops
Hi, is there a forecast of a status update for this case? My SA team is supporting the original customer where the issue was identified. I see that Avinhai tested on rhv-4.4.0-13 and the status moved to VERIFIED. Is there a chance to have it supported in the next RHV 4.4?
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 (RHV RHEL Host (ovirt-host) 4.4), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:3246
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days