console
console copied to clipboard
openshift
OCPBUGS-1829: use service port name instead targetPort in the Pipeline Event listener route
Fixes: https://issues.redhat.com/browse/OCPBUGS-1829
Analysis / Root cause: On upgrading to 1.6.2 from 1.5.2 curl command is throwing error The application is currently not serving requests at this endpoint. It may not have been started or is still starting. It is happening because in UI we are using service port TargetPort to create the Pipeline Event listener route instead of the service port name.
Solution Description: use service port name instead targetPort in the Pipeline Event listener route
@vikram-raj: This pull request references Jira Issue OCPBUGS-1829, which is invalid:
- expected the bug to target the "4.12.0" version, but no target version was set
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Fixes: https://issues.redhat.com/browse/OCPBUGS-1829
Analysis / Root cause: On upgrading to 1.6.2 from 1.5.2 curl command is throwing error
The application is currently not serving requests at this endpoint. It may not have been started or is still starting. It is happening because in UI we are using service port TargetPort to create the Pipeline Event listener route instead of the service port name.Solution Description: use service port name instead targetPort in the Pipeline Event listener route
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vikram-raj
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/pipelines-plugin/OWNERS~~ [vikram-raj]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@vikram-raj: This pull request references Jira Issue OCPBUGS-1829, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.12.0) matches configured target version for branch (4.12.0)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
Requesting review from QA contact: /cc @sanketpathak
In response to this:
/jira refresh
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.
@vikram-raj: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp-console | 3150a087b4fdff565d3f74cebae45e1888935dd5 | link | true | /test e2e-gcp-console |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@vikram-raj: all tests passed!
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: karthikjeeyar, vikram-raj
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/pipelines-plugin/OWNERS~~ [karthikjeeyar,vikram-raj]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@vikram-raj: Jira Issue OCPBUGS-1829: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-1829 has been moved to the MODIFIED state.
In response to this:
Fixes: https://issues.redhat.com/browse/OCPBUGS-1829
Analysis / Root cause: On upgrading to 1.6.2 from 1.5.2 curl command is throwing error
The application is currently not serving requests at this endpoint. It may not have been started or is still starting. It is happening because in UI we are using service port TargetPort to create the Pipeline Event listener route instead of the service port name.Solution Description: use service port name instead targetPort in the Pipeline Event listener route
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.
@vikram-raj: new pull request created: #12870
In response to this:
/cherry-pick release-4.13
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.
