softwarefactory-project-zuul[bot]
commented
6 months ago Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/bada95d290a24313838ca3b6b737ff38
:x: ansible-test-network-integration-junos-vsrx-netconf-python36-stable29 FAILURE in 14m 44s (non-voting) :heavy_check_mark: ansible-test-network-integration-junos-vsrx-netconf-python36-stable211 SUCCESS in 1h 18m 12s :heavy_check_mark: ansible-test-network-integration-junos-vsrx-netconf-python39-stable212 SUCCESS in 1h 05m 28s :x: ansible-test-network-integration-junos-vsrx-netconf-python39 RETRY_LIMIT in 9m 09s :x: ansible-test-network-integration-junos-vsrx-network_cli-python36-stable29 FAILURE in 13m 40s (non-voting) :heavy_check_mark: ansible-test-network-integration-junos-vsrx-network_cli-python36-stable211 SUCCESS in 17m 37s :heavy_check_mark: ansible-test-network-integration-junos-vsrx-network_cli-python39-stable212 SUCCESS in 15m 35s :x: ansible-test-network-integration-junos-vsrx-network_cli-python39 RETRY_LIMIT in 10m 15s :x: ansible-test-network-integration-junos-vsrx-network_cli-libssh-python36-stable29 FAILURE in 26m 53s (non-voting) :x: ansible-test-network-integration-junos-vsrx-network_cli-libssh-python36-stable211 RETRY_LIMIT in 4m 27s :heavy_check_mark: ansible-test-network-integration-junos-vsrx-network_cli-libssh-python39-stable212 SUCCESS in 20m 24s :x: ansible-test-network-integration-junos-vsrx-network_cli-libssh-python39 RETRY_LIMIT in 9m 50s :x: ansible-test-network-integration-vyos-paramiko-python39-devel NODE_FAILURE Node request 200-0007220656 failed in 0s :x: ansible-test-network-integration-vyos-paramiko-python39-stable214 NODE_FAILURE Node request 200-0007220657 failed in 0s :x: ansible-test-network-integration-vyos-paramiko-python39-stable213 NODE_FAILURE Node request 200-0007220658 failed in 0s :x: ansible-test-network-integration-vyos-paramiko-python39-stable212 NODE_FAILURE Node request 200-0007220659 failed in 0s :x: ansible-test-network-integration-vyos-paramiko-python36-stable29 NODE_FAILURE Node request 200-0007220660 failed in 0s (non-voting) :x: ansible-test-network-integration-vyos-libssh-python39-devel NODE_FAILURE Node request 200-0007220661 failed in 0s :x: ansible-test-network-integration-vyos-libssh-python39-stable214 NODE_FAILURE Node request 200-0007220662 failed in 0s :x: ansible-test-network-integration-vyos-libssh-python39-stable213 NODE_FAILURE Node request 200-0007220663 failed in 0s :x: ansible-test-network-integration-vyos-libssh-python39-stable212 NODE_FAILURE Node request 200-0007220664 failed in 0s :x: ansible-test-network-integration-vyos-libssh-python36-stable29 NODE_FAILURE Node request 200-0007220665 failed in 0s :heavy_check_mark: build-ansible-collection SUCCESS in 13m 32s :x: ansible-test-network-integration-ansible-netcommon-junos-vsrx-netconf-python39 RETRY_LIMIT in 6m 14s :x: ansible-tox-linters FAILURE in 12m 28s :heavy_check_mark: ansible-galaxy-importer SUCCESS in 5m 06s
rohitthakur2590
SUMMARY
The
INFOlog level is usually not enough to get useful information from the libssh regarding the low-level issues that we would like to be able to resolve. This can be made even more fine grained, but I do not think less verbose logs would be much useful anyway.Related is the issue in pylibssh, which maps the DEBUG verbosity to something that is not debug in libssh itself:
https://github.com/ansible/pylibssh/pull/597
If needed separate change before the pylibssh is fixed, using
logging.CRITICALcould do.ISSUE TYPE
COMPONENT NAME
connection/libssh