canonical-kubernetes will fail to come up on bare metal

[Mark W Wenning]

We found this while setting up a demo on a Quanta cluster, I am not sure if it does it on other hardware:
1. Set up maas 2.0 and juju 2.0 rc2 on the Xenial system, enlist at least 11 (!) machines.
2. Attempt to launch canonical-kubernetes bundle.
3. Bundle will never come up, 3 machines will attempt to bring up trusty and hang.

Workaround: add the phrase 'mei-me.disable_msi=1' to the global kernel parameters on the MaaS Settings screen.

[Brendan Donegan (brendan-donegan)]

@Mark, if you could attempt this again, can you tar and attach all of /var/log/maas/ from the MAAS server? Also from your comment it looks like you had a workaround so maybe it's a hardware issue?

[Andres Rodriguez (andreserl)]

Did the machines in Maas transition to deployed?

[Anastasia (anastasia-macmood)]

This looks like a MAAS-only bug.

If there was a problem on Juju side, we have fixed it - I can deploy canonical-kubernetes on AWS with Juju 2.1-rc2: https://pastebin.canonical.com/179794/

[Björn Tillenius (bjornt)]

I'm closing this bug since we haven't gotten any more information for years. If it's still an issue, please reopen this bug with more debug information.