Orka known issues and fixes by version

Use this page to match a problem you’re seeing to the Orka release that fixed it. Each entry links to the full release note. To check which version your cluster runs, use orka3 version. The Operator Version line shows the cluster’s release. A patch release only updates the components it changes, so the API Version line can show an earlier patch version (on 3.6.4, the API server stays at 3.6.3). See Orka component versions by release. If a fix is in a later release than yours, see How to upgrade your Orka cluster, or contact MacStadium support.

Open known issues

The following table lists known issues that don’t have a fix yet.

Symptom	Affects	Workaround
After you commit changes to an image under the same name and tag, `orka3 imagecache add` reports it as already cached on some nodes and skips re-caching	3.6.4	Fixed in 4.0.0. On 3.6, remove and re-add the cached image, or deploy a VM from it once. See 3.6.4.
A VM deployment fails with a generic error while `orka3 imagecache remove` runs for the same image on the same node	3.6.2 and later	Don’t remove a cached image while VMs are deploying from it on that node. See 3.6.2.
VMs deployed from an image on one node fail with `Unable to deploy the VM as the underlying VM process has crashed`, while the same image works on other nodes. The node ran out of disk space while importing the image, for example during two imports at once, and kept the incomplete image.	3.6.4 and earlier	Fixed in 4.0.0. On 3.6, contact MacStadium support to remove the incomplete cached image, so the node downloads it again in full on next use.

Fixed issues

Networking

The following table lists fixed networking issues.

Symptom	Fixed in
VMs deployed to a node with an IP address recently freed by another VM have hung NFS mounts, caused by stale firewall connection state from the previous VM	3.6.3
VMs using NAT networking on M4 Pro nodes intermittently can’t reach the internet or LAN	3.5.1
Calico network plugin setup fails on Orka 3.5 clusters	3.6.0
Self-managed clusters with public NAT IPs: the Kubernetes API TCP ingress route needs updating (run the playbook in the release note)	3.6.0

Image caching

The following table lists fixed image caching issues.

Symptom	Fixed in
Stuck caching jobs never fail; with four or more stuck on one node, no new VMs can deploy there	3.6.4
Cached images are evicted unexpectedly (regression in 3.6.3)	3.6.4
`orka3 imagecache add` with a `:latest` tag creates duplicate or stale cache entries	3.6.3
The API rejects single-encoded image names in the image cache path	3.6.3
`orka3 imagecache add` silently fails for nodes in custom namespaces	3.5.1
VMs pull an image even though it’s already running on the node	3.5.0
VMs keep running a stale NFS image after the source image is updated, with no error	3.4.2

VMs and nodes

The following table lists fixed VM and node issues.

Symptom	Fixed in
Long-lived VMs deadlock	3.6.2
Disk performance regression on Intel nodes	3.6.2
The operator fails to configure Intel VMs	3.6.0
Sequoia guests ignore a custom display resolution (also needs the 3.5.2 VM tools in the image)	3.5.2
Image deletion, copying, and tagging fail with macOS Tahoe 26.0	3.5.2
Stopped VMs aren’t removed by orphan VM cleanup	3.5.0
Apple silicon nodes become non-operational under high-volume deployment: VMs aren’t deleted, nodes run out of space, and VMs get no valid MAC address	3.4.1

OCI images and registries

The following table lists fixed image and registry issues.

Symptom	Fixed in
VM image push retries fail intermittently	3.6.0
`orka3 vm save` fails when the cluster uses OCI image storage	3.6.0
Pulling public images from GitHub Container Registry fails when registry credentials are configured	3.5.2

CLI, API, and access

The following table lists fixed CLI, API, and access issues.

Symptom	Fixed in
Users added to a namespace created with `--enable-custom-pods` don’t get dev-level access (existing namespaces need a support request)	3.6.4
`orka3 node list -o wide` shows incorrect resource usage for nodes in non-default namespaces (display only, no effect on scheduling)	3.5.1
Service accounts lose their permissions after Ansible maintenance	3.5.1
`orka3 login` with SSO fails with “invalid ID token: illegal base64 data” (also update the CLI)	3.5.1

Self-managed deployments

The following table lists fixed issues specific to Orka Anywhere.

Symptom	Fixed in
Virtual kubelet kubeconfig creation fails on on-premises deployments	3.6.0

Upgrade notes

Some upgrades need action on your side. Check the release note before you upgrade:

3.4 to 3.5: the upgrade deletes VMs. Save or back up VMs first, then redeploy them. See 3.5.0.
3.6.2: clusters with public NAT IPs or a custom API domain use TLS based on the API, so a CLI configured with the internal IP times out. Point the CLI at your public URL. See 3.6.2.

MacStadium

Orka

MacStadium VDI

IaaS

Orka known issues and fixes by version

Open known issues

Fixed issues

Networking

Image caching

VMs and nodes

OCI images and registries

CLI, API, and access

Self-managed deployments

Upgrade notes

​Open known issues

​Fixed issues

​Networking

​Image caching

​VMs and nodes

​OCI images and registries

​CLI, API, and access

​Self-managed deployments

​Upgrade notes

Open known issues

Fixed issues

Networking

Image caching

VMs and nodes

OCI images and registries

CLI, API, and access

Self-managed deployments

Upgrade notes