airship/drydock
Code Issues Proposed changes

Put bootdata init back in place

Browse Source
This commit is contained in:
Scott Hussey 2017-06-22 18:58:27 -05:00
parent 14089f60d7
commit 3ababfbbd0
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
drydock_provisioner/drivers/node/maasdriver/driver.py
View File

@ -1136,7 +1136,15 @@ class MaasTaskRunner(drivers.DriverTaskRunner):
self.logger.warning("Error acquiring node %s, skipping" % n)
failed = True
continue
# Need to create bootdata keys for all the nodes being deployed
# TODO this should be in the orchestrator
node = site_design.get_baremetal_node(n)
data_key = str(uuid.uuid4())
self.state_manager.set_bootdata_key(n, self.task.design_id, data_key)
node.owner_data['bootdata_key'] = data_key
self.logger.debug("Configured bootdata for node %s" % (n))
# Set owner data in MaaS
try:
self.logger.info("Setting node %s owner data." % n)