Description of problem: this page https://repos.fedorapeople.org/repos/openstack-m/instack-undercloud/html/build-images.html says: The built images will automatically have the same base OS as the running undercloud. See the Note below to choose a different OS: so my instack is centos7.1 but all of a sudden i saw instack-build-images downloading fedora 21 images. + curl -o fedora-user.qcow2 -L http://cloud.fedoraproject.org/fedora-21.x86_64.qcow2 which meant that export NODE_DIST=centos7 is mandatory as fedora is the default Version-Release number of selected component (if applicable): How reproducible: everytime - twice now. then set the NODE_DIST variable which resolved it Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
instack-build-images will download the fedora image as the cloud user image to run on the overcloud as part of instack-test-overcloud. We have to use fedora b/c rhel/centos does not have support for any nested virt (qemu or kvm). The build images do have the same OS as the host.
james the description above which is taken from the document says "The built images will automatically have the same base OS as the running undercloud" this is not accurate. running on a centos host will download a fedora image further more, you say "We have to use fedora", the description above says "export NODE_DIST=centos7" - this will indeed use centos as the image. that variable was also taken from the documentation and finally, when i used that above variable, i was able to complete the installation of rdo manager, including the 2 baremetal virt servers AND was able to login to horizon. nest kvm is theoretically only required only if an instance will be instantiated on those virtual nodes deployed by the instack script. the bug here to be exact is that on a centos host, the downloaded image should have been a centos image. on a fedora host, it should be a fedora image, however, on centos it in fact defaulted to fedora.