cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
311
Views
1
Helpful
2
Replies

RADKit Network Console fails connecting to service: UnboundLocalError

TheoM
Level 1
Level 1

Hi team,

after upgrading to version 1.6.4 the network console fails to connect to service with the following error:

 

Traceback (most recent call last):
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\Scripts\radkit-network-console.exe\__main__.py", line 7, in <module>
sys.exit(run())
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\core.py", line 1130, in __call__
return self.main(*args, **kwargs)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\core.py", line 1635, in invoke
rv = super().invoke(ctx)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "C:\Users\theom\AppData\Local\Programs\Cisco RADKit\env\lib\site-packages\click\decorators.py", line 26, in new_func
return f(get_current_context(), *args, **kwargs)
File "<frozen radkit_client.sync.network_console>", line 2191, in run
File "<frozen radkit_client.sync.network_console>", line 2214, in run_network_console
File "<frozen radkit_client.sync.network_console>", line 812, in cmdloop
File "<frozen radkit_client.sync.network_console>", line 1227, in do_service
UnboundLocalError: local variable '_var_var_42' referenced before assignment

 

The same behavior happens from every upgraded client while noticing that everything works perfectly fine with an older client version 1.5.2.

Any ideas why is this happening?

Thanks

1 Accepted Solution

Accepted Solutions

tvanegro
Cisco Employee
Cisco Employee

Hi ! 

Thanks for reaching out - This is a known issue. The fix will be present in the next release, 1.6.5, which should hopefully be published soon. 

 

Sorry for the inconvenience.

Tristan

View solution in original post

2 Replies 2

tvanegro
Cisco Employee
Cisco Employee

Hi ! 

Thanks for reaching out - This is a known issue. The fix will be present in the next release, 1.6.5, which should hopefully be published soon. 

 

Sorry for the inconvenience.

Tristan

TheoM
Level 1
Level 1

Thanks Tristan.

Looking forward to the next release.