Carlo Lobrano

icon indicating a website link https://blog.carlolobrano.com

icon company Red Hat icon location Cagliari, Italy icon location Senior Software Engineer @ RedHat. Love Linux, Python and Golang, addicted to NeoVIM. Having fun learning every day.

Results 97 comments of Carlo Lobrano

SNR didn't reboot the node

I see. That unfortunately cleaned up the logs too, so we don't see what was happening. Was it easy to reproduce? If so, please take the must gather before rebooting...

SNR didn't reboot the node

Did you see if there was any workload stuck in Termination phase?

SNR didn't reboot the node

> I am seeing in the SNRcontrollerManager previous logs "The unhealthy node assumed to been rebooted" Yes, SNR is unable to detect, in fact, whether or not the node is...

SNR didn't reboot the node

Hey, could you share the must-gather of this run?

Initial tests for Two Nodes OCP with Fencing (TNF) cluster

Temporarily converting it to draft to investigate a crash

Initial tests for Two Nodes OCP with Fencing (TNF) cluster

Ready again for review

Initial tests for Two Nodes OCP with Fencing (TNF) cluster

/test e2e-metal-ovn-two-node-fencing

Initial tests for Two Nodes OCP with Fencing (TNF) cluster

/test e2e-metal-ovn-two-node-fencing

Initial tests for Two Nodes OCP with Fencing (TNF) cluster

/test e2e-metal-ovn-two-node-fencing

dstask import-tw or dstask-import tw?

I also have this problem, even using `cat`. ``` cat taskwarrior.json| ./dstask-import-linux-amd64 tw failed to decode JSON from stdin ``` I checked with `jq` that the taskwarrior json export is...