Today I found the deployment works for both B/D on these two systems with the
following kernels:
* B - 4.15.0-72
* D - 5.0.0-37
I think this somewhat related to the infrastructure issue that we encountered
two days ago (gateway down)
I will close this bug as this is for maas deployment.
Di
But on another ThunderX everything goes fine.
https://pastebin.ubuntu.com/p/gkfHvc7Wxn/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854920
Title:
Unable to deploy ThunderX ARM64 nod
lspci has different outputs on 4.15.0-70.79 and 4.15.0-72.81
This is the output of 70.79
https://pastebin.ubuntu.com/p/J9H6s9MR5J/
This is the output of 72.81
https://pastebin.ubuntu.com/p/cMSG3SRkvW/
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Bionic Deployment works on Moonshot node (ms10-34-mcdivittB0-kernel) on
the same hyper-mass server.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854920
Title:
Unable to deploy Thunder
Attachment is the output from MAAS UI, but this is for Bionic.
** Attachment added: "maas.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854920/+attachment/5309519/+files/maas.log
** Description changed:
The deployment for these ThunderX ARM64 nodes (wright-kernel /
starmie-ke
5 matches
Mail list logo
