Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vagrant ubuntu box no longer available #64

Closed
nickbroon opened this issue Jan 19, 2018 · 2 comments · Fixed by #75
Closed

vagrant ubuntu box no longer available #64

nickbroon opened this issue Jan 19, 2018 · 2 comments · Fixed by #75
Assignees
@xenithorb
Labels
bug

Comments

@nickbroon
Copy link

I'd guess a switch to different provider is needed.

8:26 $ cd tests
8:26 $ vagrant up --provider libvirt ubuntu16
DEPRECATION: The 'sudo' option for the Ansible provisioner is deprecated.
Please use the 'become' option instead.
The 'sudo' option will be removed in a future release of Vagrant.

Bringing machine 'ubuntu16' up with 'libvirt' provider...
/home/nick/.vagrant.d/gems/2.4.2/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/document.rb:44: warning: constant ::Fixnum is deprecated
/home/nick/.vagrant.d/gems/2.4.2/gems/nokogiri-1.6.8.1/lib/nokogiri/xml/document.rb:44: warning: constant ::Fixnum is deprecated
==> ubuntu16: Box 'wholebits/ubuntu-16.04-64' could not be found. Attempting to find and install...
    ubuntu16: Box Provider: libvirt
    ubuntu16: Box Version: >= 0
The box 'wholebits/ubuntu-16.04-64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/wholebits/ubuntu-16.04-64"]
Error: The requested URL returned error: 404 Not Found
@nickbroon nickbroon mentioned this issue Jan 24, 2018
Closed
@xenithorb
Copy link
Collaborator

This needs to be updated anyhow. Loosely related to #66 due to needing to look up which distros should be supported at present.

@xenithorb
Copy link
Collaborator

Have any ideas for the ubuntu box provider? I'm typically using it on Fedora here. I'd like to stay as official as possible, but I remember the reason for not using Ubuntu's official boxes were that they refused to follow vagrant conventions in a lot of areas (of which I don't remember the details of) - and it basically broke a bunch of stuff.

Probably worth looking at their newer images to see if they're conforming to those standards, now.

@xenithorb xenithorb self-assigned this Feb 18, 2018
@xenithorb xenithorb added the bug label Feb 18, 2018
xenithorb added a commit that referenced this issue Feb 27, 2018
@xenithorb
Vagrantfile updates:
744c382 
 - Do extra vers per box, this allows us to
   set ansible_python_interpreter per box most hosts need
/usr/bin/python3, or python2 installed python3 ansible
   is stable enough to consider using full time now

 - RuboCop fixes
 - Add do_ansible function back as provisioner

Others:
 - Added Ansible config
 - Changed role name to be '../..' in provision.yml as this is
   the proper way to reference a role from its own subdir

 - Fixes #64
xenithorb added a commit that referenced this issue Feb 27, 2018
@xenithorb
Vagrantfile updates:
ffa8a25 
 - Update vagrant boxes to point to newer atlas boxes
   - Chose a different provider for Ubuntu images - "generic"

 - Do extra vers per box, this allows us to
   set ansible_python_interpreter per box most hosts need
   /usr/bin/python3, or python2 installed python3 ansible
   is stable enough to consider using full time now

 - RuboCop fixes
 - Add do_ansible function back as provisioner

Others:
 - Added Ansible config
 - Changed role name to be '../..' in provision.yml as this is
   the proper way to reference a role from its own subdir

 - Fixes #64
@xenithorb xenithorb mentioned this issue Feb 27, 2018
Merged
xenithorb added a commit that referenced this issue Feb 27, 2018
@xenithorb
Vagrantfile updates:
d6107fe 
 - Update vagrant boxes to point to newer atlas boxes
   - Chose a different provider for Ubuntu images - "generic"

 - Do extra vers per box, this allows us to
   set ansible_python_interpreter per box most hosts need
   /usr/bin/python3, or python2 installed python3 ansible
   is stable enough to consider using full time now

 - RuboCop fixes
 - Add do_ansible function back as provisioner

Others:
 - Added Ansible config
 - Changed role name to be '../..' in provision.yml as this is
   the proper way to reference a role from its own subdir

 - Fixes #64
xenithorb added a commit that referenced this issue Feb 27, 2018
@xenithorb
Vagrantfile updates:
41828e6 
 - Update vagrant boxes to point to newer atlas boxes
   - Chose a different provider for Ubuntu images - "generic"

 - Do extra vers per box, this allows us to
   set ansible_python_interpreter per box most hosts need
   /usr/bin/python3, or python2 installed python3 ansible
   is stable enough to consider using full time now

 - RuboCop fixes
 - Add do_ansible function back as provisioner

Others:
 - Added Ansible config
 - Changed role name to be '../..' in provision.yml as this is
   the proper way to reference a role from its own subdir

 - Fixes #64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xenithorb xenithorb

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Vagrantfile updates: RocketChat/Rocket.Chat.Ansible
2 participants
@nickbroon @xenithorb