Commissioning failure in 1 region + 2 rack environment

Users
,
1

Hi,

[environment]

I deployed MAAS 3.2 as the following design by snapcraft on Ubuntu 20.04.

  • region + rack-1: network 192.168.10.0/24
  • rack-2: network 192.168.100.0/24
    • This rack is connected to the region.

I allowed ping and the following TCP connection ports between the two networks.

[Issue]

I can commission & deploy machines in rack-1. But commissioning was failed in rack-2.

In the failed case, the following error was appeared in the console of machine. I confirmed it by BMC’s remote console.

cloud-init[2305]: Can not apply stage config, no datasource found! Likely bad things to come!
---------------------------------------------------------------
Taceback (most recent call last):
[...]
cloudinit.sources.DataSouurceNotFoundException: Did not find any data source ,searched classes:

---------------------------------------------------------------
Can not apply stage final, no datasource found! Likely bad things to come.
---------------------------------------------------------------
Taceback (most recent call last):
[...]
cloudinit.sources.DataSouurceNotFoundException: Did not find any data source ,searched classes:

---------------------------------------------------------------

And, the following log was appeared in rack-2’s rackd.log. 192.168.100.63 is the IP address of the failed machine.

2022-11-14 06:58:07 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 192.168.100.63
2022-11-14 06:58:08 provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-3c:ec:ef:6d:55:c4 requested by 192.168.100.63
2022-11-14 06:58:09 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/generic/focal/stable/boot-kernel requested by 192.168.100.63
2022-11-14 06:58:10 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/generic/focal/stable/boot-initrd requested by 192.168.100.63
2022-11-14 06:58:36 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/generic/focal/stable/squashfs requested by 192.168.100.63

Is there anything I should try/investigate?

[Remarks]

The following topic says that restarting region solves the similar issue. I tried it, but this it didn’t solve this issue.

2

I resolved this issue by my self.

The root cause is that I hadn’t allowed connections on the DNS port(53) between the following two networks. The DNS port is not written in " How to set up a firewall for MAAS" page: https://maas.io/docs/how-to-secure-maas

  • region + rack-1: 192.168.10.14/24, network 192.168.10.0/24
  • rack-2: 192.168.100.14/24, network 192.168.100.0/24
    • This rack is connected to the region.

I found that “Temporary failure in name resolution” error was printed on the terminal in the commissioning process.

Machines access to the metadata by using name resolution.

e.g. http://192-168-100-0--24.maas-internal:5248/MAAS/metadata/…

But, rack-2 couldn’t resolve “192-168-100-0–24.maas-internal”.

$ nslookup
> server 192.168.100.14
Default server: 192.168.100.14
Address: 192.168.100.14#53
> 192-168-100-0--24.maas-internal
Server:         192.168.100.14
Address:        192.168.100.14#53

** server can't find 192-168-100-0--24.maas-internal: SERVFAIL

After I allowed connections on the DNS port(53) between the two networks, rack-2 can resolve it.
And this issue didn’t occur after that.

$ nslookup
> server 192.168.100.14
Default server: 192.168.100.14
Address: 192.168.100.14#53
> 192-168-100-0--24.maas-internal
Server:         192.168.100.14
Address:        192.168.100.14#53

Non-authoritative answer:
Name:   192-168-100-0--24.maas-internal
Address: 192.168.100.14
3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.