Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71380

Still waiting to schedule task --> pod not created

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • kubernetes-plugin
    • None

      Our jenkins version is  2.346.3

       

      -Still waiting to schedule task...    -->jobs Hangs

      -Workaround (in test):  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore

       

       

          [JENKINS-71380] Still waiting to schedule task --> pod not created

          fb created issue -
          fb made changes -
          Description Original: {color:#333333}Still waiting to schedule task    -->jobs Hangs{color}

          {color:#333333}There {color}{color:#333333}are no nodes with the label

          Test done: concerning Cloud issue:  if we create a second  cloud on the same  namespaces (kubernetes)  that works, but no explanation why first cloud is not operate anymore{color}           		New: {color:#333333}Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}

          Test done: concerning Cloud issue:  if we create a second  cloud on the same  namespaces (kubernetes)  that works, but no explanation why first cloud is not operate anymore{color}
          fb made changes -
          Description Original: {color:#333333}Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}

          Test done: concerning Cloud issue:  if we create a second  cloud on the same  namespaces (kubernetes)  that works, but no explanation why first cloud is not operate anymore{color}           		New: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround:  if we create a second  cloud on the same  namespaces (kubernetes)  that works, but no explanation why first cloud is not operate anymore{color}
          fb made changes -
          Description Original: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround:  if we create a second  cloud on the same  namespaces (kubernetes)  that works, but no explanation why first cloud is not operate anymore{color}           		New: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround:  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore{color}
          fb made changes -
          Priority Original: Minor [ 4 ] New: Blocker [ 1 ]
          fb made changes -
          Description Original: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround:  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore{color}           		New: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround (in test):  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore{color}
          fb made changes -
          Description Original: {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround (in test):  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore{color}           		New: {color:#333333}Our jenkins version is  2.346.3{color}

           

          {color:#333333}-Still waiting to schedule task...    -->jobs Hangs{color}

          {color:#333333}-Workaround (in test):  if we create a second  cloud on the same  namespaces (kubernetes) Pod is created, but no explanation why first cloud is not operate anymore{color}

           

           
          Peter Niederlag made changes -
          Link New: This issue is duplicated by JENKINS-71796 [ JENKINS-71796 ]
          Mark Waite made changes -
          Comment [ One workaround mentioned is creating a second cloud on the same namespace in Kubernetes, which results in pods being created. However, there's no explanation provided for why the first cloud is not operating anymore.

          This issue appears to be critical (labeled as a blocker priority) and unresolved, affecting the functioning of Jenkins in Kubernetes environments. It's linked to another similar issue (JENKINS-71796), indicating that this may be a recurring problem for users.

          Given the critical nature of the problem and its impact on Jenkins functionality, it's important for the Jenkins community to address and resolve this issue promptly to ensure smooth operations for users relying on Jenkins in Kubernetes environments.
          [https://www.ny-stateofhealth.com|https://www.ny-stateofhealth.com/] ]
          Mark Waite made changes -
          Comment [ Hello,

          If your Jenkins jobs are hanging with the message “Still waiting to schedule task…” and creating a second cloud seems to work as a workaround, consider these steps:

          Check Jenkins Logs: Look for errors that could explain the issue.
          Review Kubernetes Resources: Ensure there are enough resources for Jenkins agents.
          Verify Network Policies: Confirm no network policies are blocking Jenkins-pod communication.
          Service Account Permissions: The Jenkins agent’s service account should have proper permissions.
          Update Jenkins and Plugins: Make sure you’re using the latest versions.
          [SpotifyPie Chart|https://www.spotify-pie.com]

          Hope this info will help you.
          Best Regard,
          geraldine198 ]

            Unassigned Unassigned
            fb fb
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: