Closed jmencak closed 8 months ago
@jmencak: This pull request explicitly references no jira issue.
Tested with the latest TuneD 2.22.1 which will be the next FDP release.
/retest
Infra issues /retest
/retest /cc @liqcui
There's no way this can break ci/prow/e2e-gcp-pao
/retest
/override ci/prow/e2e-gcp-pao
/retest
@jmencak: Overrode contexts on behalf of jmencak: ci/prow/e2e-gcp-pao
/lgtm /hold
holding to let other reviewers chime in, feel free to remove anytime
/hold cancel
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jmencak, MarSik
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 03f95571187560f7ce4b2175d00bbb3e1ae7bffd and 2 for PR HEAD 9e8d3418671c19277601a0a4b7f1a89621f2c22b in total
/override ci/prow/e2e-gcp-pao-updating-profile /retest
@jmencak: Overrode contexts on behalf of jmencak: ci/prow/e2e-gcp-pao-updating-profile
@jmencak: all tests passed!
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202403081048.p0.gf9c912b.assembly.stream.el9 for distgit cluster-node-tuning-operator. All builds following this will include this PR.
Starting with PR858, we can no longer use a random
RELEASE_VERSION
to trigger daemonset/operand updates. In the context of testing upstream TuneD this is causes an issue. Not changingRELEASE_VERSION
at all is a simple fix, because we are also adjustingCLUSTER_NODE_TUNED_IMAGE
and that will cause a daemonset/operand update.