Hey all, Sorry for the noise, I figured it out :)
Just so it's etched in stone - `gradle yum` must be ran first in order to create the repo metadata inside of bigtop/output. I'm going to open a jira and submit a patch to add this to the docs so it's a little more visible. Best, On Sun, Nov 15, 2015 at 1:26 PM, Mike Grimes <[email protected]> wrote: > Hi, > > I'm trying to use the deployment strategy in vagrant-puppet-vm/, after > having set enable_local_repo to `true` - and am getting close to having it > working, but am running into a small snag that I've been unable to figure > out a solution to. > > Just to give some context, I'm following the instructions per the wiki > here: > https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Provisioner+User+Guide > > Running `vagrant up` runs successfully until > Package[java-1.7.0-openjdk-devel.x86_64] is executed - and then it chokes > with the following error: > > ==> bigtop1: Error: > /Stage[main]/Main/Package[java-1.7.0-openjdk-devel.x86_64]/ensure: change > from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list > java-1.7.0-openjdk-devel.x86_64' returned 1: Error: Cannot retrieve > repository metadata (repomd.xml) for repository: bigtop-home_output. Please > verify its path and try again > > Now I know this was an issue back in > https://issues.apache.org/jira/browse/BIGTOP-1583 and has since been > fixed but updating the repo in bigtop-deploy/puppet/manifests/site.pp with > the centos 6 as opposed to the centos 7 one that is there by default didn't > help either. > > I've been searching for a while but my limited knowledge of how yum repos > work seems to be holding me back. Does anyone have any ideas of what I need > to do to get this working? > > Best, >
