Forum Replies Created
-
Posts
-
Issue with the bastion host traffic is resolved. You can try creating your slices with the standard bastion host settings (with bastion.fabric-testbed.net)
There is a problem with upstream connectivity affecting one of the bastion hosts, causing intermittent interruptions. We are working on the issue. In the mean time, you can set a specific bastion host in your fabric_rc file (eg
FABRIC_BASTION_HOST=bastion-renc-1.fabric-testbed.net) . We will notify about the status of the actual issueHello Danilo,
I checked both VMs (NS2 and NS4) and they are up and online. However there seems to be some changes in the SSH key(s) that are injected by the system and I cannot login to the VMs. I’m not sure about the main root cause of the exceptions that you posted, they indicate that the FABRIC orchestration system cannot perform actions on the VMs, and the issue with the SSH keys may be the main cause. We need to learn from you what might have changed on the VMs.
I’m posting the reservation info here. Both VM reservations are valid until 12/25
{ "sliver_id": "be7426fd-7ebe-4e6b-bc65-56e30d7e8e50", "slice_id": "53cfa2bd-5110-420d-8bdb-053c1af45801", "type": "VM", "notices": "Reservation be7426fd-7ebe-4e6b-bc65-56e30d7e8e50 (Slice NS2(53cfa2bd-5110-420d-8bdb-053c1af45801) Graph Id:2aced1b1-3843-4809-b9a2-9ed9e2ff0317 Owner:daniloassis@utfpr.edu.br) is in state (Active,None_) ", "start": "2025-08-02 12:44:10 +0000", "end": "2025-12-25 18:11:58 +0000", "requested_end": "2025-12-25 18:11:58 +0000", "units": 1, "state": 4, "pending_state": 11, "sliver": { "Name": "NS2", "Type": "VM", "Capacities": "{\"core\": 16, \"disk\": 1000, \"ram\": 16}", "CapacityHints": "{\"instance_type\": \"fabric.c16.m16.d1000\"}", "CapacityAllocations": "{\"core\": 16, \"disk\": 1000, \"ram\": 16}", "LabelAllocations": "{\"instance\": \"instance-000040ec\", \"instance_parent\": \"star-w1.fabric-testbed.net\"}", "ReservationInfo": "{\"reservation_id\": \"be7426fd-7ebe-4e6b-bc65-56e30d7e8e50\", \"reservation_state\": \"Active\"}", "NodeMap": "[\"e2b1e451-45b4-4691-9527-aae18cad3b19\", \"BBQSH63\"]", "StitchNode": "false", "ImageRef": "default_ubuntu_22,qcow2", "MgmtIp": "2001:400:a100:3030:f816:3eff:fed9:14ee", "Site": "STAR" } } { "sliver_id": "527af509-fb62-41ae-a0c0-191e3c7f6525", "slice_id": "059939f1-19be-49ee-ab5b-bf4504639c13", "type": "VM", "notices": "Reservation 527af509-fb62-41ae-a0c0-191e3c7f6525 (Slice NS4(059939f1-19be-49ee-ab5b-bf4504639c13) Graph Id:14a3d7f7-e797-4e75-bafb-00282ea63896 Owner:daniloassis@utfpr.edu.br) is in state (Active,None_) ", "start": "2025-08-02 12:44:10 +0000", "end": "2025-12-25 18:12:40 +0000", "requested_end": "2025-12-25 18:12:40 +0000", "units": 1, "state": 4, "pending_state": 11, "sliver": { "Name": "NS4", "Type": "VM", "Capacities": "{\"core\": 16, \"disk\": 1000, \"ram\": 16}", "CapacityHints": "{\"instance_type\": \"fabric.c16.m16.d1000\"}", "CapacityAllocations": "{\"core\": 16, \"disk\": 1000, \"ram\": 16}", "LabelAllocations": "{\"instance\": \"instance-00000cf6\", \"instance_parent\": \"toky-w2.fabric-testbed.net\"}", "ReservationInfo": "{\"reservation_id\": \"527af509-fb62-41ae-a0c0-191e3c7f6525\", \"reservation_state\": \"Active\"}", "NodeMap": "[\"e2b1e451-45b4-4691-9527-aae18cad3b19\", \"FW696S3\"]", "StitchNode": "false", "ImageRef": "default_ubuntu_22,qcow2", "MgmtIp": "133.69.160.21", "Site": "TOKY" } }Ajay,
The sliver that you reported the problem about was on FABRIC-FIU and it’s expired. I can see that you have recent slivers on the FIU node. Can you please let us know if you still encounter the problem or not?
Hello,
Yesterday some services were affected from an outage and the errors for loading projects and extension might be due to the problem with the affected services. FABRIC team checked all services to confirm they are restored and I also confirmed that slice extension is working well.
Due to the FABRIC team’s schedules, this outage might not have been communicated via the announcements, apologies for this inconvenience.
