[Komal Thareja]

@Acheme – Thank you for providing the solution for this issue. Appreciate it!

 

I also wanted to add that Apache Web Server notebook was a bit outdated and not inline with latest Fablib API. I have updated the notebook so that it uses latest Fablib APIs which take care of the networking as well and does not rely on user explicitly configuring IP addresses.

If needed, please try the latest version of the notebook from Github: https://github.com/fabric-testbed/jupyter-examples/blob/main/fabric_examples/complex_recipes/apache_web_server/apache_web_server.ipynb

 

Thanks,

Komal

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

[Komal Thareja]

Should be resolved now. I just tried a slice and it worked.

Thanks,

Komal

[Komal Thareja]

Hi Acheme,

 

We are noticing intermittent connectivity issues with TACC switch, resulting in the Network Services failing to provision. That’s resulting the Network being set to None. We are working to resolve this issue and will keep you posted.

 

Thanks,

Komal

[Komal Thareja]

Hi Acheme,

Thank you for reporting this issue. TACC worker tacc-w1 where VMs were spawned had issues. We have recovered the worker and provisioning should work now.

Thanks,

Komal

[Komal Thareja]

Yes either of the following should work.

Spring 2024 container –fabrictestbed-extensions==1.6.0 or

Fall 2023 container – fabrictestbed-extensions==1.5.6

Thanks,

Komal

[Komal Thareja]

Hi Nirmala,

Which JH container are you using? This error typically happens due to a version mismatch for Fablib. Please see below:

Fablib – if you are still using Release 1.5, please update fablib using the command:

pip install fabrictestbed-extensions==1.5.6

Also, if you face issues running notebooks on JH, please ensure there are no entries for fabrictestbed-extensions  in fabric_config/requirements.txt. If you have any entries there, Please remove them and restart your JH container.

Thanks,

Komal

[Komal Thareja]

Network model has been updated and maintenance is complete!

[Komal Thareja]

@Robin, could you please try to restart your JH container via File -> Hub Control Panel -> Stop My container -> Start My container when you see this error?

Also, the path to replace the token is /home/fabric/.tokens.json . We will fix this in the documentation of it’s incorrect. Also, could you please let us know which JH container are you using?

Thanks,

Komal

[Komal Thareja]

@Lyod –  Fabnetv4Ext notebook has a bug and configures the route incorrectly. We will fix the notebook, sharing the fix needed to the routes below. Hope this helps!

Configure Node1 cell in notebook should change the route as below via EXT gateway, ping should work.

stdout, stderr = node1.execute(f'sudo ip route add 0.0.0.0/0 via {network1.get_gateway()}')

Configure Node2 cell in notebook should change the route as below via EXT gateway, ping should work.

stdout, stderr = node2.execute(f'sudo ip route add 0.0.0.0/0 via {network2.get_gateway()}')

 

Thanks,

Komal

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

[Komal Thareja]

Hi Shams,

Could you please remove <> enclosing the project id in /home/fabric/work/fabric_config/fabric_rc and restart your JH container via File -> Hub Control Panel -> Stop Container followed by Start Container?

Please try your notebook again and let us know if you still observe this error.

Thanks,

Komal

[Komal Thareja]

STAR site has 6 worker nodes each with 128 cores = 768 cores. This is same as the previous release.

Oversubscription is not enabled on STAR.

[Komal Thareja]

@Nagmat – Your back should be available in your new JH container as fabric_bkp.tgz. Please start your container and let us know if you face any issues accessing the data.

Thanks,

Komal

[Komal Thareja]

@Nagmat – Could you please stop your JH container? I took backup of your old files and would copy it your new container.

[Komal Thareja]

Minor correction in the version above, Please update the fablib using the command:

pip install fabrictestbed-extensions

 

[Komal Thareja]

@Kriti – the hypervisor on wash-w3 was down this morning and was recovered. Issues on WASH should clear now. I also verified TACC is working as well. Please try your slices again and let us know if you still face errors.

 

@Nagmat – there was a leaked service due to timeout from TACC switch. I have cleaned up the leaked services, your slice provisioning should work as well. Please let us know if you still face errors.

[Author]

Posts