Cannot find cloud-init datasource error when adding a node through a new rackd controller

[Rong Shen]

Hello,

My maas version is 2.3. I found this error was considered a bug in previous versions. So I decide to report there to see if it is still an issue.

We added a new rackd controller following instructions on the website. This rackd controller is in a different network, and physically located in a different place. For example, regiond controller is in 192.168.2.0 network and in location A, rackd controller is in 10.77.140.0 network and in location B.

After set it up and wait for image synced, we started booting nodes through the new added rackd controller. However, nodes are not listed as machines in maas UI and we saw this error during boot up:

| Can not apply stage final, no datasource found! Likely bad things to
come!
| ------------------------------------------------------------
| Traceback (most recent call last):
| File "usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 484, in main_modules
| init.fetch(existing="trust")
| File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 348, in fetch
| return self._get_data_source(existing=existing)
| File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 258, in _get_data_source
| pkg_list, self.reporter)
| File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 455, in find_source
| raise DataSourceNotFoundException(msg)
| cloudinit.sources.DataSourceNotFoundException: Did not find any data source, searched classes: ()
| ------------------------------------------------------------

Would like to see if it is related to a bug before that related to multiple VLANs.

Here is the output package list

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=============================================
un maas <none> <none> (no description available)
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Rack Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

Attached log files below

Thank you!
Rong

[Rong Shen (rongshen)]

rackd log

[Lee Trager (ltrager)]

Currently in MAAS machines being booted must have network access to both the rack and region controller. Do the machines booting have access to both?

MAAS 2.5 will proxy all connections from the machine through the rack controller so the machine will no longer need direct access to the region.

[Rong Shen (rongshen)]

Thank you for the reply!

I don't think they have same network access. They are in different LAN. We probably will set up a different MAAS server in that LAN.

Looking forward to MAAS 2.5, it will definitely solve our issue here.

Thank you and we can close this bug.