We want to automate the process of setting up online repositories for Red Hat Ceph Storage on ubuntu nodes. The manual steps are currently described here: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/installation_guide_for_ubuntu/prerequisites#online_repositories The initial idea is to leverage the existing ``ceph_rhcs_cdn_install`` config option and build support for that on debian based systems. An additional idea is to define the baseurl for the repo as a config option as well so that we can default it to https://customername:customerpasswd@rhcs.download.redhat.com while allowing for the user to provide a custom mirror if they're hosting these repos at another location.
For QE, to do: * validate that the repo is enabled and added on Ubuntu * validate that ceph packages are properly installed afterward
PR upstream: https://github.com/ceph/ceph-ansible/pull/1734
Edit all.yml and change ceph_rhcs_cdn_debian_repo and possibly ceph_rhcs_cdn_debian_repo_version if your QE URL is different. Thanks!
Bara, the doc should be: ceph_origin: repository ceph_repository: rhcs ceph_repository_type: cdn You can remove: ceph_rhcs ceph_rhcs_cdn_install: true Thanks
I think there is an issue with your repository, see: "install 'ceph-osd'' failed: E: There were unauthenticated packages and -y was used without --allow-unauthenticated\n" It does **not** look like a ceph-ansible bug to me. Please investigate and let me know. Thanks.
Still looks like a repo issue to me and not a ceph-ansible bug, can we move forward with this? Thanks.
please move this VERIFIED.
Moving this bug to verified.
Please don't move bugs to ON_QA without attaching to an advisory. I'm closing this one as NOTABUG since it is not technically a bug in ceph-ansible.
Whoops, this was my bad! This was a real bug, and the issues in comment 14 onwards had to do with the test process.
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-2017:3387