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

[BUG] Exporting data from the existing replicas has issues in 1.6.0 #8094

Closed
manju-rn opened this issue Mar 3, 2024 · 5 comments
Closed
Assignees
Labels
backport/1.6.1 kind/bug priority/0 Must be fixed in this release (managed by PO) require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Milestone

Comments

@manju-rn
Copy link

manju-rn commented Mar 3, 2024

Describe the bug

As per this documentation https://longhorn.io/docs/1.6.0/advanced-resources/data-recovery/export-from-replica/ Data from the replicas can be extracted and loaded as a device. However, in the latest documentation of 1.6.0, during the execution of Step 5, it results in error, with longhornio/longhorn-engine:v1.6.0

image

Error:
longhorn-instance-manager: error while loading shared libraries: libqcow.so.1: cannot open shared object file: No such file or directory

Resolution (Temporary)
However, by using longhornio/longhorn-engine:v1.5.4, it works fine. So believe some libs are missing in longhornio/longhorn-engine:v1.6.0

To Reproduce

Follow section 5 in https://longhorn.io/docs/1.6.0/advanced-resources/data-recovery/export-from-replica/ to extract the data from the replicas.

Further details are in #8092

@manju-rn manju-rn added kind/bug require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage labels Mar 3, 2024
@derekbit
Copy link
Member

derekbit commented Mar 3, 2024

cc @ChanYiLin

@innobead innobead added this to the v1.7.0 milestone Mar 3, 2024
@innobead innobead added priority/0 Must be fixed in this release (managed by PO) severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact) labels Mar 3, 2024
@derekbit
Copy link
Member

derekbit commented Mar 7, 2024

#613 cc @c3y1huang

@c3y1huang
Copy link
Contributor

#613 cc @c3y1huang

#7927

@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Mar 8, 2024

Pre Ready-For-Testing Checklist

PR:

@chriscchien
Copy link
Contributor

Verified pass on longhorn master(longhorn-engine 182b37)

Follow the instruction with longhorn master engine image, replica can be exported to a block device /dev/longhorn/pvc-850fb12d-a7c3-4c9d-9b76-f10fa943241c by below command and after mount the block device, the data is correct.

> docker run -v /dev:/host/dev -v /proc:/host/proc -v /var/lib/longhorn/replicas/pvc-850fb12d-a7c3-4c9d-9b76-f10fa943241c-b6b2dbb1:/volume --privileged longhornio/longhorn-engine:master launch-simple-longhorn pvc-850fb12d-a7c3-4c9d-9b76-f10fa943241c 2147483648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.6.1 kind/bug priority/0 Must be fixed in this release (managed by PO) require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Projects
Status: Resolved/Scheduled
Development

No branches or pull requests

7 participants