Questions[vagrant](ubuntu)

I am trying to use the official ubuntu/focal64 Vagrant box to run some new VMs. I have tried with versions v20200518.0.0 and v20200522.0.0 (the newest as of my testing). I am using Vagrant 2.2.9 and I tried with both VirtualBox 6.0.4 and 6.1.8.

My Vagrantfile is extremely simple:

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/focal64"
  config.vm.box_version = "20200522.0.0"

  config.vm.define "db1" do |db1|
    db1.vm.network "private_network", ip: "192.168.56.10"
  end

  config.vm.define "db2" do |db2|
    db2.vm.network "private_network", ip: "192.168.56.11"
  end

  config.vm.define "app1" do |app1|
    app1.vm.network "private_network", ip: "192.168.56.20"
  end
end

(Later on I plan to add provisioning to each of those boxes, but this is a simple test just to get started.)

The problem is that these boxes will not boot. Here is the error I get:

[  148.806822] VFS: Cannot open root device "PARTUUID=43931bda-01" or unknown-block(0,0): error -6
[  151.754729] Please append a correct "root=" boot option: here are the available partitions
[  154.534996] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[  157.312019] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-31-generic #35-Ubuntu
[  159.842670] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006

After that there is a stack trace, but I can't get a screenshot because the box reboots too quickly.

When I try to use the ubuntu/bionic64 images, those work fine. Only the new focal64 images seem to be broken.

How can I get these VMs to boot?

Cross-Posted

Environmental Details

Relevant bits of server's /etc/ssh/sshd_config:

X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost no

Relevant bits of client's $HOME/.ssh/config:

Host *
    XAuthLocation /opt/X11/bin/xauth
    ForwardX11 yes
    ForwardX11Trusted yes

Using XQuartz on macOS High Sierra.

The Problem

I'm spinning up a vagrant Ubuntu 18.04 VM. I've added a second user outside of the vagrant user.

ssh -X vagrant@ubuntu-bionic xclock

I can get X11Forwarding to work when I login as the vagrant user. I cannot get X11Forwarding to work when I login as the ops user.

ssh -X ops@ubuntu-bionic xclock

X11 forwarding request failed on channel 0
Error: Can't open display:

I want to be able to get it to work with the ops user. From the client, $DISPLAY has a value. When I login with vagrant, $DISPLAY has a value. When I login as ops, $DISPLAY is unset. If I set $DISPLAY to match what it is with the vagrant user, I get the same error:

Error: Can't open display: localhost:10.0

when X11UseLocalhost yes

Error: Can't open display: ubuntu-bionic:10.0

when X11UseLocalhost no

If I login as ops and then sudo su - vagrant, $DISPLAY remains unset. If I login as vagrant and then sudo su - ops, $DISPLAY is inherited.

What am I missing to get this to work? I've run xhost + in each user (including sudo -s root xhost +) and it still doesn't work.

If I add -vv to my ssh commands, I see this message when connecting as vagrant:

X11 forwarding request accepted on channel 0

and as ops:

Remote: X11 forwarding disabled in user configuration file.
X11 forwarding request failed on channel 0

I'm an experienced programmer, but a Python, Ubuntu, and Linux newbie. I apologize, as well, if this question would be better in a different forum.

I am working on a project in Python using PyCharm, with code executing in an Ubuntu environment in Vagrant. It has to access a MongoDb database.

When the database is local, I have no difficulties. I also can connect to one remote database. However, the database I most want to connect to is part of a replica set, and that seems to be the problem.

(I should say that the database with the replica set performs just fine in its actual role. I seem to be the one with the problem.)

We set up some ssh tunnels, using these suggestions:

Connecting to a Mongo Replica Set via SSH

We set up hosts and ifconfig appropriately.

My supervisor can now connect with minimal difficulty. I, however, keep getting this message:

pymongo.errors.ServerSelectionTimeoutError: No replica set members available for replica set name "abc"

The connection information includes all 3 replica set servers as part of the host string, plus the replica set name being specified and ReadPreference.PRIMARY.

The stack track looks like this:

File "/usr/local/src/dashboard/dashboard/dashboard/app/tasks/exports/__init__.py", line 95, in get_sections
    sections = CourseSection.objects(**params)
File "/apps/dashboard-env/lib/python3.4/site-packages/mongoengine/queryset/manager.py", line 37, in __get__
    queryset = queryset_class(owner, owner._get_collection())
File "/apps/dashboard-env/lib/python3.4/site-packages/mongoengine/document.py", line 198, in _get_collection
    cls.ensure_indexes()
File "/apps/dashboard-env/lib/python3.4/site-packages/mongoengine/document.py", line 878, in ensure_indexes
  collection.create_index(fields, background=background, **opts)
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/collection.py", line 1753, in create_index
    self.__create_index(keys, kwargs, session, **cmd_options)
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/collection.py", line 1641, in __create_index
    with self._socket_for_writes() as sock_info:
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/collection.py", line 193, in _socket_for_writes
    return self.__database.client._socket_for_writes()
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/mongo_client.py", line 965, in _socket_for_writes
    server = self._get_topology().select_server(writable_server_selector)
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/topology.py", line 224, in select_server
    address))
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/topology.py", line 183, in select_servers
    selector, server_timeout, address)
File "/apps/dashboard-env/lib/python3.4/site-packages/pymongo/topology.py", line 199, in _select_servers_loop
    self._error_message(selector))
pymongo.errors.ServerSelectionTimeoutError: No replica set members available for replica set name "abc"

The specific message No replica set members available for replica set name "abc" seems to be relatively uncommon, as I haven't found any hits on Google for problems with a specific named replica set.

Any suggestions would be much appreciated.

Is there a way to install a newer version than in the repository?

Ubuntu installs vagrant 1.4.3 at the moment, but I need at least 1.5

Vagrant is a tool to build and manage virtual machines for developers. It has a getting started on Ubuntu guide that contains iffy-looking suggestions like

$ sudo ln -s /usr/bin/ruby1.8 /usr/bin/ruby  # wtf???

or installing RubyGems from source rather than from Ubuntu packages, and then using gem install to install vagrant itself.

I'm not feeling comfortable just following those instructions. Is there perhaps a PPA? Are there, perhaps, alternative tools that are packaged for Ubuntu?