I have maas configured for dhcp but it seems the instances can’t find the llpd package. This smells like a networking issue somehow??
Here you can see my network settings. The .1/32 is my juniper router. The .110/32 is my maas server.
I have it configured as a proxy.
The error is:
" E: Unable to locate package lldpd "
What’s the output of the following command?
maas $ADMIN package-repositories read
My bad here you go, Alex:
root@orion:/home/john# maas maas_admin package-repositories read
Success.
Machine-readable output follows:
[
{
"name": "main_archive",
"url": "http://archive.ubuntu.com/ubuntu",
"distributions": [],
"disabled_pockets": [],
"disabled_components": [],
"disable_sources": true,
"components": [],
"arches": [
"amd64",
"i386"
],
"key": "",
"enabled": true,
"id": 1,
"resource_uri": "/MAAS/api/2.0/package-repositories/1/"
},
{
"name": "ports_archive",
"url": "http://ports.ubuntu.com/ubuntu-ports",
"distributions": [],
"disabled_pockets": [],
"disabled_components": [],
"disable_sources": true,
"components": [],
"arches": [
"armhf",
"arm64",
"ppc64el",
"s390x"
],
"key": "",
"enabled": true,
"id": 2,
"resource_uri": "/MAAS/api/2.0/package-repositories/2/"
}
]
Hey, Alex - also would you happen to know how to retrieve the default username / password for ubuntu images after maas commissioning?
assuming it’s an official Ubuntu image, the user is ubuntu, and it doesn’t have a password. MAAS injects the SSH keys of the user that deployed it.
about the lldpd package, your repositories look standard.
Are you using a APT proxy? Often this error is caused by an incomplete mirror, as this package is in universe and not main
At Alex, side question - is there a way to commission a machine over PXE but automatically keep it powered on for ssh and also not configure bmc etc?
I can see these options on commissioning an existing registered Machine from UI but not sure how to do it as a preset definition before pxe boot.