On Wed, Feb 19, 2020 at 04:35:40PM +0200, Gal Pressman wrote: > > Again, call it what you want, but you can't deny this change to force the rename > > by default has not broken things. For the record I'm not even talking about PSM2 > > here. There are other, more far reaching implications. > > It's not just PSM2, it broke our libfabric provider and apparently MVAPICH as well: > http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/2020-January/006960.html You all recognize that finding stuff name dependent stuff like this is horribly hacky, right? The whole point of doing this, over a long time, is to get all this hacky stuff fixed up. > Regarding the issue you described, why not disable the rename on the upgrade > path and only enable it for fresh installations? That isn't really a rdma-core issue, though? Jason
