Closed kashifest closed 5 months ago
/test metal3-dev-env-integration-test-ubuntu-release-1.5 /test metal3-centos-e2e-integration-test-release-1-5
/test metal3-dev-env-integration-test-ubuntu-release-1-5
/test metal3-dev-env-integration-test-ubuntu-release-1.5
@kashifest: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test markdownlint
/test metal3-centos-e2e-integration-test-release-1-7
/test metal3-dev-env-integration-test-ubuntu-main
/test shellcheck
The following commands are available to trigger optional jobs:
/test metal3-centos-e2e-basic-test-main
/test metal3-centos-e2e-basic-test-release-1-6
/test metal3-centos-e2e-basic-test-release-1-7
/test metal3-centos-e2e-feature-test-main
/test metal3-centos-e2e-feature-test-release-1-5
/test metal3-centos-e2e-feature-test-release-1-6
/test metal3-centos-e2e-feature-test-release-1-7
/test metal3-centos-e2e-integration-test-main
/test metal3-centos-e2e-integration-test-release-1-5
/test metal3-centos-e2e-integration-test-release-1-6
/test metal3-dev-env-integration-test-centos-main
/test metal3-dev-env-integration-test-centos-release-1-5
/test metal3-dev-env-integration-test-centos-release-1-6
/test metal3-dev-env-integration-test-centos-release-1-7
/test metal3-dev-env-integration-test-ubuntu-release-1-5
/test metal3-dev-env-integration-test-ubuntu-release-1-6
/test metal3-dev-env-integration-test-ubuntu-release-1-7
/test metal3-e2e-1-26-1-27-upgrade-test-main
/test metal3-e2e-1-26-1-27-upgrade-test-release-1-5
/test metal3-e2e-1-26-1-27-upgrade-test-release-1-6
/test metal3-e2e-1-26-1-27-upgrade-test-release-1-7
/test metal3-e2e-1-27-1-28-upgrade-test-main
/test metal3-e2e-1-27-1-28-upgrade-test-release-1-5
/test metal3-e2e-1-27-1-28-upgrade-test-release-1-6
/test metal3-e2e-1-27-1-28-upgrade-test-release-1-7
/test metal3-e2e-1-28-1-29-upgrade-test-main
/test metal3-e2e-1-28-1-29-upgrade-test-release-1-5
/test metal3-e2e-1-28-1-29-upgrade-test-release-1-6
/test metal3-e2e-1-28-1-29-upgrade-test-release-1-7
/test metal3-e2e-clusterctl-upgrade-test-main
/test metal3-e2e-clusterctl-upgrade-test-release-1-5
/test metal3-e2e-clusterctl-upgrade-test-release-1-6
/test metal3-e2e-clusterctl-upgrade-test-release-1-7
/test metal3-ubuntu-e2e-basic-test-main
/test metal3-ubuntu-e2e-basic-test-release-1-6
/test metal3-ubuntu-e2e-basic-test-release-1-7
/test metal3-ubuntu-e2e-feature-test-main
/test metal3-ubuntu-e2e-feature-test-release-1-5
/test metal3-ubuntu-e2e-feature-test-release-1-6
/test metal3-ubuntu-e2e-feature-test-release-1-7
/test metal3-ubuntu-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-release-1-5
/test metal3-ubuntu-e2e-integration-test-release-1-6
/test metal3-ubuntu-e2e-integration-test-release-1-7
/test metal3-dev-env-integration-test-ubuntu-release-1-5
/test metal3-dev-env-integration-test-ubuntu-release-1-5
/test metal3-centos-e2e-integration-test-release-1-5
/test metal3-e2e-clusterctl-upgrade-test-release-1-5
/test metal3-dev-env-integration-test-ubuntu-release-1-5 /test metal3-dev-env-integration-test-ubuntu-main /test metal3-centos-e2e-integration-test-release-1-7
Maybe add a comment here why its like this, but otherwise seem that this is passing and fixing all 1.5 jobs.
I have added in the description, do you mean thats not enough ?
Maybe add a comment here why its like this, but otherwise seem that this is passing and fixing all 1.5 jobs.
I have added in the description, do you mean thats not enough ?
That was supposed to be a comment on the code change, ie. include comment in the ansible file.
That was supposed to be a comment on the code change, ie. include comment in the ansible file.
Ah, no I guess its fine, commit message has that as well, I dont want to hamper the running tests now, once the test pass, I can push a change and then override the tests if you want, IMO its not needed.
@adilGhaffarDev is the failure in the clusterctl test now related to what you are fixing in ironic upgrade ?
STEP: Waiting for ironic update to rollout @ 06/14/24 08:49:50.134
12:00:02 [FAILED] in [It] - /home/metal3ci/metal3/test/e2e/upgrade_ironic.go:61 @ 06/14/24 08:59:50.147
12:00:02 < Exit [It] Should create a management cluster and then upgrade all the providers @ 06/14/24 08:59:50.149 (40m31.701s)
@adilGhaffarDev is the failure in the clusterctl test now related to what you are fixing in ironic upgrade ?
this is a known issue clusterctl upgrade tests on the 1.5 branch, fix is in progress.
/override metal3-e2e-clusterctl-upgrade-test-release-1-5
@adilGhaffarDev confirmed that the error we see now is unrelated , known issue and being worked upon separately. However, since the test reached this far shows that the fix is working.
@kashifest: Overrode contexts on behalf of kashifest: metal3-e2e-clusterctl-upgrade-test-release-1-5
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: smoshiur1237
The full list of commands accepted by this bot can be found here.
The pull request process is described here
I have also verified the go versions in the different branch tests, if you simple search for go env
in the jenkins log you will find that for release-1.5 branch it is go1.21.11
whereas for other branches it is go1.22.4
as expected
This PR installs go1.21.x for release-1.5 branch. For other branches it should install 1.22.x. This is for the fact that CAPM3 release-1.5 branch wont survive go 1.22 because of version incompatability with controller runtime. Signed-off-by: Kashif Khan kashif.khan@est.tech