Why would this happen during commission?
2019-10-26T05:39:24+00:00 maas-enlisting-node cloud-init[2214]: Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: Reading package lists...
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: Reading package lists...
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: Building dependency tree...
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: Reading state information...
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: Package ipmitool is not available, but is referred to by another package.
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: This may mean that the package is missing, has been obsoleted, or
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: is only available from another source
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: E: Package 'ipmitool' has no installation candidate
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: E: Unable to locate package sshpass
2019-10-26T05:39:25+00:00 maas-enlisting-node cloud-init[2214]: E: Unable to locate package jq
Deploying images work fine. Running machines work fine. Commissioning machines don’t work.
This environment is nearly air-gapped. During commission, there’s a call to a snap repo, which fails. Does that have to succeed in order for commissioning machines to succeed?