Goferd connection issues in a server with two IP addresses

Support
,
1

Problem:
I have a server that serves as dev and UAT box.

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:50:56:a0:34:f8 brd ff:ff:ff:ff:ff:ff
    inet 10.2.20.14/24 brd 10.2.20.255 scope global eth0
    inet 10.2.20.13/24 brd 10.2.20.255 scope global secondary eth0:0
    inet6 fe80::250:56ff:fea0:34f8/64 scope link
       valid_lft forever preferred_lft forever

As can be seen there are two different IP addresses.

When I registered this server with my katello server, the web interface picked up the IP address 10.2.20.13.

But qpid picked up the IP address 10.2.20.14.

2018-04-27 03:53:44.718357 -0400 ROUTER_CORE (info) Link Route Activated 'linkRoute/3' on connection broker
2018-05-02 13:11:01.91599 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26241
2018-05-02 13:11:01.920017 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26242
2018-05-02 13:18:26.545924 -0400 SERVER (info) Connection from 10.2.20.14:26242 (to 0.0.0.0:5647) failed: amqp:resource-limit-exceeded local-idle-timeout expired
2018-05-02 13:18:36.649073 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26357
2018-05-02 13:18:36.726960 -0400 SERVER (info) Connection from 10.2.20.14:26357 (to 0.0.0.0:5647) failed: amqp:connection:framing-error SSL Failure: error:140940E5:SSL routines:ssl3_read_bytes:ssl handshake failure
2018-05-02 13:18:46.818657 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26363
2018-05-02 13:23:14.212425 -0400 SERVER (info) Connection from 10.2.20.14:26363 (to 0.0.0.0:5647) failed: proton:io Connection reset by peer - disconnected :5672 (SSL Failure: Unknown error)
2018-05-02 13:23:36.644086 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26455
2018-05-02 13:23:37.395321 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from 10.2.20.14:26457

As a result of this, in the web interface the host status is yellow denoting warning status. It cannot calculate the errata applicability as well.

Expected outcome:
The web interface (I am assuming foreman/katello) should pick up the same IP address as qpid picks up or vice versa.

Foreman and Proxy versions:

On content host, version of katellio is
katello-agent-3.1.0-1.el6.noarch

On Katello server:

foreman-selinux-1.16.1-1.el7.noarch
foreman-release-scl-3-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch
foreman-postgresql-1.16.1-1.el7.noarch
foreman-release-1.16.1-1.el7.noarch
foreman-debug-1.16.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-5.el7.noarch
foreman-1.16.1-1.el7.noarch
foreman-compute-1.16.1-1.el7.noarch
foreman-cli-1.16.1-1.el7.noarch
foreman-installer-katello-3.5.1.1-1.el7.noarch
foreman-proxy-1.16.1-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.2.4-1.fm1_16.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-2.el7.noarch
tfm-rubygem-foreman-tasks-0.10.9-1.fm1_16.el7.noarch
tfm-rubygem-foreman_docker-3.2.1-1.fm1_16.el7.noarch
foreman-installer-1.16.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.12-1.fm1_16.el7.noarch

Foreman and Proxy plugin versions:

Other relevant data:
Let me know what I can upload.

Screenshot from the web interface:

Screenshot%20from%202018-05-03%2023-37-58

2

I changed the host parameter in /etc/gofer/agent.conf in the content host and used the IP address 10.2.20.13. Restarted goferd in content host and katello-service in the katello server. But it still continued to pick up 10.2.20.14.

What can I do to reconcile this difference?

3

I feel like that if I can manipulate the ip address that foreman has picked up then I can fix this. FWIW,

hammer host info --name hostname shows the secondary IP address that comes from eth0:0. But the primary IP address of the content host comes from eth0.

[root@content-host ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0:0
DEVICE=eth0:0
ONBOOT=yes
USERCTL=no
BOOTPROTO=static
NETMASK=255.255.255.0
IPADDR=10.2.20.13
PEERDNS=no

[root@content-host ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
USERCTL=no
BOOTPROTO=static
NETMASK=255.255.255.0
IPADDR=10.2.20.14
PEERDNS=no

[root@content-host ~]#

Is there any way to tell subscription manager to pick up 10.2.20.14 during registration?