Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard W.M. Jones
2015-02-09 11:37:41 UTC
Description of problem:
Currently in RHEL 7.1:
$ virt-builder -l
centos-6 x86_64 CentOS 6.6
centos-7.0 x86_64 CentOS 7.0
cirros-0.3.1 x86_64 CirrOS 0.3.1
debian-6 x86_64 Debian 6 (Squeeze)
debian-7 x86_64 Debian 7 (Wheezy)
fedora-18 x86_64 Fedora® 18
fedora-19 x86_64 Fedora® 19
fedora-20 x86_64 Fedora® 20
fedora-21 x86_64 Fedora® 21 Server
scientificlinux-6 x86_64 Scientific Linux 6.5
ubuntu-10.04 x86_64 Ubuntu 10.04 (Lucid)
ubuntu-12.04 x86_64 Ubuntu 12.04 (Precise)
ubuntu-14.04 x86_64 Ubuntu 14.04 (Trusty)
You can add the internal-only virt-builder RHEL repo
(http://file.rdu.redhat.com/~rjones/builder/index.asc) in
order to get RHEL images too, but customers cannot do that.
What is needed is a way to get images from RHN, which will
involve authenticating to the CDN using subscription-manager --
I'm unclear of the precise details of how this works.
Version-Release number of selected component (if applicable):
libguestfs-tools-c-1.28.1-1.18.el7.x86_64
Ummm +1 I guess. Not sure why Red Hat isn't keen to do this...
Comment 3Richard W.M. Jones
2017-02-16 13:35:18 UTC
Moving to 7.5 because we don't have the infrastructure in place
to make this happen. Mainly it will require RHN to publish some
kind of automated information about available cloud images.
There are also likely to be issues with passing authentication
credentials from the host to RHN.
What would it take to make this happen? Assuming that the host machine is enrolled with subscription-manager, and has an appropriate pool attached, it seems like the disconnect is the Enabled Repos. virt-builder could call subscription-manager to enable the appropriate repos just during the build call.
(In reply to Adam Young from comment #4)
> What would it take to make this happen? Assuming that the host machine is
> enrolled with subscription-manager, and has an appropriate pool attached, it
> seems like the disconnect is the Enabled Repos. virt-builder could call
> subscription-manager to enable the appropriate repos just during the build
> call.
The idea was the index files (for virt-builder repositories) are distributed via CDN, so you need to authenticate with it to fetch them, and also to fetch the actual disk images. This is because the files are not RPMs, so `subscription-manager` + `yum download` will not work.
So subscription-manager will not help in this case, since virt-builder would need to interact with the CDN (with certs, etc) on its own, or using some existing library.
Comment 6Richard W.M. Jones
2018-07-26 08:21:04 UTC
Comment 14RHEL Program Management
2020-12-15 07:33:10 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 17RHEL Program Management
2021-07-31 07:27:14 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 18Richard W.M. Jones
2021-07-31 07:45:55 UTC
My apologies, this bug was closed by a broken process that we
do not have any control over. Reopening.