[Komal Thareja]

Hi Fraida,

Thank you for reporting this issue. There was a leaked network service. I have cleared it up. Please try your slice again and it should work. Regarding the Slice state, it is a bug and we working on it.

Thanks,

Komal

[Komal Thareja]

The maintenance is complete. Testbed is open for use!

[Komal Thareja]

Thanks Gregory for reporting this. It was indeed a bug when running in script mode. The fix is now available on the main branch for https://github.com/fabric-testbed/fabrictestbed-extensions. The fix is also available in the “Beyond Bleeding Edge Container”

Once the new version for fabrictestbed-extensions==1.5.4 is pushed to pypi it would be available there as well.

Thanks,
Komal

[Komal Thareja]

Thank you for sharing your slice details! Are you running this as a script?
The difference in behavior could be because of the wait handling in Jupyter Notebook v/s a script.
ModifyOK state indicates that the modify was successful.
You can invoke: slice.update() to move the slice into StableOK state.

Connectivity should work as well. Also, could you please share the script you are running so I can emulate this and address the difference in the behavior of the wait to avoid invoking explicit update.

Thanks,
Komal

[Komal Thareja]

Regarding SSH problem, if the Configure Environment Notebook was ran again assuming the same file name was used for the sliver keys, the sliver private/public keys got overwritten. So the SSH keys in ~/work/fabric_config/ are now different than what is in the VM and thus resulting in SSH failures.

You can verify by ls -ltr ~/work/fabric_config

Thanks,
Komal

[Komal Thareja]

Hi Gregory,

Which container are you using? I tried the Ipv4Ext notebook on the “Beyond Bleeding Edge” IPv6Ext from 1.5.3 container and did not see this issue. Also, if you run into this issue, please do not delete the slice. It will help to get the information for the slice for debugging.

Also, please share the output of the following command from your container:
pip list | grep fabric
cat ~/work/fabric_config/requirements.txt

Thanks,
Komal

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

[Komal Thareja]

Also, please check that the correct Project Id is passed in your configure environment notebook.

[Komal Thareja]

@Bruce – It looks like Fablib was unable to refresh your token. Could you please Restart your JH container and try again?
You can stop your container via File -> Hub Control Panel -> Stop My Server; logout and login again.

Thanks,
Komal

[Komal Thareja]

Thank you for reporting this issue James! The new image pulled some newer jupyter packages which required change in the way Widgets are installed/registered. This was causing the failure. I have updated the image and deployed the fix. Please try your notebook and let us know if you still observe errors.

Appreciate your help with this!

Thanks,

Komal

[Komal Thareja]

Hello Arash,

Please take a look at this article https://learn.fabric-testbed.net/knowledge-base/install-the-python-api/ on setting up FABlib in your local environment instead of using GKE JH containers.

 

Thanks,

Komal

[Komal Thareja]

Hello Bruce,

Thank you for reporting this issue. The default user for default_centos9_stream is cloud-user instead of centos Our configuration was incorrect and has been updated and the issue has been addressed. Please try a slice and let us know if you still observe any failures or errors.

Also, please note the FABlib uses the default user for default_centos9_stream as centosAny execution of the commands via node.execute() should be pass in the username as cloud-user.

node.execute(‘echo Hello, FABRIC from node hostname -s‘, username=”cloud-user”)

We’ll address this in FABLib as well.

Appreciate your feedback!

Thanks,

Komal

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

[Komal Thareja]

Hey Sarah,

Thank you for reporting this issue and using the workaround yesterday. The fix for this issue has been deployed as well.

Thanks,

Komal

[Komal Thareja]

Hello Manas,

Please check from Portal, Experiments -> Manage SSH Keys to ensure that your bastion keys have not expired. This typically happens when your bastion keys have expired. Please regenerate them and upload to your JH container if they have expired.

Thanks,

Komal

[Komal Thareja]

Thank you for sharing the warning message. I have updated the config, could you please try using either 1.4.6 or 1.5.1 container and let me know if the container comes up?

Thanks,

Komal

[Komal Thareja]

Hi Sarah,

When you have the bleeding edge/beyond bleeding edge container running, could you please share the output of the following commands?


ls -lrt /home/fabric/work/
ls -lrt /home/fabric/work/fabric_config


Also, could you please share the warning message you couldn’t upload to kthare10@renci.org

Thanks,
Komal

[Author]

Posts