Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2144139

Summary: [leapp] Invalid format in config file /etc/fcoe/cfg-ens2f0.bk
Product: Red Hat Enterprise Linux 7 Reporter: guazhang <guazhang>
Component: leapp-repositoryAssignee: Leapp Notifications Bot <leapp-notifications-bot>
Status: CLOSED MIGRATED QA Contact: upgrades-and-conversions
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9Keywords: MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-12 13:22:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description guazhang@redhat.com 2022-11-19 05:23:50 UTC 
Description of problem:
leapp upgrade testing found the error in fcoe service, please have a look

Version-Release number of selected component (if applicable):
RHEL-7.9 Server x86_64 to kernel-4.18.0-438.el8

How reproducible:


Steps to Reproduce:
1. https://gitlab.cee.redhat.com/kernel-qe/kernel/-/blob/master/storage/block/leapp_system_upgrade/main.sh
1. upgrade successful 
2. check fcoe status 
3.

Actual results:


Expected results:


Additional info:

Red Hat Enterprise Linux 8.8 Beta (Ootpa) 
Kernel 4.18.0-438.el8.x86_64 on an x86_64 



[root@storageqe-68 ~]# systemctl status fcoe.service
● fcoe.service - Open-FCoE Inititator.
   Loaded: loaded (/usr/lib/systemd/system/fcoe.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2022-11-19 00:01:43 EST; 19min ago
  Process: 6096 ExecStart=/usr/sbin/fcoemon $FCOEMON_OPTS (code=exited, status=0/SUCCESS)
  Process: 6093 ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS (code=exited, status=0/SUCCESS)
 Main PID: 6097 (fcoemon)
    Tasks: 1 (limit: 201739)
   Memory: 344.0K
   CGroup: /system.slice/fcoe.service
           └─6097 /usr/sbin/fcoemon --syslog

11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com systemd[1]: Starting Open-FCoE Inititator....
11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com fcoemon[6096]: Invalid format in config file /etc/fcoe/cfg-ens2f0.bk: FCOE_ENABL>
11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com fcoemon[6096]: Invalid format for FCOE_ENABLE variable in /etc/fcoe/cfg-ens2f0.bk
11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com fcoemon[6096]: Invalid format in config file /etc/fcoe/cfg-ens2f1.bk: FCOE_ENABL>
11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com fcoemon[6096]: Invalid format for FCOE_ENABLE variable in /etc/fcoe/cfg-ens2f1.bk
11月 19 00:01:43 storageqe-68.rhts.eng.pek2.redhat.com systemd[1]: Started Open-FCoE Inititator..
lines 1-17/17 (END)

[root@storageqe-68 ~]# cat /etc/fcoe/cfg-e
cfg-ens2f0     cfg-ens2f0.bk  cfg-ens2f1     cfg-ens2f1.bk  cfg-ethx       
[root@storageqe-68 ~]# cat /etc/fcoe/cfg-ens2f0.bk 
FCOE_ENABLE=yes
MODE=fabric
DCB_REQUIRED=yes
AUTO_VLAN=no
[root@storageqe-68 ~]# cat /etc/fcoe/cfg-ens2f0 | grep -v ^#
FCOE_ENABLE="yes"

DCB_REQUIRED="no"

AUTO_VLAN="yes"

MODE="fabric"

[root@storageqe-68 ~]# 

fcoe-utils-1.0.33-4.git848bcc6.el8.x86_64




[root@storageqe-68 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b8:83:03:51:84:a6 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f0
    inet 10.73.130.177/23 brd 10.73.131.255 scope global dynamic noprefixroute eno1
       valid_lft 39770sec preferred_lft 39770sec
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether b8:83:03:51:84:a7 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether b8:83:03:51:84:a8 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f2
5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether b8:83:03:51:84:a9 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f3
6: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f4:e9:d4:45:34:c0 brd ff:ff:ff:ff:ff:ff
    altname enp55s0f0
    inet 172.17.99.213/16 brd 172.17.255.255 scope global dynamic noprefixroute ens2f0
       valid_lft 601360sec preferred_lft 601360sec
7: ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f4:e9:d4:45:34:c2 brd ff:ff:ff:ff:ff:ff
    altname enp55s0f1
8: ens2f0.200-fcoe@ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f4:e9:d4:45:34:c0 brd ff:ff:ff:ff:ff:ff
9: ens2f1.200-fcoe@ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f4:e9:d4:45:34:c2 brd ff:ff:ff:ff:ff:ff
[root@storageqe-68 ~]# 


https://beaker.engineering.redhat.com/recipes/12965016#task152870733,task152870753
Comment 4 Petr Stodulka 2022-11-22 13:55:19 UTC 
Hi, thank you for the report. Currently not sure this is even supported. FCOE is currently not supported for the in-place upgrades - as any other storage based on network, but not arguing that in such a case there could be at least an inhibitor for the upgrade in case FCOE is detected.
Comment 5 RHEL Program Management 2023-09-12 12:30:56 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-09-12 13:22:20 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.