Comment 6 for bug 1754493

Revision history for this message
Andres Rodriguez (andreserl) wrote :

So I just did a quick test in a container:

1. sudo apt-get install maas
2. sudo maas init
3. waiting for images to sync while tailing logs
4. Saw this:

==> /var/log/maas/maas.log <==
Apr 3 18:26:17 maas-bionic maas.bootresources: [info] Finished importing of boot images from 1 source(s).

==> /var/log/maas/regiond.log <==
2018-04-03 18:26:17 maasserver.clusterrpc.boot_images: [info] Rack controller (fbcqp7) did not import boot resources; it is not connected to the region at this time.

5. Went to the UI to check region/rack connection, showed as everything connected.
6. After a few mins, the rack controller disconnected, the UI 'Controllers' page went blank.
7. While 6 happened, I saw this:

2018-04-03 18:26:28 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-03 18:26:59 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-03 18:27:29 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

==> /var/log/maas/maas.log <==
Apr 3 18:27:59 maas-bionic maas.import-images: [info] Starting rack boot image import
Apr 3 18:27:59 maas-bionic maas.import-images: [info] Downloading image descriptions from http://localhost:5240/MAAS/images-stream/streams/v1/index.json