- This topic has 3 replies, 2 voices, and was last updated 1 day, 2 hours ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC General Questions and Discussion › node.add_fabnet() raises ResourceNotFoundError
Hi,
I had a storage slice that was working fine, but after it expired I tried to rebuild it using the same notebook and now I’m getting the following error when calling node.add_fabnet():
ResourceNotFoundError: ‘Network not found: FABNET_IPv4_MICH’
The traceback points to slice.py:2206 inside get_network(), which is called from node.py:4347 inside add_fabnet(). It looks like add_fabnet() is trying to look up a FABNetv4 network that doesn’t exist yet in the new slice.
My code:
slice = fablib.new_slice(name=slice_name)
node = slice.add_node(name=node_name, site=site)
node.add_storage(name=storage_name)
node.add_fabnet() # <-- fails here
slice.submit()
Nothing changed in my code between when it was working and now. My questions:
– Has the add_fabnet() API changed and now requires explicit arguments?
– Is the MICH site currently healthy and available?
– Is there a recommended way to attach FABNetv4 to a storage slice with the current version of fabrictestbed-extensions?
fabrictestbed-extensions version:
fabric@summer:Configure FPGAs-71%$ pip show fabrictestbed-extensions
Name: fabrictestbed_extensions
Version: 2.0.4
Summary: FABRIC Python Client Library and CLI Extensions
Home-page:
Author:
Author-email: Paul Ruth <pruth@renci.org>, Komal Thareja <kthare10@renci.org>
License:
Location: /opt/conda/lib/python3.11/site-packages
Editable project location: /home/fabric/fabrictestbed-extensions
Requires: atomicwrites, click, fabric_ceph_client, fabric_fss_utils, fabric_paramiko_expect, fabrictestbed, ipycytoscape, ipyleaflet, ipython, ipywidgets, jinja2, pandas, paramiko, tabulate
Required-by: SliceCommander
Any help is appreciated, thanks!
Hi Arash,
I’m looking at this will push out a fix soon.
Best,
Komal
Hi Arash,
Fix has been deployed on beyond bleeding edge container. Will be available in bleeding edge container later this evening. Please let me know if you run into any more issues. Apologies for the inconvenience.
Best,
Komal
Thank you, Komal. It works now.