Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #22392

/assign maxwelldb

Adolfo Duarte and others added 2 commits September 18, 2020 13:15
Misconfiguratoin of DNS and netwrok control access will cause the
addition of rhel compute node to fail.

DNS configuration and network control access are under the control of the user
and their state can not be predicted.
In order to prevent the failures, it falls on the users shoulders to verify
that DNS and control access are correctly configured to allow the needed access.
The access maybe easily tested prior to installation.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Could not make automatic cherrypick of Bugzilla bug 1804083 for this PR as the target_release is not set for this branch in the bugzilla plugin config. Running refresh:
/bugzilla refresh

Details

In response to this:

[enterprise-4.6] Bug 1804083: Explains requirements for deploying RHEL compute node

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 bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Sep 18, 2020
@openshift-ci-robot
Copy link

@openshift-ci-robot: This pull request references Bugzilla bug 1804083, which is invalid:

  • expected Bugzilla bug 1804083 to depend on a bug in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Bugzilla bug 1804083 for this PR as the target_release is not set for this branch in the bugzilla plugin config. Running refresh:
/bugzilla refresh

In response to this:

[enterprise-4.6] Bug 1804083: Explains requirements for deploying RHEL compute node

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.

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 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 18, 2020
@maxwelldb maxwelldb merged commit 3e695f0 into openshift:enterprise-4.6 Sep 18, 2020
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

Bugzilla bug 1804083 has not been moved to the MODIFIED state.

Details

In response to this:

[enterprise-4.6] Bug 1804083: Explains requirements for deploying RHEL compute node

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.

@yuvalk yuvalk mentioned this pull request Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants