Hi all, any idea why I see this in all jobs? I have just one job running, so my 10 machines quota is not reached.
24/May/2023 08:52:54:DEBUG:executed 'duffy client --url https://duffy.ci.centos.org/api/v1 --auth-name networkmanager --auth- key $CICO_API_KEY request-session pool=virt-ec2-t2-centos-9s- x86_64,quantity=2': returned 0 24/May/2023 08:52:54:DEBUG:machine content { "error": { "detail": "can't reserve nodes: quantity=2 pool='virt-ec2-t2- centos-9s-x86_64'" } }
Thanks, Vlad
On 24/05/2023 13:01, Vladimir Benes wrote:
Hi all, any idea why I see this in all jobs? I have just one job running, so my 10 machines quota is not reached.
24/May/2023 08:52:54:DEBUG:executed 'duffy client --url https://duffy.ci.centos.org/api/v1 --auth-name networkmanager --auth- key $CICO_API_KEY request-session pool=virt-ec2-t2-centos-9s- x86_64,quantity=2': returned 0 24/May/2023 08:52:54:DEBUG:machine content { "error": { "detail": "can't reserve nodes: quantity=2 pool='virt-ec2-t2- centos-9s-x86_64'" } }
Thanks, Vlad
You can query for pool status and you'd see that actually there is only one available node (ready) so you can't ask for 2 :
duffy client show-pool virt-ec2-t2-centos-9s-x86_64 { "action": "get", "pool": { "name": "virt-ec2-t2-centos-9s-x86_64", "fill_level": 8, "levels": { "provisioning": 0, "ready": 1, "contextualizing": 6, "deployed": 3, "deprovisioning": 0 } } }
On Wed, 2023-05-24 at 13:11 +0200, Fabian Arrotin wrote:
On 24/05/2023 13:01, Vladimir Benes wrote:
Hi all, any idea why I see this in all jobs? I have just one job running, so my 10 machines quota is not reached.
24/May/2023 08:52:54:DEBUG:executed 'duffy client --url https://duffy.ci.centos.org/api/v1%C2%A0--auth-name networkmanager -- auth- key $CICO_API_KEY request-session pool=virt-ec2-t2-centos-9s- x86_64,quantity=2': returned 0 24/May/2023 08:52:54:DEBUG:machine content { "error": { "detail": "can't reserve nodes: quantity=2 pool='virt-ec2-t2- centos-9s-x86_64'" } }
Thanks, Vlad
You can query for pool status and you'd see that actually there is only one available node (ready) so you can't ask for 2 :
aha, what is the pool size? should we wait more for the pool to be emptier? We wait up to 3h for nodes to be ready. And now it looks 2h was enough. Good. We have test suite running for 2.5h so we cannot wait more than 3 as there is the 6h limit.
Thanks, Vlad
duffy client show-pool virt-ec2-t2-centos-9s-x86_64 { "action": "get", "pool": { "name": "virt-ec2-t2-centos-9s-x86_64", "fill_level": 8, "levels": { "provisioning": 0, "ready": 1, "contextualizing": 6, "deployed": 3, "deprovisioning": 0 } } }
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users