Skip to content

OCPBUGS-109666: fix the name of the Helm release in EAP 8.1 quickstart - #1208

Open
jmesnil wants to merge 1 commit into
openshift:mainfrom
jmesnil:OCPBUGS-109666_eap81_helm_release_name
Open

OCPBUGS-109666: fix the name of the Helm release in EAP 8.1 quickstart#1208
jmesnil wants to merge 1 commit into
openshift:mainfrom
jmesnil:OCPBUGS-109666_eap81_helm_release_name

Conversation

@jmesnil

@jmesnil jmesnil commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

By default, the name of the Helm release is redhat-eap81 while the quickstart is referring to eap81. Fix all occurences in the quickstart for the names of the resources to be consistent.

JIRA: https://redhat.atlassian.net/browse/OCPBUGS-109666

By default, the name of the Helm release is `redhat-eap81` while the quickstart
is referring to `eap81`. Fix all occurences in the quickstart for the names
of the resources to be consistent.

JIRA: https://redhat.atlassian.net/browse/OCPBUGS-109666

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 14, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@jmesnil: This pull request references Jira Issue OCPBUGS-109666, 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 (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

By default, the name of the Helm release is redhat-eap81 while the quickstart is referring to eap81. Fix all occurences in the quickstart for the names of the resources to be consistent.

JIRA: https://redhat.atlassian.net/browse/OCPBUGS-109666

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
openshift-ci Bot requested review from TheRealJon and jhadvig August 14, 2026 08:20
@openshift-ci

openshift-ci Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmesnil
Once this PR has been reviewed and has the lgtm label, please assign christoph-jerolimov for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@openshift-ci

openshift-ci Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

@jmesnil: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

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

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants