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.
DescriptionPradeep Kumar Surisetty
2016-04-20 08:29:33 UTC
Description of problem:
1) Registered couple of vm's as capsules to satellite server.
2) Each VM has 2 nics.
Eth0 : NAT bridge ( which cant be accessed by external satellite server).
Eth1: 10G NIC. Which is accessible to satellite server
3) After registering either capsule/hosts to satellite
"Hammer capsule list" or "hammer host list" lists first nic associated to each node.
For ex:
hammer -u admin -p changeme host list
4 | vmcapsule01.redhat.com | RedHat 7.2 | | 192.168.122.110 | 52:54:00:35:bc:2c
Above listed IP is not accessible to satellite as this is with NATed bridge.
It would be challenging for user to track all these ipts. Good to list IP's which satellite can acces capsules/hosts
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
In Sat 6.1 there's no easy way of determining the primary interfaces or swapping it with any additional interface. In next version though user is able to select which interface is primary and then the IP of primary interface is being displayed. When a host registers by itself (so not created by provisioning), we try to detect primary interface, physical interfaces have higher priority so it should work out of the box.
We can't really detect whether the IP is truly reachable from Satellite, the IP might be from some existing subnet range but that does not mean it's on the same subnet.
So I suggest verifying this BZ with 6.2, it should not need any code changes.