QualiSystems / QualiSystems/cloudshell-cli

Explore an issue

Abierto
#101 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

help wanted Ready to Take
Lenguaje dominante
Python
Estrellas
7
Forks
5
Merge medio
20 min
PR fusionados (30 d)
1

Descripción

2020-03-24 09:24:50,197 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect
2020-03-24 09:24:50,322 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect root#
2020-03-24 09:24:50,539 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect Command: commit
2020-03-24 09:24:50,794 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect commit
2020-03-24 09:24:51,055 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect
2020-03-24 09:24:51,055 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 expect_session - hardware_expect
2020-03-24 09:25:21,059 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 session_pool_manager - remove_session Removing session
2020-03-24 09:25:21,060 [DEBUG]: QS.JuniperLSCP_105.202.Thread-5 session_manager_impl - remove_session SSH session was removed
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit Error occurred
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit Traceback (most recent call last):
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\paramiko\channel.py", line 699, in recv
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit out = self.in_buffer.read(nbytes, self.timeout)
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\paramiko\buffered_pipe.py", line 164, in read
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit raise PipeTimeout()
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit paramiko.buffered_pipe.PipeTimeout
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit During handling of the above exception, another exception occurred:
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit Traceback (most recent call last):
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\session\ssh_session.py", line 137, in _receive
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit byte_data = self._current_channel.recv(self._buffer_size)
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\paramiko\channel.py", line 701, in recv
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit raise socket.timeout()
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit socket.timeout
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit During handling of the above exception, another exception occurred:
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit Traceback (most recent call last):
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\session\expect_session.py", line 152, in _receive_all
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit read_buffer += self._receive(0.1, logger)
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\session\ssh_session.py", line 140, in _receive
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit raise SessionReadTimeout()
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit cloudshell.cli.session.session_exceptions.SessionReadTimeout
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit During handling of the above exception, another exception occurred:
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit Traceback (most recent call last):
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\Windows\TEMP\tmpev0m0ury.zip_env\driver.py", line 141, in Deploy
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit int_list = ls_flow.create_ls(ls_name, int_list)
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\Windows\TEMP\tmpev0m0ury.zip_env\driver_files\flows.py", line 47, in create_ls
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit commit_rollback.commit()
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\networking\juniper\command_actions\commit_rollback_actions.py", line 25, in commit
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit self._cli_service, command_template.COMMIT
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\command_template\command_template_executor.py", line 60, in execute_command
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit **self.optional_kwargs
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\service\cli_service_impl.py", line 143, in send_command
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit **kwargs
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\session\expect_session.py", line 266, in hardware_expect
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit read_buffer = self._receive_all(timeout, logger)
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit File "C:\ProgramData\QualiSystems\venv\Juniper_LS_Cloud_Provider_2_10\lib\site-packages\cloudshell\cli\session\expect_session.py", line 158, in _receive_all
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit self.class.name, "Socket closed by timeout"
2020-03-24 09:25:21,061 [ERROR]: QS.JuniperLSCP_105.202.Thread-5 logging_session - exit cloudshell.cli.session.session_exceptions.ExpectedSessionException: ('JuniperSSHSession', 'Socket closed by timeout')
JuniperLSCP_105.202--24-Mar-2020--09-24-22.log

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Empieza con driver.py en Deploy y driver_files/flows.py en create_ls; después, sigue el rastro de commit_rollback_actions.py y del session receive stack mostrado en el informe. Reproduce el Juniper commit timeout si es posible; el issue no define cuál es el comportamiento esperado ni cómo debería ser completion.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
cli, networking
Tipo de issue
Error
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
15/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.