Hide Forgot
Description of problem: Not clear whether this issue needs to be called a bug, raising this bug to track the Master/Slave RHUI setup issues. For master/slave setups we need to use the following server url to add the RH repos on the slave RHUA nodes. Instead of just https://hostname.example.com we need to use https://hostname.example.com/pulp/repos The issues faced because of using https://hostname.example.com/pulp/repo 1) On Pulp-Server : we have /var/lib/pulp/repos/pulp/repos as the directory structure [root@dhcp201-198 os]# pwd /var/lib/pulp/repos/pulp/repos/content/dist/rhel/rhui/server-6/releases/6Server/x86_64/os 2) On Pulp-CDS : we have /var/lib/pulp-cds/repos/pulp/repos as the directory structure 3) Using this link will cause the slave's clients from failing to fetch the content, due to dual /pulp/repos 4) Creating a soft link or changing the alias in pulp-cds.conf file solved the issue. [root@dhcp201-150 repos]# ln -s ./pulp/repos/content content [root@dhcp201-150 repos]# ls content pulp Version-Release number of selected component (if applicable): pulp - 211 and rhui 2.0.40 How reproducible: By setting up a master/slave setup. Steps to Reproduce: 1. 2. 3. Actual results: slave's clients fails to fetch content. Expected results: Slaves' clients should be able to fetch the contents Additional info:
Released in RHUI 2.0.2