Bug 1847421 - Jenkins e2e failing because of unmitigated update to jenkins-client-plugin examples
Summary: Jenkins e2e failing because of unmitigated update to jenkins-client-plugin ex...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Jenkins
Version: 4.2.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Akram Ben Aissi
QA Contact: Jitendar Singh
URL:
Whiteboard:
Depends On:
Blocks: 1848921
TreeView+ depends on / blocked
 
Reported: 2020-06-16 11:04 UTC by Vibhav Bobade
Modified: 2021-05-06 18:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1848921 (view as bug list)
Environment:
Last Closed: 2021-05-06 18:54:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:08:00 UTC

Description Vibhav Bobade 2020-06-16 11:04:13 UTC
Description of problem:

Due to https://github.com/openshift/jenkins-client-plugin/commit/4f11936fc995ced1b080d8f5261b0482d26ac5e2 the jenkins-second-deployment isn't being created. And the e2e tests for these are failing as it looks for the jenkins-second-deployment to dump the logs. 

For example, https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/pr-logs/pull/openshift_jenkins/1075/pull-ci-openshift-jenkins-release-4.3-e2e-aws-jenkins/31 fails when it is not able to find jenkins-second-deployment as it is not being created due to https://github.com/openshift/jenkins-client-plugin/commit/4f11936fc995ced1b080d8f5261b0482d26ac5e2 

we get the error 

fail [github.com/openshift/origin/test/extended/builds/pipeline_origin_bld.go:252]: Unexpected error:
    <*util.ExitError | 0xc001acc480>: {
        Cmd: "oc --namespace=e2e-test-jenkins-pipeline-z5n6w --config=/tmp/configfile520612857 delete dc jenkins-second-deployment",
        StdErr: "Error from server (NotFound): deploymentconfigs.apps.openshift.io \"jenkins-second-deployment\" not found",
        ExitError: {
            ProcessState: {
                pid: 2110,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 243942},
                    Stime: {Sec: 0, Usec: 140137},
                    Maxrss: 85748,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 12690,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 0,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 771,
                    Nivcsw: 8,
                },
            },
            Stderr: nil,
        },
    }
    exit status 1

Expected Result:
Test should pass

Comment 2 Stephen Cuppett 2020-06-18 14:42:49 UTC
Setting target release to the active development branch (4.6.0). For fixes, if any, requested/required on previous versions, cloned BZs targeting those release z-streams will be created.

Comment 3 Stephen Cuppett 2020-06-19 12:36:56 UTC
Setting target release to current development version (4.6) for investigation. Where fixes (if any) are required/requested for prior versions, cloned BZs will be created when appropriate.

Comment 4 Akram Ben Aissi 2020-06-23 18:10:04 UTC
to QA: No specific verifier for this, just that the e2e tests are now working.
This is development environment specific

Comment 7 Jitendar Singh 2020-06-25 07:42:40 UTC
VERIFIED

Comment 9 errata-xmlrpc 2020-10-27 16:07:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196


Note You need to log in before you can comment on or make changes to this bug.