rook: yum install fails from the ceph toolbox

Is this a bug report or feature request?

  • Bug Report

Deviation from expected behavior: When attempting to install packages in the rook-ceph toolbox, it fails with the following error:

[root@minikube /]# yum install s3cmd
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
epel/x86_64/metalink                                                                                                                                                                                    |  16 kB  00:00:00     
 * base: mirrors.syringanetworks.net
 * epel: mirror.steadfastnet.com
 * extras: mirrors.syringanetworks.net
 * updates: mirrors.syringanetworks.net
Ceph                                                                                                                                                                                                    | 2.9 kB  00:00:00     
Ceph-noarch                                                                                                                                                                                             | 2.9 kB  00:00:00     
base                                                                                                                                                                                                    | 3.6 kB  00:00:00     
https://4.chacra.ceph.com/r/ceph-iscsi/master/ff5e6873c43ab6828d3f7264526100b95a7e3954/centos/7/flavors/default/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

 One of the configured repositories failed (ceph-iscsi packages for \x86_64),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=ceph-iscsi ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable ceph-iscsi
        or
            subscription-manager repos --disable=ceph-iscsi

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=ceph-iscsi.skip_if_unavailable=true

failure: repodata/repomd.xml from ceph-iscsi: [Errno 256] No more mirrors to try.
https://4.chacra.ceph.com/r/ceph-iscsi/master/ff5e6873c43ab6828d3f7264526100b95a7e3954/centos/7/flavors/default/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

Expected behavior: Should be able to add packages during development to the toolbox. In particular, s3cmd is mentioned in the rook docs for consuming object storage.

How to reproduce it (minimal and precise):

  • Install a cluster from master
  • kubectl create -f toolbox.yaml
  • yum install s3cmd

This does not repro with the v1.0.5 toolbox. There must be a change in the ceph/ceph:v14.2.2 base image that is causing this.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 17 (10 by maintainers)

Commits related to this issue

Most upvoted comments

@leseb Yes, using v3.x for Nautilus and pointing to the latest ceph-iscsi master for the in-development Octopus sounds good-to-me.