microsoft / microsoft/hcsshim

hcnDeleteNamespace failed in Win32: The specified request is unsupported (0x803b0015)

Open
#2,155 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
694
Forks
304
Avg merge
1d 19h
Merged PRs (30d)
28

Description

We are seeing errors in the upstream Kubernetes tests that have this error in containerd. I've posted some more details in https://github.com/kubernetes/kubernetes/issues/125195#issuecomment-2145586842

We are also seeing this error in the logs:

``
[1429] {"Timestamp":"2024-05-29T00:52:27.9870075+00:00","ProviderName":"ContainerD","Level":4,"Keywords":0,"Payload":{"ID":1,"EventName":"LogrusEntry","TraceEventProcessID":5084,"TraceEventProcessName":"","Message":"Container to stop "b6eacb5bab6ce42f8f0d173a9b0fae2175623c982adbf2cd8f3b9f89825e8215" must be in running or unknown state, current state "CONTAINER_EXITED"","Time":"2024-05-29T00:52:28.0224034+00:00"}}


The hns service crashed:

5/29/2024 12:21:00 AM 7031 Error The Host Network Service service terminated
unexpectedly. It has done this 1 time(s). The
following corrective action will be taken in 120000
milliseconds: Restart the service.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the upstream Kubernetes tests and the linked Kubernetes issue for the surrounding failure details. Review the containerd log showing the exited container and the HNS service crash report, then trace the hcnDeleteNamespace failure in hcsshim. Done means identifying a reproducible cause and restoring successful namespace deletion without the HNS service crashing.

Written by the indexing model from the issue text.

Assessment

Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.