Hi,
Just to let you know that this morning, some jobs used all the nodes that we still had already in "provisioned" state at the Duffy level, but that after that, no nodes were available to fulfil the other requests.
This is due to a network issue we suffered during the week-end (and already contacted the IT team managing the switches to analyze the root cause), and because of that, the dispatcher process (in charge of deploying in advance the duffy nodes) put all provisioning steps into failed mode.
I updated that back to normal, and dispatcher started to reinstall nodes and put those back into the "Ready" pool.
Sorry for the inconveniences
I also even face similar issue intermittently.
Got resolved after some time.
Regards, Budh Ram Gurung Software Engineer - Devtools
On Mon, May 8, 2017 at 2:22 PM, Fabian Arrotin arrfab@centos.org wrote:
Hi,
Just to let you know that this morning, some jobs used all the nodes that we still had already in "provisioned" state at the Duffy level, but that after that, no nodes were available to fulfil the other requests.
This is due to a network issue we suffered during the week-end (and already contacted the IT team managing the switches to analyze the root cause), and because of that, the dispatcher process (in charge of deploying in advance the duffy nodes) put all provisioning steps into failed mode.
I updated that back to normal, and dispatcher started to reinstall nodes and put those back into the "Ready" pool.
Sorry for the inconveniences
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Budh Gurung -
Fabian Arrotin