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 1278564 - Existing foreman hosts won't recognize updates to the capsules set in the targeted subnet. [NEEDINFO]
Summary: Existing foreman hosts won't recognize updates to the capsules set in the tar...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 19:47 UTC by Dylan Gross
Modified: 2020-05-14 15:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-30 14:24:15 UTC
Target Upstream Version:
Embargoed:
bstephen: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2041653 0 None None None Never

Description Dylan Gross 2015-11-05 19:47:35 UTC 
Description of problem:

   If the Capsule information has changed since a new foreman host was created, it will not get reflected in the host (unless the host is deleted/re-created, or the MAC address is modified).

 
Version-Release number of selected component (if applicable):

   Observed on Satellite v6.1.2


How reproducible:   Always.

Steps to Reproduce:
1.  Incorrectly, leave the TFTP Capsule as "None" for the desired subnet
2.  Create a "New Host" under the "Hosts"... "All Hosts"
3.  Observe that /var/lib/tftpboot/pxelinux.cfg/01-<mac> is (correctly) not created

4.  Remedy the TFTP Capsule for the subnet by selecting the appropriate TFTP capsule.

5.  Edit the host under "Hosts"..."All Hosts" and then "Submit" again.  

6.  Observe that the /var/lib/tftpboot/pxelinux.cfg/01-<mac> is still not set, even though the TFTP capsule for the subnet is set properly.


Actual results:

   After correcting the TFTP Capsule for the subnet, editing and submitting the host did not create the TFTP entry for the host to be built.


Expected results:

   Editing and submitting the host again would recognize that the current capsule configuration for the subnet and appropriately create the TFTP entry.

Additional info:

   Note:  Easily worked around
    1.  Deleting and re-creating the "New Host" will correctly pull the TFTP capsule from the Subnet info.
    -- or --
    2.  Changing the "MAC Address" on the "Network" tab of the host when editing, before submitting, will also force it to recognize the change to the TFTP capsule for the subnet.   (Changing the IP Address does not appear to do so).
Comment 3 Bryan Kearney 2016-07-08 20:42:00 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 5 Ohad Levy 2016-11-30 14:24:15 UTC 
Satellite wont update the host tftp entry unless its in build mode, please make sure its enabled.

another easier workaround is simply to click on rebuild - which will trigger validation (including tftp) to check the host is ready for provisioning.

I believe this is a user error - please reopen i miss understood.
Note You need to log in before you can comment on or make changes to this bug.