Forum Replies Created
-
AuthorPosts
-
@Sanjana – your config looks correct. Could you please try creating a slice and try SSH? If the SSH still fails, could you please share your public key: /home/fabric/work/fabric_config/slice_key.pub
I can verify the correct key is being passed to the VM or not from backend.
Thanks,
Komal
@Vaiden – Issue has been resolved. You may have to do the following to resolve in your slice:
- Remove MAX VM and FabNetv4 Network Service connected to it
- Submit
- Add Max VM and FabNetv4 Network Service
- Submit
Thanks,
Komal
-
This reply was modified 1 year ago by
Komal Thareja.
1 user thanked author for this post.
February 6, 2024 at 11:28 am in reply to: Maintenance on MAX – 02/06/2024 (9:00am-12:00pm EST) #6532Issue has been resolved and maintenance is complete.
Thanks,
Komal
@Vaiden – we have identified the issue and will let you know once it is resolved. For more updates follow here: https://learn.fabric-testbed.net/forums/topic/maintenance-on-max-02-06-2024-900am-1200pm-est/
February 5, 2024 at 4:43 pm in reply to: Unable to create new directory under /sys/ to configure NVMe-oF #6525@Shoaib – Please consider running the commands as sudo
sudo <replace with command
Thanks,
Komal
@Sanjana,
Could you please share the output of following commands:?
cat ~/work/fabric_config/fabric_rc
cat ~/work/fabric_config/ssh_config
ls -ltr ~/work/fabric_config
Thanks,
Komal
@Sanjana – Could you please remove this file if it exists
~/work/fabric_config/ssh_config
and run thevalidate_and_config.ipynb
notebook again?Please try SSH to VMs via command line and share the error you see if it still fails.
Thanks,
Komal
@Sanjana – glad to hear that you were able to create a slice successfully, are you still facing errors when you SSH to the VMs?
Thanks,
Komal
@Sanjana,
Could you please follow the notebook:
jupyter-exanples-1.6.*/configure_and_validate.ipynb
to ensure your configuration is correct? Please try creating a slice after that and let us know if you still run into errors.Thanks,
Komal
1 user thanked author for this post.
Good morning Nagmmat,
This looks like a config issue – specifically incorrect/missing project id. Could you please verify your config using the notebook
jupyter-examples-1.6.*/configure_and_validate.ipynb
?Please let us know if you still run into errors.
Thanks,
Komal
Good morning Bruce,
This error can be ignored. We will fix this in the next version.
Thanks,
Komal
Hello Bruce,
This is because of an incompatible API change. If you are running JH container, please remove any entries in `/home/fabric/work/fabric_config/requirements.txt’ and restart your JH container via File -> Hub Control Panel -> Stop My Server -> Start My Server.
Compatible versions:
JH 1.5 =>
fabrictestbed-extensions==1.5.6
JH 1.6 =>
fabrictestbed-extensions==1.6.2
Thanks,
Komal
@Vaiden
You slice is in state
ModifyError
For any further modifications to your slice, you need to run the following commands:slice=fablib.get_slice(name=slice_name) slice.modify_accept()
Regarding the Authentication Error. Please check if you Bastion key has expired and SSH keys are setup properly. You can use the notebook config_and_validate.ipynb to update/validate SSH keys and your config.
Snapshot of Slice State:
Slice Name: ServiceX_NDN_Proxy_tcp_4nodes Slice ID: 61c1d373-b3b6-472f-a34a-3dd6dac8c809 Project ID: 7a5adb91-c4c0-4a1c-8021-7b6c56af196f Project Name: MF Graph ID: 34d3dd32-ff1f-4fc2-bad3-c1e542584c9c Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 14098c5d-6c93-4d8a-b67b-a0bbdb765da2, email: William.Logan1@uky.edu} Slice state: ModifyError Lease time: 2024-05-18 18:27:07+00:00
Also, looking at
/tmp/fablib/fablib.log
would provide more information for the failure cause for Authentication error.Thanks,
Komal
-
This reply was modified 1 year ago by
Komal Thareja.
Hi Manas,
Thank your for bearing with me. I think I finally have a fix for the issue. I have applied the patch on UCSD and STAR for now and have not been able to reproduce it there.
I would appreciate if you also try at these two sites and share your observation. Hopefully it works consistently now.
Appreciate your help!
Thanks,
Komal
January 31, 2024 at 5:41 pm in reply to: Maintenance on Network AM – 01/31/2024 (5:00pm-5:30pm EST) #6492Maintenance has been completed and testbed ready to use!
Thanks,
Komal
-
AuthorPosts