Description of problem: 1. 'rhui haproxy reinstall' says there is no registered isntances with the given hostname, but there is one 2. if to feed 'rhui haproxy reinstall' with cds hostname it will be reinstalled Version-Release number of selected component (if applicable): iso 20161220 How reproducible: always Steps to Reproduce: 1. rhui haproxy list to insure there is one 2. rhui haproxy reinstall hostname 3. msg: There are no registered instances with that hostname. Actual results: >> [root@rhua ~]# rhui haproxy list -= RHUI HAProxy Load-balancers =- Hostname: hap01.example.com SSH Username: ec2-user SSH Private Key: /root/.ssh/id_rsa_rhua ------------------------------------------------------------------------------ >> [root@rhua ~]# rhui haproxy reinstall hap01.example.com --help usage: rhui haproxy reinstall [-h] hostname positional arguments: hostname The hostname of the instance to reinstall on; this instance must be registered already. optional arguments: -h, --help show this help message and exit >>[root@rhua ~]# rhui haproxy reinstall hap01.example.com There are no registered instances with that hostname. >> rhui haproxy reinstall cds01.example.com Checking that the RHUA services are reachable from the instance... [ec2-user.com] sudo: yum install -d 0 -e 0 -y nc [ec2-user.com] sudo: nc rhua.example.com 8140 < /dev/null Done. Installing Puppet on the HAProxy Load-balancer... [ec2-user.com] sudo: yum install -y puppet [ec2-user.com] sudo: puppet config set server rhua.example.com Done. [ec2-user.com] sudo: mkdir -p /etc/facter/facts.d [ec2-user.com] put: /etc/puppet/rhui-secrets/rhui-custom-facts.json -> /etc/facter/facts.d/rhui-custom-facts.json Setting up certificates... [ec2-user.com] run: echo $HOME [ec2-user.com] sudo: puppet config print certname [ec2-user.com] sudo: rm -rf /var/lib/puppet/ssl [ec2-user.com] sudo: mkdir -p /var/lib/puppet/ssl/{certs,private_keys} [localhost] local: puppet cert clean cds01.example.com [ec2-user.com] put: /var/lib/puppet/ssl/certs/ca.pem -> /home/ec2-user/ca.pem [ec2-user.com] sudo: mv /home/ec2-user/ca.pem /var/lib/puppet/ssl/certs/ca.pem [ec2-user.com] sudo: puppet agent --onetime --detailed-exitcodes --no-daemonize --no-usecacheonfailure [ec2-user.com] run: echo $HOME [ec2-user.com] sudo: cp -r /var/lib/puppet/ssl/certificate_requests/cds01.example.com.pem /home/ec2-user/cds01.example.com.pem [ec2-user.com] sudo: chown -R $USER /home/ec2-user/cds01.example.com.pem [ec2-user.com] download: /var/lib/puppet/ssl/ca/requests/cds01.example.com.pem <- /home/ec2-user/cds01.example.com.pem Warning: Local file /var/lib/puppet/ssl/ca/requests/cds01.example.com.pem already exists and is being overwritten. [ec2-user.com] sudo: rm -rf /home/ec2-user/cds01.example.com.pem [localhost] local: puppet cert sign cds01.example.com Done. Installing and configuring the HAProxy Load-balancer... [ec2-user.com] sudo: puppet agent --onetime --detailed-exitcodes --no-daemonize --no-usecacheonfailure Done. Ensuring that Apache and Crane are available... [localhost] local: yum install -y nc [localhost] local: nc cds01.example.com 443 < /dev/null [localhost] local: nc cds01.example.com 5000 < /dev/null Done.
There should be a check in this argument that verifies that the target is an haproxy. Should not allow reinstall of haproxy against an already defined CDS which is not meant to be the haproxy.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0149