-
Notifications
You must be signed in to change notification settings - Fork 135
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
Fix test regression on LXD 4.0 #594
Fix test regression on LXD 4.0 #594
Conversation
062f30c
to
76bf24b
Compare
76bf24b
to
5694ecb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for rebasing to get testing on 4.0 :)
5694ecb
to
f6a01d2
Compare
f014738
to
b5ebdc5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please better explain the rational for the content_type
and create_at
fiddling as I don't fully understand why they need tweaking :/
e6d2aac
to
7c3ff77
Compare
8508894
to
2bd52ef
Compare
@simondeziel This is ready for a review. The changes should be better explained on the commit messages, if anything is still confusing let me know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content_type
handling is the last remaining concern/question I have.
Signed-off-by: hamistao <[email protected]>
Signed-off-by: hamistao <[email protected]>
Older LXD versions' APIs don't include: The `created_at` field, the `expires_at` field on /1.0/storage-pools/<pool>/volumes/custom/<volume_name>/snapshots, The `content_type` on /1.0/storage-pools/<pool>/volumes/custom/<volume_name>/snapshots/<snapshot_name>. Signed-off-by: hamistao <[email protected]>
Signed-off-by: hamistao <[email protected]>
2bd52ef
to
9137f09
Compare
@simondeziel This should be ready to merge |
Fixes #590.
Unfortunately, the best possible solution for
create
is picking the latest snapshot name when getting the object after creation.This is prone to error if multiple snapshots of the same volume are being taken concurrently. But since this isn't a realistic use case, these changes should be acceptable in favor of not hurting UX by returning an empty object.