Custom Query (98 matches)
Results (22 - 24 of 98)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#56 | fixed | Sliver with 4 VMs remains in "geni_status": "notready" | ||
Description |
Created a 4 VMs sliver named IG-CT-1 at the Utah InstaGENI rack. No errors were reported, but 30 minutes after the sliver creation, all 4 VMs are still showing "geni_status": "notready". RSpec is attached. |
|||
#92 | fixed | sliver manifest does not pass rspeclint | ||
Description |
When creating a API V2 Sliver with unbound resources and two links, the resulting manifest does not pass rspeclint: $ rspeclint ln22-manifest-rspec-instageni-gpolab-bbn-com-protogeniv2.xml Line 1: Failed validation with root at element: Schemas validity error : Element '{http://www.geni.net/resources/rspec/3}link': The attribute 'vlantag' is required but missing. Schemas validity error : Element '{http://www.geni.net/resources/rspec/3}link': The attribute 'vlantag' is required but missing. : rspec The manifest rspec is attached. |
|||
#111 | fixed | Sliver failure for GA Tech aggregate for Confirmation Test IG-CT-3 | ||
Description |
Running test case IG-CT-3, which includes 1 VM @GPO InstaGENI and 1 VM @ GA Tech InstaGENI connected via a GRE Tunnel. The sliver creation is successful and the sliver status is ready for GPO InstaGENI, but the sliver failed for the GA Tech sliver. Failure shown in sliverstatus may be the same as reported by Josh in earlier email, writing ticket to track to resolution: "geni_error": "Running os dependent initialization script rc.linux *** WARNING: could not identify root disk, no swap enabled Informing Emulab Control that we have rebooted Checking Testbed reservation status Cleaning node; removing configuration files Allocated! emulab-net/IG-CT-3/VM-2 Setting up for SFS ... Setting up Ping of Death Authenticated IPOD enabled from 143.215.216.132/255.255.255.255 Starting node health monitoring daemon FATAL: Module i2c_piix4 not found. FATAL: Module w83781d not found. Failed running rc.healthd (256)! at /usr/local/etc/emulab/libsetup.pm line 1152, <TD> line 2. Starting slothd usage detector Starting testbed update watchdog Running config scripts Checking manifest... Checking Testbed localization configuration ... Checking Testbed keys ... Checking Testbed Blobs configuration ... Checking Testbed user accounts configuration ... Adding group: emulab-net/502 Adding: lnevers/20001/502/1/lnevers//users/lnevers/ updating local home directory Adding: geniuser/502/502/1/Geni User//users/geniuser/ updating local home directory Checking Testbed route configuration ... net.ipv4.conf.all.forwarding = 1 Checking Testbed tunnel configuration ... FATAL: Module ip_gre not found. Checking Testbed interface configuration ... Using Linux netem instead of custom qdiscs. Checking Testbed hostnames configuration ... Checking Testbed trace configuration ... Checking Testbed trafgen configuration ... Checking Testbed Tarball configuration ... Checking Testbed RPM configuration ... Starting linktest daemon *** ERROR: linktest daemon failed to start. Status: 15 *** /usr/local/etc/emulab/rc/rc.bootsetup: Error running /usr/local/etc/emulab/rc/rc.linktest ", "geni_status": "failed" Also received this email failure notification: -------- Original Message -------- Subject: GATECHINSTAGENI: 1 nodes failed to boot Date: Mon, 29 Apr 2013 11:35:59 -0400 (EDT) From: testbed-ops@ops.instageni.rnoc.gatech.edu To: lnevers <lnevers@emulab.net> CC: testbed-ops@ops.instageni.rnoc.gatech.edu Nodes: [Node: pcvm2-2] in urn:publicid:IDN+emulab.net+slice+IG-CT-3 failed. Slice name is "IG-CT-3". VMs assigned are:
|