Skip to content
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

ci/e2e: variabilize number of nodes #484

Merged
merged 8 commits into from
Nov 8, 2022
Merged

Conversation

ldevulder
Copy link
Contributor

@ldevulder ldevulder commented Nov 2, 2022

This allow to quickly increase the number of nodes to add in the provisioned cluster. Part of #423.

Verification run: https://github.com/rancher/elemental/actions/runs/3416821900.
NOTE: K3s test failed because of a download issue with opensuse.org, nothing related to this PR, and RKE2 is green with 6 nodes.

@ldevulder ldevulder self-assigned this Nov 2, 2022
@ldevulder ldevulder marked this pull request as draft November 2, 2022 13:48
@ldevulder ldevulder force-pushed the e2e-variabilize-node-number branch 7 times, most recently from f5b85fc to 9303c41 Compare November 3, 2022 17:08
@ldevulder ldevulder force-pushed the e2e-variabilize-node-number branch 2 times, most recently from d170432 to b5f5143 Compare November 7, 2022 22:13
@ldevulder ldevulder mentioned this pull request Nov 8, 2022
8 tasks
@ldevulder ldevulder marked this pull request as ready for review November 8, 2022 07:35
Copy link
Contributor

@juadk juadk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but it could be better if we can get a summarize at the end of test about how many nodes we deploy in the test. Without the summarize, we can guess it by browsing the log but the log is very big with the boot part and so on.

@ldevulder ldevulder enabled auto-merge (rebase) November 8, 2022 09:53
@Itxaka
Copy link
Contributor

Itxaka commented Nov 8, 2022

FYI you can change the name of the job to use the number of nodes on it, so its visible on a glance at the job, see https://github.com/rancher/elemental-operator/blob/main/.github/workflows/e2e.yaml#L74 for example

Or just push the number of nodes to the job summary so its visible in the job summary: https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/

@ldevulder ldevulder force-pushed the e2e-variabilize-node-number branch 3 times, most recently from ae7a0f3 to 2f5d6cb Compare November 8, 2022 13:33
This allow to quickly increase the number of nodes to add in the
provisioned cluster.

Signed-off-by: Loic Devulder <ldevulder@suse.com>
This is to workaround this error:
```
Unexpected type of value '10', expected type: Number.
```

Looks like a GHA bug...

Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
Signed-off-by: Loic Devulder <ldevulder@suse.com>
@ldevulder ldevulder enabled auto-merge (rebase) November 8, 2022 13:35
@ldevulder ldevulder merged commit b566a31 into main Nov 8, 2022
@ldevulder ldevulder deleted the e2e-variabilize-node-number branch November 8, 2022 14:02
@ldevulder ldevulder mentioned this pull request Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants