fix cluster up extended test#17029
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
@csrwng i'm not sure why this wasn't using --version=latest before but i think it should be for the bulk of the tests, no? Adding another test that runs w/o --version=latest makes sense to me, but we can't do that right now because current master actually can't bring up v3.7-alpha1 anyway. so that's a follow up. |
|
/test extended_clusterup |
49e4712 to
e2b3d21
Compare
ffc3ff2 to
00bf958
Compare
|
/test extended_clusterup |
00bf958 to
547c2c7
Compare
|
/test extended_clusterup |
547c2c7 to
406a664
Compare
|
/test extended_clusterup |
406a664 to
9605ac2
Compare
|
/test extended_clusterup |
9605ac2 to
8468209
Compare
|
/test extended_clusterup |
8468209 to
49e74f2
Compare
|
/test extended_clusterup |
49e74f2 to
1ceb3dc
Compare
|
/test extended_clusterup |
|
@csrwng bump, this now passes the new cluster up extended test job i created (which just runs the clusterup.sh bucket) |
|
@bparees I think that when we use --version="latest" infrastructure images are created with a pull policy of 'always'. If we want to test the local images, we may need to use the specific tag (git hash) that we used to build them. |
ok. is there an easy way to grab that so i can just pass it to the script? |
|
@stevekuznetsov ? ^^ |
? |
|
In our jobs we gather it like so: And use it like so: |
1ceb3dc to
5f75825
Compare
|
/test extended_clusterup |
5f75825 to
e01bb9b
Compare
|
/test extended_clusterup |
|
thanks @stevekuznetsov |
|
(and updated the jenkins job to set ORIGIN_COMMIT) |
|
(well, trying to update the job. ci.jenkins looks dead) |
|
the updated job definition is here: |
|
@bparees lgtm on passing test |
|
/test extended_clusterup |
1 similar comment
|
/test extended_clusterup |
|
passed cluster up test here: |
|
/retest |
|
/cherrypick stage |
|
@Kargakis: @Kargakis once the present PR merges, I will cherry-pick it on top of stage in a new PR and assign it to you. DetailsIn response to this:
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. |
|
Automatic merge from submit-queue. |
|
I don't see the cherry-pick :( @Kargakis |
No description provided.