Vagrant failing with error msg

I have installed virtual box and vagrant in system. But when i try to run the vagrant up it fails with following error message

 mongodb-m042:  One of the configured repositories failed (CentOS-7 - Base),
mongodb-m042:  and yum doesn't have enough cached data to continue. At this point the only
mongodb-m042:  safe thing yum can do is fail. There are a few ways to work "fix" this:
mongodb-m042:      1. Contact the upstream for the repository and get them to fix the problem.
mongodb-m042:      2. Reconfigure the baseurl/etc. for the repository, to point to a working
mongodb-m042:         upstream. This is most often useful if you are using a newer
mongodb-m042:         distribution release than is supported by the repository (and the
mongodb-m042:         packages for the previous distribution release still work).
mongodb-m042:      3. Run the command with the repository temporarily disabled
mongodb-m042:             yum --disablerepo=base ...
mongodb-m042:      4. Disable the repository permanently, so yum won't use it by default. Yum
mongodb-m042:         will then just ignore the repository until you permanently enable it
mongodb-m042:         again or use --enablerepo for temporary usage:
mongodb-m042:             yum-config-manager --disable base
mongodb-m042:         or
mongodb-m042:             subscription-manager repos --disable=base
mongodb-m042:      5. Configure the failing repository to be skipped, if it is unavailable.
mongodb-m042:         Note that yum will try to contact the repo. when it runs most commands,
mongodb-m042:         so will have to try and fail each time (and thus. yum will be be much
mongodb-m042:         slower). If it is a very temporary problem though, this is often a nice
mongodb-m042:         compromise:
mongodb-m042:             yum-config-manager --save --setopt=base.skip_if_unavailable=true
mongodb-m042: failure: repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2 from base: [Errno 256] No more mirrors to try.

Hey @shivanandpatil

Have you tried to start over with

vagrant destroy
vagrant up --provision

I just have not seen that error come up, so my apologies, if the above does not help.

Hello shivanandpatil,

I’m sorry you’ve had this issue.

Can you confirm that you can destroy the Vagrant environment with:

vagrant destroy

And then try to bring up the environment with:

vagrant up --provision

If this does not work, please try:

vagrant plugin install vagrant-vbguest

Let me know if this helps.