lxc-copy message is the wrong way around

Bug #1551935 reported by Martin Pitt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

$ sudo lxc-copy -n adt-wily -e
Created adt-wily as clone of adt-wily_1WtXPo

This should say "Created adt-wily_1WtXPo as a clone of adt-wily". This might seem trivial, but is highly relevant when trying to parse that message to find out the cloned container name. This is still not easy at all :-(

Revision history for this message
Christian Brauner (cbrauner) wrote :

I'm fixing the ordering now. Regarding the last part "This is still not easy at all.": Do you mean that the message should be simpler (e.g. Created adt-wily_1WtXPo)?

Changed in lxc (Ubuntu):
status: New → Confirmed
status: Confirmed → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Well, the point is not really about "simpler", but "might change/be i18n'ed" and thus "is not predictable". However, this is really a side issue to this report. The non-machine-readability was originally bug 1197754, but it applies to lxc-copy as well. If/once the message is stable, I can parse "^Created ([^ ]+)", but this still isn't a nice API.

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks Christian for the fast fix!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc - 2.0.0~rc5-0ubuntu1

---------------
lxc (2.0.0~rc5-0ubuntu1) xenial; urgency=medium

  * New usptream release (2.0.0~rc5)
    - Fix a number of cgfs issues (LP: #1549363, LP: #1543697, LP: #1552355)
    - Fix attach failing to allocate a tty (LP: #1551960)
    - Fix LXC rebooting the container despite post-stop failure
    - Fix lxc-copy output (LP: #1551935)
    - Documentation, manpagen and manpage translations update
    - Update to the plamo template

 -- Stéphane Graber <email address hidden> Thu, 03 Mar 2016 11:05:25 -0500

Changed in lxc (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.