Container remains in container creating state

asked 2022-06-25T08:31:28.92+00:00
Nikheel Jain 136 Reputation points

kubectl get pods -n teams-recording-bot
output:
NAME READY STATUS RESTARTS AGE
teams-recording-bot-0 0/1 ContainerCreating 0 42m

can't setup certifcates:
kubectl get cert -n teams-recording-bot
NAME READY SECRET AGE
ingress-tls False ingress-tls 41m

kubectl logs -n teams-recording-bot teams-recording-bot-0
Error from server (BadRequest): container "recording-bot" in pod "teams-recording-bot-0" is waiting to start: ContainerCreating

pod logs:
[Pod] [teams-recording-bot-0] FailedMount: Unable to attach or mount volumes: unmounted volumes=[certificate], unattached volumes=[kube-api-access-bnvqt certificate]: timed out waiting for the condition
11 mins ago [Pod] [teams-recording-bot-0] FailedMount: Unable to attach or mount volumes: unmounted volumes=[certificate], unattached volumes=[certificate kube-api-access-bnvqt]: timed out waiting for the condition
1 min ago [Pod] [teams-recording-bot-0] FailedMount: MountVolume.SetUp failed for volume "certificate" : secret "ingress-tls" not found
682 msecs ago [Pod] [teams-recording-bot-0] Scheduled: Successfully assigned teams-recording-bot/teams-recording-bot-0 to aksscale000000

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,104 questions
No comments
{count} votes

Accepted answer
  1. answered 2022-07-02T04:27:19.613+00:00
    risolis 5,921 Reputation points

    Hello @Nikheel Jain

    I hope you are doing fine.

    I would like to provide my humble opinion on this case scenario.

    • AKS is not considered as IaaS service since it is considered as PaaS service(Just a friendly reminder)
    • It is true that for this set up that you are trying to get it done, You need a windows server instance which is IaaS service.
    • Then, WebApp can not be used for this due to the following explanation below:

    217016-image.png

    Furthermore, there is a good point to be shared as shown below:

    Use one bot channel registration per environment, since your endpoint changes when you switch between local development, staging, and production environments.
    Deleting the Teams channel registration will cause a new pair of keys to be generated when it is re-enabled. This invalidates all 29:xxx and a:xxx IDs that the bot may have stored for proactive messaging.

    I hope this can help you the behavior observed until now buddy : )

    Looking forward to your feedback,

    Best Regards,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


7 additional answers

Sort by: Most helpful
  1. answered 2022-06-25T09:25:27.063+00:00
    Manu Philip 14,031 Reputation points Microsoft MVP

    As the error message indicates, there is a mount failure : FailedMount: MountVolume.SetUp failed for volume "certificate"
    Probably, you need to check the reason behind the mount failure and try creating pods again

    No comments

  2. answered 2022-06-25T10:26:43.5+00:00
    Nikheel Jain 136 Reputation points

    Can't find any concrete reason for not mounting


  3. answered 2022-06-28T11:24:43.837+00:00
    HellBoy 6 Reputation points

    Redefine pods may help


  4. answered 2022-06-30T07:25:53.147+00:00
    Harsh Basuta 16 Reputation points

    As the error message indicates, there is a mount failure : FailedMount: MountVolume.SetUp failed for volume "certificate"
    Probably, you need to check the reason behind the mount failure and try creating pods again!!!!

    No comments