Skip to content

Bug 1802297: handle ingress certificate signed by custom ca#1087

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.2from
akram:4.2-bz-1802297
Jun 26, 2020
Merged

Bug 1802297: handle ingress certificate signed by custom ca#1087
openshift-merge-robot merged 1 commit intoopenshift:release-4.2from
akram:4.2-bz-1802297

Conversation

@akram
Copy link
Contributor

@akram akram commented Jun 19, 2020

No description provided.

@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Jun 19, 2020
@openshift-ci-robot
Copy link
Contributor

@akram: This pull request references Bugzilla bug 1802297, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

8 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.2.z) matches configured target release for branch (4.2.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1782819 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent bug Bugzilla bug 1809924 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1782819 targets the "4.3.0" release, which is one of the valid target releases: 4.3.0, 4.3.z
  • dependent Bugzilla bug 1809924 targets the "4.3.z" release, which is one of the valid target releases: 4.3.0, 4.3.z
  • bug has dependents
Details

In response to this:

Bug 1802297: handle ingress certificate signed by custom ca

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jun 19, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 19, 2020
@akram akram force-pushed the 4.2-bz-1802297 branch 4 times, most recently from fc9dc31 to 077d905 Compare June 19, 2020 01:31
@akram
Copy link
Contributor Author

akram commented Jun 19, 2020

/test e2e-aws

@akram
Copy link
Contributor Author

akram commented Jun 19, 2020

I am investigating the e2e-aws-jenkins and still don't understanding how it was working in the past. Seems that oc run --image=docker.io/openshift/origin-jenkins doest not work well, but that's probably not the issue.
2 series of tests are failing, still looking at if for 4.2 . The stock image in 4.2 have also issues on startup.

This e2e-aws is really flaking me out
/test e2e-aws

@akram
Copy link
Contributor Author

akram commented Jun 19, 2020

The upstream build was causing issue because the base image quay.io/openshift/origin-cli:latest suddenly changed the oc run command that creates pods instead of deployments.
Now, we are sticking to : quay.io/openshift/origin-cli:4.2

@jkhelil
Copy link
Contributor

jkhelil commented Jun 19, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 19, 2020
@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 19, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

11 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2020
@akram
Copy link
Contributor Author

akram commented Jun 25, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 25, 2020
@jkhelil
Copy link
Contributor

jkhelil commented Jun 25, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@shawn-hurley shawn-hurley added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 25, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@akram
Copy link
Contributor Author

akram commented Jun 25, 2020

/test e2e-aws-jenkins

@akram
Copy link
Contributor Author

akram commented Jun 25, 2020

/test e2e-aws-jenkins

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2020
@sbose78
Copy link

sbose78 commented Jun 25, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akram, jkhelil, sbose78

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@akram
Copy link
Contributor Author

akram commented Jun 26, 2020

anoter flake:

error: unable to connect to image repository default-route-openshift-image-registry.apps.build01.ci.devcluster.openshift.com/ci-op-jrq4d35m/stable@sha256:cd035ba7a19a77a82df2829e86a14e51b075c6d37f1d25536c1d39bd20a0c996: endpoint "https://default-route-openshift-image-registry.apps.build01.ci.devcluster.openshift.com" does not support v2 API

/test images

@akram
Copy link
Contributor Author

akram commented Jun 26, 2020

/test images

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit ac84ad3 into openshift:release-4.2 Jun 26, 2020
@openshift-ci-robot
Copy link
Contributor

@akram: All pull requests linked via external trackers have merged: openshift/jenkins#1087, openshift/cluster-kube-controller-manager-operator#350. Bugzilla bug 1802297 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1802297: handle ingress certificate signed by custom ca

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

Comments