[automated-testing] reboot_nodes_and_wait_to_come_online bug

Vijay Bhaskar Reddy Avuthu vavuthu at redhat.com
Mon Jun 11 11:49:30 UTC 2018


I will take a look.

Regards,
Vijay A

On Mon, Jun 11, 2018 at 5:05 PM, Nigel Babu <nigelb at redhat.com> wrote:

> Oh dear. That's a problem. Vijay, I think you wrote the original code? Can
> you take a look?
>
> On Mon, Jun 11, 2018 at 1:58 PM, Vitalii Koriakov <vkoriako at redhat.com>
> wrote:
>
>> Hello all
>> Noticed such behavior:
>>
>> Reboot nodes with the method reboot_nodes_and_wait_to_come_online. In
>> case when nodes are not online after timeout - it says that all nodes are
>> online.
>> So logs are:
>>
>>
>> 2018-06-08 18:28:00,210 INFO (are_nodes_online) 172.19.2.122 is offline
>> 2018-06-08 18:28:00,211 INFO (reboot_nodes_and_wait_to_come_online)
>> Nodes are offline, Retry after 5 seconds .....
>> 2018-06-08 18:28:05,216 INFO (reboot_nodes_and_wait_to_come_online) All
>> nodes ['172.19.2.86', '172.19.2.126', '172.19.3.113', '172.19.2.122'] are
>> up and running
>>
>> So it doesn't check are nodes online after 5 sec and just return that all
>> nodes are online.
>>
>> Regards,
>> Vitalii
>> _______________________________________________
>> automated-testing mailing list
>> automated-testing at gluster.org
>> http://lists.gluster.org/mailman/listinfo/automated-testing
>>
>
>
>
> --
> nigelb
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20180611/c7ba1306/attachment.html>


More information about the automated-testing mailing list