Bug 2077289: set necessary JVM args to allow jenkins JVM to come up on a FIPS node

[gabemontero]

manual pick after bot failed at #1425 (comment)

/assign @coreydaley

[openshift-ci]

@gabemontero: This pull request references Bugzilla bug 2077289, which is invalid:

• expected dependent Bugzilla bug 2075135 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

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.

In response to this:

Bug 2077289: set necessary JVM args to allow jenkins JVM to come up on a FIPS 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]

@gabemontero: 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.

[gabemontero]

bump @coreydaley

you OK with tagging with lgtm and backport risk even though we are waiting on the 4.10 bz to get verified so this 4.9 PR can get the valid bz label?

[coreydaley]

/label backport-risk-assessed
/lgtm

[coreydaley]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: coreydaley, gabemontero

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:

• OWNERS [gabemontero]

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

[openshift-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci]

@openshift-bot: This pull request references Bugzilla bug 2077289, which is invalid:

• expected dependent Bugzilla bug 2075135 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

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.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

[gabemontero]

/bugzilla refresh

[openshift-ci]

@gabemontero: This pull request references Bugzilla bug 2077289, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.9.z) matches configured target release for branch (4.9.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 2075135 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2075135 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
• bug has dependents

Requesting review from QA contact:
/cc @jitendar-singh

In response to this:

/bugzilla 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.

[gabemontero]

/assign @jitendar-singh
/assign @prietyc123

for cherry pick approve

thanks

[prietyc123]

/label cherry-pick-approved

[openshift-ci]

@gabemontero: All pull requests linked via external trackers have merged:

• openshift/jenkins#1433

Bugzilla bug 2077289 has been moved to the MODIFIED state.

In response to this:

Bug 2077289: set necessary JVM args to allow jenkins JVM to come up on a FIPS 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.

[gabemontero]

/cherrypick release-4.8

[openshift-cherrypick-robot]

@gabemontero: #1433 failed to apply on top of branch "release-4.8":

Applying: set necessary JVM args to allow jenkins JVM to come up on a FIPS node
Using index info to reconstruct a base tree...
M	2/contrib/s2i/run
M	README.md
M	slave-base/contrib/bin/run-jnlp-client
Falling back to patching base and 3-way merge...
Auto-merging slave-base/contrib/bin/run-jnlp-client
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
Auto-merging 2/contrib/s2i/run
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 set necessary JVM args to allow jenkins JVM to come up on a FIPS node
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.8

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.