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

incus info fails to list snapshots in a YAMLish format #543

Closed
C0rn3j opened this issue Feb 27, 2024 · 4 comments
Closed

incus info fails to list snapshots in a YAMLish format #543

C0rn3j opened this issue Feb 27, 2024 · 4 comments

Comments

@C0rn3j
Copy link

C0rn3j commented Feb 27, 2024

Using btrfs backed LXD 4.x works correctly with a single line per snapshot, 5.0.3 changes the output to the full tables.

lxc info on LXD 4.0.9

Snapshots:
  snap0 (taken at 2024/02/27 09:51 CET) (stateless)

lxc info on LXD 5.0.3 and 5.20

Snapshots:
+-------+----------------------+------------+----------+
| NAME  |       TAKEN AT       | EXPIRES AT | STATEFUL |
+-------+----------------------+------------+----------+
| snap0 | 2024/02/27 09:56 CET |            | NO       |
+-------+----------------------+------------+----------+

incus info on 0.6.0 (please additionally note the whack expire time)

Snapshots:
+-------+----------------------+----------------------+----------+
| NAME  |       TAKEN AT       |      EXPIRES AT      | STATEFUL |
+-------+----------------------+----------------------+----------+
| snap0 | 2024/02/27 09:52 CET | 0001/01/01 00:57 LMT | NO       |
+-------+----------------------+----------------------+----------+

Was this intended? What used to be one line is now five, and it makes it hell to parse.
Incus additionally has a non-sensical expire time.

@stgraber stgraber closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2024
@stgraber
Copy link
Member

Info commands are meant for human consumption.

What you want in your case is incus snapshot list which has options for json, yaml and csv output.

@C0rn3j
Copy link
Author

C0rn3j commented Feb 28, 2024

Fair enough (though a bit womp-womp on the LXD deploys I manage), but how about the EXPIRES AT timestamp?

That looks like a bug for sure.

@stgraber
Copy link
Member

Yeah, I'm looking into that one, it looks like the zero timestamp isn't being correctly identified and rendered.

@stgraber
Copy link
Member

@C0rn3j #546

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants