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

VolSync integration in test environment #661

Closed
1 of 4 tasks
nirs opened this issue Dec 6, 2022 · 0 comments · Fixed by #927
Closed
1 of 4 tasks

VolSync integration in test environment #661

nirs opened this issue Dec 6, 2022 · 0 comments · Fixed by #927
Assignees
Labels
test Testing related issue

Comments

@nirs
Copy link
Member

nirs commented Dec 6, 2022

According to @ShyamsundarR, volsync will be installed by ramen automatically using cluster manager add-on mechanism.

But even if ramen installs volsync, we have the issue that volsync crds are missing.
This causes ramen to fail on the managed cluster after few minutes. Can be fixed by
disabling volsync in ramen config manually, but this does not make sense if we want
to test volsync in the e2e tests.

Tasks:

  • Install volsync crds as part of starting the environment so we don't have to disable volsync in ramen configmap
  • If we install volsync crds, should install also the operator?
  • Is volsync installed automatically as expected?
  • Does it work without submariner?
    • The minikube clusters are using host network, so all of them are in libvirt default network (192.168.122.0/24)

Needs to discuss the right way to solve this.

Maybe start with disabling volsync in ramen config, since we don't need for metro dr
e2e tests, which is more urgent than regional dr e2e tests.

@BenamarMk what do yo think?

@nirs nirs added the test Testing related issue label Dec 6, 2022
@nirs nirs changed the title volsync integration in test environment VolSync integration in test environment Dec 6, 2022
nirs added a commit to nirs/ramen that referenced this issue Mar 16, 2023
This eliminates the need to disable volsync in ramen configmap. We will
improve this later to actually install volsync.

Part-of: RamenDR#661
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
nirs added a commit to nirs/ramen that referenced this issue Mar 16, 2023
This eliminates the need to disable volsync in ramen configmap. We will
improve this later to actually install volsync.

Part-of: RamenDR#661
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
nirs added a commit to nirs/ramen that referenced this issue Mar 16, 2023
This eliminates the need to disable volsync in ramen configmap. We will
improve this later to actually install volsync.

Part-of: RamenDR#661
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
nirs added a commit to nirs/ramen that referenced this issue Mar 16, 2023
This eliminates the need to disable volsync in ramen configmap. We will
improve this later to actually install volsync.

Part-of: RamenDR#661
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
ShyamsundarR pushed a commit that referenced this issue Mar 16, 2023
This eliminates the need to disable volsync in ramen configmap. We will
improve this later to actually install volsync.

Part-of: #661
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
@nirs nirs assigned nirs and unassigned BenamarMk May 15, 2023
@nirs nirs linked a pull request Jun 18, 2023 that will close this issue
@nirs nirs closed this as completed in #927 Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Testing related issue
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants