Bug #9882
closedhammer host create with no compute profile or attributes results in "mac value is blank"
Description
When creating a host on a compute resource with no compute attributes or compute profile, you get the error "mac value is blank":
# hammer -u … -p … compute-resource info --id 22 | grep -i provider Provider: Libvirt # hammer -u … -p … host create \ --architecture-id 37 \ --domain-id 42 \ --environment-id 81 \ --location-id 258 \ --mac 'a9:1a:9a:70:be:60' \ --medium-id 32 \ --name 'AkqttNPO2' \ --operatingsystem-id 43 \ --organization-id 259 \ --partition-table-id 28 \ --puppet-proxy-id 1 \ --root-pass 'changeme' \ --compute-resource-id 22 Could not create the host: mac value is blank!
Foreman detects whether the host is compute or not based on the presence of the compute_resource_id and some attributes to create it with.
Updated by Dominic Cleal almost 10 years ago
- Description updated (diff)
- Category set to API
- Subject changed from hammer host create with mac results in "mac value is blank" to hammer host create with no compute profile or attributes results in "mac value is blank"
Updated by Marek Hulán over 9 years ago
- Status changed from Ready For Testing to Resolved
I believe this was caused by missing compute attributes that would specify at least one interface which caused fog to create a vm without any nic so Foreman couldn't load a mac. To create the host properly on libvirt compute resource, you have to specify --interface argument as well so it will create at least one interface, e.g.
# hammer -u … -p … host create \ --architecture-id 37 \ --domain-id 42 \ --environment-id 81 \ --location-id 258 \ --mac 'a9:1a:9a:70:be:60' \ --medium-id 32 \ --name 'AkqttNPO2' \ --operatingsystem-id 43 \ --organization-id 259 \ --partition-table-id 28 \ --puppet-proxy-id 1 \ --root-pass 'changeme' \ --compute-resource-id 22 \ --interface type=network # <--- this is important
After we match interfaces with compute interface (introduced in 1.8) this is no longer an issue. If you see this behaviour on Foreman 1.8+, please reopen the issue.