RATATOSK
← All releases

hamiv2.7.1

Security 1Breaking changes 2Important fixes 8Dependency updates 1Other changes 12

Get hami alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security1

nvidia-mig-parted security fix in Docker builds

Affectsimages built from docker/Dockerfile, docker/Dockerfile.hamimaster, or docker/Dockerfile.withlib(Inferred)

These builds previously installed nvidia-mig-parted v0.10.0, which was affected by the vulnerability. They now install the fixed version, v0.12.2.

Show release-note lines
* fix: upgrade nvidia-mig-parted to v0.12.2 to solve security issues by @Shouren in https://github.com/Project-HAMi/HAMi/pull/1388
github.com/Project-HAMi/HAMi/releases/tag/v2.7.1

Breaking changes2

Cambricon resource-assigned key spelling corrected

AffectsHAMi setups using the Cambricon device implementation(Inferred)

The code and test previously used CAMBRICON_DSMLU_ASSIGHED; both now use CAMBRICON_DSMLU_ASSIGNED.

Show release-note lines
* fix: fix typos by @DSFans2014 in https://github.com/Project-HAMi/HAMi/pull/1434
github.com/Project-HAMi/HAMi/releases/tag/v2.7.1

Iluvatar chart support now defaults to disabled

AffectsHAMi installations using or configuring Iluvatar GPUs

The chart previously exposed generic Iluvatar resource names; it now offers devices.iluvatar.customresources for model-specific resources. The old iluvatar-name, iluvatar-memory and iluvatar-cores flags are replaced by enable-iluvatar.

Evidence“This PR improves support for Iluvatar GPUs, including device plugin (gpu-manager) adaptation, scheduling policy compatibility, and resource isolation and sharing capabilities.” Project-HAMi/HAMi/pull/1399 ↗
Show release-note lines
* Improved support for iluvatar GPUs by @qiangwei1983 in https://github.com/Project-HAMi/HAMi/pull/1399
github.com/Project-HAMi/HAMi/releases/tag/v2.7.1

Important fixes8

  • Terminated-pod device quota cleanup fixed
    Affectspods whose devices have tracked quota usage

    When replicas changed from 1 to 0, the scheduler could process the update event before the deletion event and delete the pod from its manager first, leaving its device quota usage uncleared. The scheduler now removes quota usage from the pod’s recorded devices before deleting it from the pod manager.

    **Fix: Calculation error for quotas by @luohua13 in https://github.com/Project-HAMi/HAMi/pull/1400**
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • GPU plugin-removal health check fixed
    AffectsGPU nodes where the scheduler checks the hami.io/node-handshake annotation

    When the device plugin was removed from a GPU node, CheckHealth returned true, true because the scheduler and plugin updated different prefix values for the annotation. The health check now reads the annotation through util.HandshakeAnnos[devType].

    * Fix: After removing the device plugin from the gpu node, it can still… by @luohua13 in https://github.com/Project-HAMi/HAMi/pull/1456
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • HAMi-core updated to address vLLM-related issues
    AffectsvLLM 0.9.2 on HAMi vGPU with only virtual GPU index 1 exposed (CUDA_VISIBLE_DEVICES=1)

    In this setup, vLLM failed during memory profiling and aborted startup with a host pid is error! message.

    **Update HAMi-core to fix vllm-related issues: #1381 # 1461 by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1478**
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • Resourceqota hard-quota clearing fixed
    AffectsResourceqota custom resources

    When the hard quota was cleared while the custom resource remained, the update handler used the new object to delete quota data, leaving the existing quota uncleared. The scheduler now deletes quota data using the old object before adding it using the updated object.

    **Fix: Calculation error for quotas by @luohua13 in https://github.com/Project-HAMi/HAMi/pull/1400**
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • Helm ClusterRoleBinding role reference name fixed
    AffectsHelm chart installations with a release name or chart name other than hami

    In these installations, the static roleRef.name did not match the ClusterRole name, causing the ClusterRoleBinding to fail.

    * Fix: failed clusterrolebinding when change release name or chart name by @FouoF in https://github.com/Project-HAMi/HAMi/pull/1380
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • Nil pod check added to ReleaseNodeLock
    Affectscode that calls ReleaseNodeLock(Inferred)

    In some cases, passing a nil pod to ReleaseNodeLock could cause a panic.

    * fix: check pod nil in `ReleaseNodeLock` by @DSFans2014 in https://github.com/Project-HAMi/HAMi/pull/1372
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • GetScheduledPods() returns a shallow copy of the pod map
    AffectsHAMi scheduler(Inferred)

    Concurrent iteration and writes to the scheduler's pod map caused a fatal error.

    * Fix concurrent map iteration and map write fatal error. by @litaixun in https://github.com/Project-HAMi/HAMi/pull/1452
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1
  • Concurrent map access fix in nodeManager.ListNodes()
    AffectsHAMi scheduler code that calls nodeManager.ListNodes()(Inferred)

    Concurrent reads and writes to the node map could cause a fatal error. Previously, ListNodes() returned the internal map; it now returns copied node information and omits entries with a nil NodeInfo or nil Node.

    * Fix concurrent map read write fatal error. by @litaixun in https://github.com/Project-HAMi/HAMi/pull/1476
    github.com/Project-HAMi/HAMi/releases/tag/v2.7.1

Dependency updates1

    1 more, none mentioning security
    • * Fix release CI by @archlitchi in https://github.com/Project-HAMi/HAMi/pull/1373
    Other changes12

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.