1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 436 through 450 (of 466 total)
  • Author
    Posts
  • Komal Thareja
    Participant

      Update is complete!

      Komal Thareja
      Participant

        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 2 years, 7 months ago by Komal Thareja.
        Komal Thareja
        Participant

          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
          Participant

            This maintenance is now complete.

            in reply to: Exception: [Errno 99] Cannot assign requested address #3585
            Komal Thareja
            Participant

              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

              in reply to: Maintenance on FABRIC-Network AM – 10/26/2022 [COMPLETED] #3377
              Komal Thareja
              Participant

                Maintenance on FABRIC-Network AM – Completed

                in reply to: Cannot delete slice in “StableError” #3339
                Komal Thareja
                Participant

                  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, 10 months ago by Komal Thareja.
                  in reply to: Does delete_slice.ipynb work on dead or closing slices? #3315
                  Komal Thareja
                  Participant

                    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.

                    in reply to: Min Length of Slice Name Differs #3303
                    Komal Thareja
                    Participant

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

                      in reply to: fabric-cli does not produce valid JSON #3270
                      Komal Thareja
                      Participant

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

                        in reply to: fabric-cli does not produce valid JSON #3246
                        Komal Thareja
                        Participant

                          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.

                          in reply to: Slices stuck in “Closing” or “Configuring” state #3174
                          Komal Thareja
                          Participant

                            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.

                            in reply to: Two problem I am having so far for logging into FABRIC VMs #3136
                            Komal Thareja
                            Participant

                              No worries, I was able to reproduce this issue by creating a slice from the GUI. We will work on resolving this, thank you for helping us identify this problem and make the testbed better. Appreciate your feedback.

                              in reply to: Two problem I am having so far for logging into FABRIC VMs #3134
                              Komal Thareja
                              Participant

                                We are working to investigate this behavior and would appreciate if you please share the slice id of the slice created from the portal? This would help us gather the required information quickly.

                                Appreciate your help!

                                Thanks

                                in reply to: renew slice did not fully work #3078
                                Komal Thareja
                                Participant

                                  Also, from previous conversation, I found that the slice was renewed on Sep 8. Could you please let us know when did you loose SSH connectivity?

                                Viewing 15 posts - 436 through 450 (of 466 total)