Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CC can exceed quota with two VM sizes in a node array

Open
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
cloud

Research direction

Start by inspecting the two templates in cyclecloudprov_templates and the nodearray configuration using MaxNumber and MaxCoreCount. Reproduce the VM0 and VM1 quota scenario, then determine where capacity is counted across the array. Done means VM0 cannot exceed its stated vCPU quota while both VM sizes remain selectable.

Written by the indexing model from the issue text.

Description

VM0 1000 vCPU quota
VM1 10000 vCPU quota
Two templates in cyclecloudprov_templates with MaxNumber set. Initially MaxNumber was set slightly higher where vCPU * MaxNumber > vCPU Quota for VM0. MaxCoreCount on nodearray set to 11000.

The jobs specify which VM they are running on. So it's not a priority. They were able to exceed the quota for VM0.

Dominant language
HTML
Stars
10
Forks
15
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/cyclecloud-lsf

All issues in Azure/cyclecloud-lsf

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.