-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just testing the new ksctl register member command #1032
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfrancisc 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:
Approvers can indicate their approval by writing |
@mfrancisc it's related - se my comment in the other PR: kubesaw/ksctl#53 (comment) |
Thanks I was looking into it locally, I've inverted the SAs apparently 🤦♂️ |
/retest updated the ksctl PR |
hmmm seems like it picked up master branch instead of my for now : https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/codeready-toolchain_toolchain-e2e/1032/pull-ci-codeready-toolchain-toolchain-e2e-master-e2e/1823719902742056960/artifacts/e2e/test/build-log.txt |
yup, the pairing was broken - I didn't realize that the if statement is evaluated at the beginning of the makefile target. Here is the fix #1034 |
/retest |
🤦 |
I see later it installs from my branch , but it doesn't run the
```
detected branch registermember
# check if a branch with the same ref exists in the user's fork of ksctl repo
branches of https://github.com/mfrancisc/ksctl - checking if there is a branch registermember we could pair with.
curl https://github.com/mfrancisc/ksctl.git/info/refs?service=git-upload-pack --output -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 define temp dirdelete to have clear environmentrm -rf /tmp/ksctl clonegit clone --depth=1 https://github.com/kubesaw/ksctl.git /tmp/ksctl add the user's fork as remote repogit --git-dir=/tmp/ksctl/.git --work-tree=/tmp/ksctl remote add external https://github.com/mfrancisc/ksctl.git fetch the branchgit --git-dir=/tmp/ksctl/.git --work-tree=/tmp/ksctl fetch external refs/heads/registermember
merge the branch with mastergit --git-dir=/tmp/ksctl/.git --work-tree=/tmp/ksctl merge --allow-unrelated-histories --no-commit FETCH_HEAD
|
The thing is that the migration suite installs the latest operators first and then it registers the member clusters. I didn't realize that the registering member clusters still happens in the context of the latest install and that the env var is still set for that command. |
the pairing that you see is for a later execution when ksctl is used to generate the appstudio NSTemplateTier files |
Quality Gate passedIssues Measures |
@MatousJobanek the pairing worked fine now and the tests are passing apparently with the new command : https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/codeready-toolchain_toolchain-e2e/1032/pull-ci-codeready-toolchain-toolchain-e2e-master-e2e/1828051122380607488/artifacts/e2e/test/build-log.txt |
closing as not needed anymore, the new register-member command was merged. |
Paired with: kubesaw/ksctl#53
Will close once verified.