Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1821407: Clarify alert for supported operator's install mode #4948

Merged
merged 1 commit into from Apr 9, 2020

Conversation

jhadvig
Copy link
Member

@jhadvig jhadvig commented Apr 7, 2020

@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 Apr 7, 2020
@openshift-ci-robot
Copy link
Contributor

@jhadvig: This pull request references Bugzilla bug 1821407, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1821407: Remove 'openshift-operators' namespace from single names…

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.

@jhadvig jhadvig changed the title Bug 1821407: Remove 'openshift-operators' namespace from single names… Bug 1821407: Remove 'openshift-operators' namespace from single namespace install mode dropdown Apr 7, 2020
@openshift-ci-robot
Copy link
Contributor

@jhadvig: This pull request references Bugzilla bug 1821407, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1821407: Remove 'openshift-operators' namespace from single namespace install mode dropdown

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.

@jhadvig
Copy link
Member Author

jhadvig commented Apr 7, 2020

/cherrypick release-4.4

@openshift-cherrypick-robot

@jhadvig: once the present PR merges, I will cherry-pick it on top of release-4.4 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.4

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
Copy link
Contributor

@jhadvig: This pull request references Bugzilla bug 1821407, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1821407: Remove 'openshift-operators' namespace from single namespace install mode dropdown

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 7, 2020
@spadgett
Copy link
Member

spadgett commented Apr 7, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2020
@jhadvig jhadvig changed the title Bug 1821407: Remove 'openshift-operators' namespace from single namespace install mode dropdown Bug 1821407: Clarify alert for supported operator's install mode Apr 8, 2020
@jhadvig
Copy link
Member Author

jhadvig commented Apr 8, 2020

@spadgett updated the alert's wording:

Screenshot 2020-04-08 at 10 21 24

@jhadvig
Copy link
Member Author

jhadvig commented Apr 9, 2020

@spadgett comment addressed. Thanks !

Screenshot 2020-04-09 at 12 02 21

Comment on lines 303 to 309
{`The operator group in the '${selectedTargetNamespace}' namespace does not support the
${
selectedInstallMode === InstallModeType.InstallModeTypeAllNamespaces
? 'global'
: 'single namespace'
}
installation mode.`}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No reason for this to be a string, it can be markup.

Suggested change
{`The operator group in the '${selectedTargetNamespace}' namespace does not support the
${
selectedInstallMode === InstallModeType.InstallModeTypeAllNamespaces
? 'global'
: 'single namespace'
}
installation mode.`}
The operator group in the {selectedTargetNamespace} namespace does not support the
{
selectedInstallMode === InstallModeType.InstallModeTypeAllNamespaces
? 'global'
: 'single namespace'
}
installation mode.

@jhadvig
Copy link
Member Author

jhadvig commented Apr 9, 2020

@spadgett comment addressed

Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@spadgett
Copy link
Member

spadgett commented Apr 9, 2020

/retest

@spadgett
Copy link
Member

spadgett commented Apr 9, 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 Apr 9, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2020
Copy link
Contributor

@benjaminapetersen benjaminapetersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benjaminapetersen, jhadvig, spadgett

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

The pull request process is described here

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-merge-robot openshift-merge-robot merged commit 9ed85ae into openshift:master Apr 9, 2020
@openshift-ci-robot
Copy link
Contributor

@jhadvig: All pull requests linked via external trackers have merged: openshift/console#4948. Bugzilla bug 1821407 has been moved to the MODIFIED state.

In response to this:

Bug 1821407: Clarify alert for supported operator's install mode

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-cherrypick-robot

@jhadvig: new pull request created: #4997

In response to this:

/cherrypick release-4.4

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.

@spadgett spadgett added this to the v4.5 milestone Apr 14, 2020
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/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. component/olm Related to OLM lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants