Internap support has stated this is due to some legacy kernel module they are in the process of phasing out. Target is week of July 10 for the rest of their upgrades. The workaround above stands for now we will retest once we’ve been notified of the upgrade completion.
Wow, great work debugging this. Thanks a lot @wgrant and @noise!
I applied the suggested workaround here:
https://github.com/snapcore/snapcraft/pull/1386
I’ll keep hitting the re-run button over the weekend, to give it a try with a few executions.
1 Like
I got confirmation today that the Internap fix was rolled out globally. Calling this fixed!
It should not be necessary anymore, but won’t hurt to leave it.
I agree with Bret in that it’s not harmful (if anything, maybe slows things down a tiny bit). I’d consider removing it and if you happen to see the same problem again, please report it (regression!) and the workaround can be re-enabled, which would be a quick action on your side.
My rationale is so cruft is not accumulated; particularly since at this point it’ll be like “what does this do?” “oh, doesn’t do anything anymore but it’s always been there”.
Git will take care of keeping the history for us 
I’m with Daniel, mostly because I’m the one maintaining the travis.yml file and after a few months it always gets crazy and we need to go back and clean it