fedora element lacks repos

Bug #1401256 reported by Abel Lopez on 2014-12-10
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
diskimage-builder
Undecided
Unassigned

Bug Description

The latest fedora element dies in the package install because there are no repos enabled.

Comparing to the centos7 element, they setup yum in pre-install.d

simply doing
disk-image-create -o fedora.qcow2 fedora
fails
doing the same with centos7 works

Gregory Haynes (greghaynes) wrote :

This command works for me. Can you provide more information such as logs?

Abel Lopez (al592b) wrote :

Yes, Please see
http://paste.openstack.org/show/rPj7syZpc4xpyIgtw6eu/

I think because the repo setup happens in pre-install.d, it would only succeed if /etc/yum.repos.d/fedora.repo exists.

This fails on ubuntu, because even if you install yum and rpm, the repos.d is in /etc/yum/repos.d/ and fedora.repo is not included.

Abel Lopez (al592b) wrote :

I'm able to proceed if I extract the fedora*.repo and install it on my local yum.
This implies that only fedora based systems will be able to build fedora images. IMO, this should be set up as in the centos7 element which setup up the repo in a HEREDOC

Ben Nemec (bnemec) wrote :

Unless I'm mistaken, pre-install.d runs inside the chroot so the file doesn't need to exist on the host system. I'm also unable to reproduce this in an Ubuntu VM, so I'm wondering if there's something happening in the "cisco" element that isn't interacting nicely with the fedora element for some reason. You should essentially never get a "no enabled repos" error on fedora because the base cloud image ships with the repos enabled to begin with.

FWIW, the command I used to test was "ubuntu@dib-test:~$ disk-image-create -a amd64 -o test.qcow2 fedora base vm" which appears to be the same as your paste output except the cisco element that I don't have.

Changed in diskimage-builder:
status: New → Incomplete
Abel Lopez (al592b) wrote :

It's probably something wrong with my build host.
I ended up fixing it by clearing out the yum cache and starting over

Changed in diskimage-builder:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers