8000 Starting builds fail after migration to Deployment (jenkins-agent-base) · Issue #1165 · coreos/fedora-coreos-pipeline · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Starting builds fail after migration to Deployment (jenkins-agent-base) #1165
Closed
@c4rt0

Description

@c4rt0

While testing changes on jenkins-fcos-devel I came across an issue when spinning up the builds after the Deployment successfully scales up.
With the Deployment in place as per the PR the recent change in https://github.com/coreos/fedora-coreos-pipeline/pull/1151/files#diff-ec27debddfd43cff8cffc23f46bcd7f38ec21c7cf26fb79e55588724b1f76d74R103 needs modification to the previous state.

With that change the builds init state completes successfully.

With the current problematic configuration in place i.e.:

-Dorg.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStepExecution.defaultImage=jenkins-agent-base:latest

the following error is observed:

14:41:08  	Container [jnlp] waiting [ErrImagePull] initializing source docker://jenkins-agent-base:latest: reading manifest latest in docker.io/library/jenkins-agent-base: requested access to the resource is denied
14:41:08  	Pod [Pending][ContainersNotReady] containers with unready status: [jnlp]
14:41:21  ERROR: Unable to pull container image "jenkins-agent-base:latest". Check if image tag name is spelled correctly.

This consistently results in the failed init stage of each build.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0