Custom Query (98 matches)

The host OS on pc5.utah.geniracks.net contains the standard DNS resolution client tools:

vhost1,[~],10:01(0)$ ls -1 /usr/bin/{host,dig,nslookup}
/usr/bin/dig*
/usr/bin/host*
/usr/bin/nslookup*

However, these tools seem to be missing from inside my container, virt1.ecgtest2:

[chaos@virt1 ~]$ ls -1 /usr/bin/{host,dig,nslookup}
ls: cannot access /usr/bin/host: No such file or directory
ls: cannot access /usr/bin/dig: No such file or directory
ls: cannot access /usr/bin/nslookup: No such file or directory

[chaos@virt1 ~]$ type host
bash: type: host: not found
[chaos@virt1 ~]$ type dig
bash: type: dig: not found
[chaos@virt1 ~]$ type nslookup
bash: type: nslookup: not found

This seems unexpected. I would think experimenters might want to be able to do DNS lookups, e.g. to download tools on the control network.

There should be a plan or checklist for creating accounts on a rack for a new site admin.

Set up 10 experiments but some of the hosts are not accessible even though the slivers status reports that the slivers are ready.

Scenario:

• 10 slices created, each slice contains one sliver with 2 VMs.
• Slice names are 2vmslice1 through 2vmslice10.
• All slivers are ready according to the sliver status.

There are 3 VMs on which I am prompted for a password, below are the sliver name, the hostname and ports for the VMs not allowing login.

SliceName: 2vmslice4  'hostname': 'pc3.utah.geniracks.net', 'port': 31803, 
SliceName: 2vmslice8  'hostname': 'pc1.utah.geniracks.net', 'port': 32826, 
SliceName: 2vmslice9  'hostname': 'pc1.utah.geniracks.net', 'port': 33082, 

Attaching the sliver status to the ticket.