Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Satellite6 does not honour the mac address specified for provisioning via compute-resource
Version-Release number of selected component (if applicable): 6.2.9
How reproducible: Always
Steps to Reproduce:
A) Through hammer:
1) hammer host create --hostgroup rhev --name host4 --mac 52:54:00:e4:15:26 --managed true --build true --location Pune --organization-id 1 --enabled true --compute-profile rhev --compute-resource rhevm
B) Through api:
curl -H "Accept:application/json,version=2" -H "Content-Type:application/json" -X POST -u admin:redhat -k -d "{\"host\":{\"organization_id\":1,\"enabled\":1,\"build\":1,\"hostgroup_id\":2,\"compute_profile_name\":\"rhev\",\"compute_resource_name\":\"rhevm\",\"owner_id\":null,\"interfaces_attributes\": [ {\"provision\":1,\"domain_id\":1,\"mac\":\"00:50:56:91:7c:41\",\"primary\":1,\"type\":\"Nic::Managed\",\"ip\":\"192.168.100.99\",\"managed\":1,\"subnet_id\":1} ],\"name\":\"test123\",\"managed\":1,\"location_id\":2,\"owner_type\":\"User\",\"overwrite\":0}}" https://satellite.example.com/api/hosts
Actual results:
Vm gets populated with a different MAC address.
Expected results:
VM should be built with same MAC address as provided on hammer or api.
Additional info:
1) I am using rhevm 4.0.
2) This issue is also observed at the customer end where vmware is being used.
3) This works as expected when provisioned through webui
Just quick update - we don't see this as bug, virtualization/cloud workflow is based on fact that compute resource generates MAC address and Satellite reads that. This RFE is on our backlog, no plans for now.
Comment 4Lukáš Hellebrandt
2018-07-27 10:42:04 UTC
I can also reproduce this in Sat 6.4 using WebUI, using both API v3 and v4.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Description of problem: Satellite6 does not honour the mac address specified for provisioning via compute-resource Version-Release number of selected component (if applicable): 6.2.9 How reproducible: Always Steps to Reproduce: A) Through hammer: 1) hammer host create --hostgroup rhev --name host4 --mac 52:54:00:e4:15:26 --managed true --build true --location Pune --organization-id 1 --enabled true --compute-profile rhev --compute-resource rhevm B) Through api: curl -H "Accept:application/json,version=2" -H "Content-Type:application/json" -X POST -u admin:redhat -k -d "{\"host\":{\"organization_id\":1,\"enabled\":1,\"build\":1,\"hostgroup_id\":2,\"compute_profile_name\":\"rhev\",\"compute_resource_name\":\"rhevm\",\"owner_id\":null,\"interfaces_attributes\": [ {\"provision\":1,\"domain_id\":1,\"mac\":\"00:50:56:91:7c:41\",\"primary\":1,\"type\":\"Nic::Managed\",\"ip\":\"192.168.100.99\",\"managed\":1,\"subnet_id\":1} ],\"name\":\"test123\",\"managed\":1,\"location_id\":2,\"owner_type\":\"User\",\"overwrite\":0}}" https://satellite.example.com/api/hosts Actual results: Vm gets populated with a different MAC address. Expected results: VM should be built with same MAC address as provided on hammer or api. Additional info: 1) I am using rhevm 4.0. 2) This issue is also observed at the customer end where vmware is being used. 3) This works as expected when provisioned through webui