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.
Bug 1206615 - Kickstart template on rhel5 includes --device=MAC
Summary: Kickstart template on rhel5 includes --device=MAC
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Og Maciel
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-27 14:27 UTC by Justin Sherrill
Modified: 2017-02-23 20:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 14:02:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
cookies (105.45 KB, image/png)
2015-05-14 11:22 UTC, Tazim Kolhar 		no flags Details
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10614 0 None None None 2016-04-22 16:42:38 UTC

Description Justin Sherrill 2015-03-27 14:27:49 UTC 
Description of problem:

The Satellite Kickstart Default provisioning template will render the following:

network --bootproto dhcp --device=52:54:00:35:17:60 --hostname moe-59-64.lexample.com

However rhel5 does not seem to support specifying the mac address with --device, only rhle6 and newer.  This causes rhel5 provisioning to fail with an error "The Following network interface <MAC> does not exist"



Version-Release number of selected component (if applicable):
katello-2.2.0.8-1.el7sat.noarch
katello-ca-consumer-ibm-x3250m4-06.lab.eng.rdu2.redhat.com-1.0-1.noarch
katello-certs-tools-2.2.1-1.el7sat.noarch
katello-common-2.2.0.8-1.el7sat.noarch
katello-debug-2.2.0.8-1.el7sat.noarch
katello-default-ca-1.0-1.noarch
katello-installer-2.3.5-1.el7sat.noarch
katello-installer-base-2.3.5-1.el7sat.noarch
katello-server-ca-1.0-1.noarch


The relevant line form the snippet:

network --bootproto <%= dhcp ? 'dhcp' : "static --ip=#{@host.ip} --netmask=#{subnet.mask} --gateway=#{subnet.gateway} --nameserver=#{[subnet.dns_primary, subnet.dns_secondary].select(&:present?).join(',')}" %> --device=<%= @host.mac -%> --hostname <%= @host %>


How reproducible:
Always

Steps to Reproduce:
1. Attempt to provision a rhel5 machine

Actual results:
Fails with error "The Following network interface <MAC> does not exist"


Expected results:
Successful provision


Additional info:

The foreman kickstart default for rhel does not seem to have the same networking line (and does not include a --device reference), but I'm not sure the history behind this.
Comment 2 Justin Sherrill 2015-05-07 14:23:19 UTC 
This was resolved as part of https://bugzilla.redhat.com/show_bug.cgi?id=1186321
Comment 3 Tazim Kolhar 2015-05-12 09:32:33 UTC 
hi

please provide verification steps

thanks
Comment 4 Justin Sherrill 2015-05-12 14:53:14 UTC 
Tazim,

To test you could either:

1.  Examine the Satellite kickstart templates and verify that --device= is not included on the network line

or (preferably)

2.  Attempt to sync and provision a rhel5 server following the normal provisioning methods.
Comment 5 Tazim Kolhar 2015-05-14 11:22:43 UTC 
Created attachment 1025355 [details]
cookies
Comment 6 Tazim Kolhar 2015-05-15 07:41:12 UTC 
FAILEDQA:

# rpm -qa | grep foreman
foreman-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
foreman-libvirt-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-vmware-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-compute-1.7.2.21-1.el7sat.noarch
foreman-debug-1.7.2.21-1.el7sat.noarch




steps

In Satellite kickstart template
network --bootproto <%= dhcp ? 'dhcp' : "static --ip=#{@host.ip} --netmask=#{subnet.mask} --gateway=#{subnet.gateway} --nameserver=#{[subnet.dns_primary, subnet.dns_secondary].select(&:present?).join(',')}" %> --device=<%= @host.mac -%> --hostname <%= @host %>
rootpw --iscrypted <%= root_pass %>

--device=  is included on the network line
Comment 7 Justin Sherrill 2015-05-15 13:02:22 UTC 
Actually it looks like the foreman-templates do now have a --device=mac option, although in 1.7 they didn't.  It looks like this was introduced in c0fe869d28f3a79ba65bc7d433c15c9d548b0baa in upstream foreman and that was brought into katello at some point.
Comment 8 Justin Sherrill 2015-05-26 15:17:51 UTC 
Created redmine issue http://projects.theforeman.org/issues/10614 from this bug
Comment 10 Tazim Kolhar 2015-06-04 10:08:19 UTC 
FAILEDQA:

# rpm -qa  | grep foreman
foreman-compute-1.7.2.26-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.13-1.el6_6sat.noarch
foreman-vmware-1.7.2.26-1.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
foreman-postgresql-1.7.2.26-1.el6_6sat.noarch
foreman-libvirt-1.7.2.26-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.7-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el6_6sat.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
foreman-debug-1.7.2.26-1.el6_6sat.noarch
foreman-ovirt-1.7.2.26-1.el6_6sat.noarch
foreman-gce-1.7.2.26-1.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.15-1.el6_6sat.noarch
foreman-proxy-1.7.2.5-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch
intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
ruby193-rubygem-foreman_docker-1.2.0.14-1.el6_6sat.noarch
intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch
foreman-1.7.2.26-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch



steps:
network --bootproto <%= dhcp ? 'dhcp' : "static --ip=#{@host.ip} --netmask=#{subnet.mask} --gateway=#{subnet.gateway} --nameserver=#{[subnet.dns_primary, subnet.dns_secondary].select(&:present?).join(',')}" %> --hostname <%= @host %><%= os_major >= 6 ? " --device=#{@host.mac}" : '' -%>

--device=  is included on the network line
Comment 11 Justin Sherrill 2015-06-04 14:23:28 UTC 
Tazim,

Did you actually test a rendered kickstart?  Or just look at the template?  The 'fix' was to update the template to only render the --device part for rhel 6 and higher.

-Justin
Comment 12 Tazim Kolhar 2015-06-09 09:25:09 UTC 
Hi,

     I had rendered a kickstart template
     for example i logged in to sat6 -> Provisioning template
     then under the template render I checked --device part

     does that makes sense ?  

Thanks and Regards,
Tazim
Comment 13 Justin Sherrill 2015-06-09 13:27:27 UTC 
Tazim,

Are you sure you were testing an el5 provisioning?  That is an RHEL 5 operating system was selected?

When I do it on rhel 5:

network --bootproto dhcp --hostname zoom.example.com


When i do it for rhel 6:

network --bootproto dhcp --hostname testhost.example.com --device=3c:97:0e:e9:27:09
Comment 14 Og Maciel 2015-06-09 20:46:03 UTC 
For a provisioned RHEL 5.11 x86_64 system the template shows:

network --bootproto dhcp --hostname schemp-5-11-large.xxx.yyy.com

For a provisioned RHEL 7.2 x86_64 system the template shows:

network --bootproto dhcp --hostname curly-7-1.xxx.yyy.com --device=52:54:00:d1:04:b1

This is now verified on latest version of Satellite 6.1.0 SNAP 7 Compose 2
Comment 15 Bryan Kearney 2015-08-11 13:27:58 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 16 Bryan Kearney 2015-08-12 14:02:14 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.