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-repository | Assignee: | Leapp Notifications Bot <leapp-notifications-bot> |
| Status: | NEW --- | QA Contact: | upgrades-and-conversions |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.9 | ||
| Target Milestone: | rc | ||
| 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: | 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
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. |