[Komal Thareja]

Maintenance is complete. UTAH and MICH sites are also available for use.

[Komal Thareja]

Hello,

Could you please run the configure notebook from ‘Jupiter-examples-rel1.4.1’ directory and then try the hello world example again?

From the screenshot it looks like environment was rolled back to Release 1.3.8.

Thanks,
Komal

[Komal Thareja]

Update is complete. All sites except MICH and UTAH are available for use. We will share another update when MICH and UTAH are available.

NOTE: Please install/upgrade to latest version of fabrictestbed-extensions if you are accessing FABRIC resources from outside the JupyterHub environment.

pip install fabrictestbed-extensions==1.4.0

[Komal Thareja]

Update is complete!

[Komal Thareja]

This looks like an issue with the Project ID setting in fabric_config/fabric_rc. Could you please re-run the notebook: Configure Environment and verify that Project ID being set is same as the Project Id in the portal?

Setup Environment
Configure Environment: Configure you Environment including creating the fabric_rc and ssh_config files.

• This reply was modified 1 year, 10 months ago by Komal Thareja.

[Komal Thareja]

Hello Nagmat,

Please Restart your Jupyter Container via File -> Hub Control Panel -> Stop My server, followed by Start My Server.
Please let us know if you still face this error.

Thanks,
Komal

[Komal Thareja]

This maintenance is now complete.

[Komal Thareja]

Hi Durbek,

Thank you for reporting this issue. This seems to be an issue in older version of Fablib and has been addressed in the later versions.

The default notebook creates VM with default_rocky_8 image (which comes with NetworkManager) and as part of post_boot_config Fablib tries to stop it. This is not the case for the default_ubuntu images. The failure observed is when Fablib is trying to stop the Network manager.

I would recommend following steps to help address this issue:

1. Please update fabric_config/requirements.txt in your JH container to include the following statement:
fabrictestbed-extensions==1.3.3

2. Restart your JH container

3. Try your experiment again, you may see some traces like which can be ignored.
sudo: nmcli: command not found

4. You would also need to update the cells where IP addresses are configured on the VMs for ubuntu to include following two steps after ip addr show:

Node1:

stdout, stderr = node1.execute('sudo apt install net-tools')
stdout, stderr = node1.execute(f'sudo ifconfig {node1_iface.get_os_interface()} up')

Node2:

stdout, stderr = node2.execute('sudo apt install net-tools')
stdout, stderr = node2.execute(f'sudo ifconfig {node2_iface.get_os_interface()} up')

Thanks,
Komal

[Komal Thareja]

Maintenance on FABRIC-Network AM – Completed

[Komal Thareja]

Hi George,

Could you please share the Slice ID for your slice? Please note that Slice Delete is an asynchronous operation. Slice might show stay in StableError for a bit until all the associated resources with it are deleted/released.

NOTE: Deletion was a synchronous operation earlier but was made asynchronous recently as part of performance optimizations.

Thanks,
Komal

• This reply was modified 2 years, 1 month ago by Komal Thareja.

[Komal Thareja]

User can not delete Dead and Closing slices. Dead and Closing slices do not have any Active resources associated with them as they have been deleted. Portal does not show Dead and Closing slices by default. If you do want to see the Dead and Closing slices on the portal you can check the check box “Include Dead and Closing” Slices. We periodically delete the Dead and Closing slices older than 30 days.

[Komal Thareja]

Thank you Charles for reporting this issue. It’s a bug in the code. We will fix it.

[Komal Thareja]

JupyterHub has been updated with the CLI containing the fixes for JSON outputs.

[Komal Thareja]

Thank you Timothy and Sajith for your contributions! Appreciate it! I have approved the PR and merged to the master branch. Will create a new release and push to Jupyter Hub.

[Komal Thareja]

Slices in Closing state do not have any resources allocated to them. They can be ignored. They stay in the Closing state as the confirmation for the delete response from the various Sites is not received (potentially because of the Kafka timeouts). These slices do not prevent the creation of new slices with the same name. We are working to improve the Kafka timeouts and would work to address the issue of Closing slices in the upcoming release.

Slices in Configuring state would prevent the creation of a new slice with the same name. I checked all the slices listed above and they are all in Closing state.

Thank you so much for sharing your observations and help us make the testbed better.
Please do share the slice id of the slices in Configuring state if you do run into them again.

[Author]

Posts