Date: Thu, 28 Jan 2016 09:04:25 -0500 From: Rick Miller <vmiller@hostileadmin.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: uname exits 0, no output Message-ID: <CAHzLAVHTqN_Ke%2B7xmVCYMo1n1Ghaxq4eS-T0ze5YNAG5gK0AgQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi all, First, some background before describing odd behavior: We have automated CI (Continuous Integration) tests which run in openstack for each code commit to our application. These tests spawn a new environment (network, Vms etc), configure it, execute the tests & then destroy the env at the end. Now, to the odd behavior: sometimes, the tests execute a =E2=80=9Cuname -a= =E2=80=9D command via ssh because it needs to know the operating system version. The odd behavior is that approximately 5% of the time =E2=80=9Cuname -a=E2=80=9D on= FreeBSD 10.x openstack instances returns exit-code 0 (i.e. Successful) but produces no output on stdout. This causes the tests to fail; which causes the whole CI-execution to be marked as a failure. This behavior is only exhibited on the BSD hosts and not Linux hosts. I am trying to track down what the likely cause is. I'm hoping someone might be able to shed some light on the BSD image itself. Could there be something in the OS and/or the OpenSSH versions or libraries on BSD which could explain this behavior? --=20 Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVHTqN_Ke%2B7xmVCYMo1n1Ghaxq4eS-T0ze5YNAG5gK0AgQ>