Hide Forgot
Description of problem: Need to know how to disable all unwanted repos. Version-Release number of selected component (if applicable): ~~~~~~~~~~~~~~~~~~ $ rpm -qfi /bin/instack-virt-setup Name : instack-undercloud Version : 4.0.0 Release : 13.el7ost Architecture: noarch ~~~~~~~~~~~~~~~~~~ How reproducible: Steps to Reproduce: Following the doc https://access.redhat.com/articles/2534191 ~~~~~~~~~~~~~~~~~ 5. Set the environment variables for RHN: $ export REG_METHOD=portal $ export REG_USER=rhn-support-XXXXX $ export REG_PASSWORD=********** $ export REG_POOL_ID=XXXXXXXXXXXXXX $ export REG_REPOS="rhel-7-server-rpms rhel-7-server-extras-rpms rhel-7-server-openstack-9-rpms rhel-7-server-openstack-9-director-rpms rhel-7-server-rh-common-rpms" ~~~~~~~~~~~~~~~~~ And then $ instack-virt-setup But as result it end up with error because some unwanted repos been enable and which no longer available. ~~~~~~~~~~~~~~~~~~ ++ find /tmp/in_target.d/pre-install.d -maxdepth 1 -name 'package-installs-*' + '[' -n '' ']' WARNING: map-packages is deprecated. Please use the pkg-map element. https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/fast-datapath/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below knowledge base article https://access.redhat.com/articles/1320623 Like yum-config-manager --disable rhel-7-fast-datapath-rpms ~~~~~~~~~~~~~~~~~~ So, would like to know if there is any option disable all the unwanted repos. FYI, it can be done using subscription manager but will not help as its pass to the overcloud images. Actual results: Expected results: Additional info:
Oh, actually it's already merged: https://review.openstack.org/#/c/377331/
Please someone backport the change to OSP 10.
Moving to verified as this is a dev/test bug only so there's no sense wasting QE time verifying it. If any developers or testers find that it's not actually fixed they can reopen.
instack-virt-setup is not a supported tool for customer use. We shouldn't need to document any fixes to it.
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://rhn.redhat.com/errata/RHEA-2016-2948.html