Closed iversond closed 7 years ago
To manually resolve the issue, I updated the /etc/yum.repos.d/public-yum-ol7.repo
by hand. This was in version 0.0.4
of the vagrant box.
sudo rm /etc/yum.repos.d/public-yum-ol7.repo
cd /etc/yum.repos.d
wget http://public-yum.oracle.com/public-yum-ol7.repo
I wasn't able to get a re-creation case on this, but I think it may be related to the recent transition of OEL 7.2 to 7.3. I experienced an almost identical error when trying to provision a CentOS 7.2 VM.
At any rate, I went ahead and upgraded the Vagrant box to use OEL 7.3 - so running vagrant box update
should upgrade bring it up to date.
C:\pum_images\fscm92
λ vagrant box outdated
Checking if box 'jrbing/ps-vagabond' is up to date...
A newer version of the box 'jrbing/ps-vagabond' is available! You currently
have version '0.0.4'. The latest is version '1.0.0'. Run
`vagrant box update` to update.
C:\pum_images\fscm92
λ vagrant box update
==> ps-vagabond: Checking for updates to 'jrbing/ps-vagabond'
ps-vagabond: Latest installed version: 0.0.4
ps-vagabond: Version constraints:
ps-vagabond: Provider: virtualbox
==> ps-vagabond: Updating 'jrbing/ps-vagabond' with provider 'virtualbox' from version
==> ps-vagabond: '0.0.4' to '1.0.0'...
==> ps-vagabond: Loading metadata for box 'https://atlas.hashicorp.com/jrbing/ps-vagabond'
==> ps-vagabond: Adding box 'jrbing/ps-vagabond' (v1.0.0) for provider: virtualbox
ps-vagabond: Downloading: https://atlas.hashicorp.com/jrbing/boxes/ps-vagabond/versions/1.0.0/providers/virtualbox.box
ps-vagabond: Progress: 100% (Rate: 18.8M/s, Estimated time remaining: --:--:--)
==> ps-vagabond: Successfully added box 'jrbing/ps-vagabond' (v1.0.0) for 'virtualbox'!
C:\pum_images\fscm92