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

Ibmcloud e2e #636

Merged
merged 4 commits into from May 11, 2022
Merged

Ibmcloud e2e #636

merged 4 commits into from May 11, 2022

Conversation

Mathieu-Ferraton
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 13, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 13, 2022

Hi @Mathieu-Ferraton. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 13, 2022
@kaovilai
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 14, 2022
@Mathieu-Ferraton Mathieu-Ferraton marked this pull request as ready for review April 29, 2022 10:17
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 29, 2022
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 3, 2022
improve test filtering and add labels to aws specific test cases
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 3, 2022
@Mathieu-Ferraton
Copy link
Contributor Author

/retest

1 similar comment
@kaovilai
Copy link
Member

kaovilai commented May 4, 2022

/retest

Makefile Outdated Show resolved Hide resolved
@@ -155,7 +155,7 @@ items:
spec:
containers:
- name: todolist
image: quay.io/rhn_engineering_whayutin/todolist-mariadb-go:latest
image: quay.io/mferrato/todolist-mariadb-go:v1
Copy link
Member

Choose a reason for hiding this comment

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

What's happening here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Wesley's image is amd64 only. I made a PR to the mig-demo-app repo konveyor/mig-demo-apps#74 to add the code enabling multiarch builds for the mariadb-based app. We discused that with @weshayutin as a temporary solution until we have a place to store the multiarch manifest. But I'd rather store it somewhere else, if you know of a better place.

Copy link
Contributor

Choose a reason for hiding this comment

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

Correct.. I've just opened an issue on OADP to better describe what needs to be done here and why. #666

Pretty crazy re: the issue #
7c0696e0-5c7b-48dc-a500-69be86939db9 e6557d1ec7732d827674187696a95a86

Copy link
Member

Choose a reason for hiding this comment

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

So konveyor quay org would be one

@@ -381,7 +381,7 @@ var _ = Describe("Configuration testing for DPA Custom Resource", func() {
}

awsTests := []TableEntry{
Entry("AWS Without Region No S3ForcePathStyle with BackupImages false should succeed", InstallCase{
Entry("AWS Without Region No S3ForcePathStyle with BackupImages false should succeed", Label("aws"), InstallCase{
Copy link
Member

Choose a reason for hiding this comment

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

I would rather see this label added in a for loop instead since that's the whole point of a separate awsTests declaration. But I am aware this is not possible right now.
onsi/ginkgo#974 might allow this in the future.

Mathieu-Ferraton and others added 2 commits May 4, 2022 09:23
Co-authored-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
Co-authored-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
@Mathieu-Ferraton
Copy link
Contributor Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented May 4, 2022

@Mathieu-Ferraton: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@weshayutin
Copy link
Contributor

@hhpatel14 @deepakraj1997 please review when you have a moment :)

TEST_FILTER := $(shell echo '! aws && ! gcp && ! azure' | sed -r "s/[&]* [!] $(CLUSTER_TYPE)|[!] $(CLUSTER_TYPE) [&]*//")
TEST_FILTER := ($(shell echo '! aws && ! gcp && ! azure && ! ibmcloud' | \
sed -r "s/[&]* [!] $(CLUSTER_TYPE)|[!] $(CLUSTER_TYPE) [&]*//")) || $(CLUSTER_TYPE)
#TEST_FILTER := $(shell echo '! aws && ! gcp && ! azure' | sed -r "s/[&]* [!] $(CLUSTER_TYPE)|[!] $(CLUSTER_TYPE) [&]*//")
Copy link
Contributor

Choose a reason for hiding this comment

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

nit.. probably can remove this :)

Copy link
Contributor

Choose a reason for hiding this comment

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

we can remove the commented line, but i think we can keep the test_filter as we can use it to run cloud specific tests in future.

"config": {
"profile": "$BSL_AWS_PROFILE",
"region": "$BSL_REGION",
"s3ForcePathStyle": "true",
Copy link
Contributor

Choose a reason for hiding this comment

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

@Mathieu-Ferraton @kaovilai Wont this set s3ForcePathStyle for all the SPECs that are running ? I think we explicitly set these in some tests and remove in some tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@deepakraj1997 You're right, but I think these are aws specific tests, which we want to skip for ibmcloud clusters (this can be discussed further though). If we use IBM COS bucket as BSL with ibmcloud/powerVS clusters, then we need to keep this to true, or fork an ibmcloud plugin out of the aws one.

Copy link
Member

Choose a reason for hiding this comment

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

@deepakraj1997 This is fine. It would apply to all specs within the ibmcloud which have to use aws plugin via the s3ForcePathStyle to work.

@kaovilai kaovilai merged commit 3fe6c28 into openshift:master May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Indicates a non-member PR verified by an org member that is safe to test. testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants