Plugins » Discovery

After discovered host is converted to Managed, associated NICs still have their associations set to the original record from the database (Host::Discovered), which led the host.managed? statement fail in tftp_ready? method in TFTP orchestration. This led to TFTP orchestration to be skipped completely, so I added a statement to set the appropriate assotiation explicitly during auto provisioning.

This is a regression and I cannot find the root cause of this, it worked previously. We have reports that both 1.14 and 1.15 are broken.

I see the exact same behavior (no TFTP configs getting generated, no log/debug entries, reboot into FDI again) when provisioning a discovered host directly via API. The JSON i send to the API endpoint api/v2/discovered_hosts/:id looks like this:

{'discovered_host': {'operatingsystem_id': 3, 'root_pass': 'XXXXXX', 'managed': 1, 'ptable_id': 52, 
                     'medium_id': 4, 'subnet_id': 2, 'ip': '10.XXX.XXX.85', 'provision_method': 'build', 
                     'enabled': 1, 'hostgroup_id': 7, 'mac': 'XX:XX:XX:XX:XX:XX', 'architecture_id': 1, 
                     'build': 1, 'domain_id': 2, 'name': u'macXXXXXXXXXXXX'}
}

I found out that sending a request to api/hosts/:id/rebuild_config does finally generate the TFTP config. This indicates that something is wrong in the object conversion from Discovered Host to Managed Host. For the time being i am using this second API request as a workaround.