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.

Description of problem:

An IPoIB interface which was correctly configured previously has come up in a bad state after a recent reboot, presumably following an initscripts update since the last boot.
It's supposed to be operating in CONNECTED_MODE (set in ifcfg-ib0) but actually came up in datagram mode, with resulting grief on the NFS mounts.
It turns out that ifup brings it up using ifup-eth, not ifup-ib because there's no keys-ib0 file which it checks for.
I don't know where that's supposed to come from, and unfortunately don't have a backup to know if it was there previously when the interface came up correctly.  Creating one with the right contents fixed the problem.

Version-Release number of selected component (if applicable):
initscripts-9.03.49-1.el6_7.1.x86_64

Working fine for me because I have:

TYPE=InfiniBand

in my ifcfg-ib0 file which is what sets the DEVICETYPE used for ifup-$DEVICETYPE.  It should also work if TYPE is missing, because then it should strip the number from DEVICE and use that.

DO you have the original ifcfg file?

(In reply to Orion Poplawski from comment #2)
> Working fine for me because I have:
> 
> TYPE=InfiniBand
> 
> in my ifcfg-ib0 file which is what sets the DEVICETYPE used for
> ifup-$DEVICETYPE.  It should also work if TYPE is missing, because then it
> should strip the number from DEVICE and use that.

Thanks for the clue.  TYPE is undocumented as far as I can see, but it turns
out our dear vendor had set it to Ethernet originally.  I should have looked
more closely -- sorry for the noise.  It works once I remove that.

Something seems to have changed in initscripts because it was originally working
somehow, but the change looks like a bug fix if anything.  (I realized since
it's under etckeeper I could check the whole configuration was unchanged.)

I don't seem to have a way to mark this as invalid.