maas should tell cloud-init not to try metadata service on every boot

Bug #1506991 reported by Scott Moser on 2015-10-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Blake Rouse
falkor
Won't Fix
Undecided
David Britton

Bug Description

on reboot of installed node, cloud-init will attempt to hit the metadata service as if it were the first boot.
this is to detect 'new instance', in order to do first instance setup. If maas service is unavailable then the node will have issues on boot.

'manual_cache_clean' is the cloud-config syntax that says to not go looking. the user must clean the cache manually.

So, 2 ways of doing this.
a.) cloud-init maas datasource can assume that.
b.) maas provide that setting to cloud-init via the install (as it sets some other cloud-init settings now).

Related branches

Changed in maas:
milestone: none → 1.9.0
importance: Undecided → Critical
Changed in maas:
status: New → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: In Progress → Fix Committed
Adam Collard (adam-collard) wrote :

@David

What needs to be done in Falkor for this?

Changed in falkor:
assignee: nobody → David Britton (davidpbritton)
status: New → Incomplete
Changed in falkor:
status: Incomplete → Won't Fix
Changed in maas:
status: Fix Committed → Fix Released
no longer affects: maas/1.8
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers