support running curtin in with debug

Bug #1467673 reported by Scott Moser on 2015-06-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Blake Rouse
curtin
Medium
Unassigned

Bug Description

would be nice to be able to make a change to maas to be albe to run curtin with debug enabled.
that would allow people to see more debug output of curtin on the console at least.
also nice would be to run with --showtrace.

currently this can only be accomplished by changing maas region controller's
  /usr/lib/python2.7/dist-packages/curtin/pack.py

the method 'pack_install' there just needs:
- command = ["curtin", "install"]
+ command = ["curtin", "-vv", "install"]

currently curtin's config cannot enable debug log or showtrace, so I'll add a task for that also.

Related branches

Scott Moser (smoser) wrote :

Added this to curtin.
now you can add to your curtin config somethin glike:

    verbosity: 3
    showtrace: true

and get the equivalent of '-vvv' and '--showtrace'

Changed in curtin:
importance: Undecided → Medium
status: New → Fix Committed
Changed in maas:
milestone: none → 1.9.0
assignee: nobody → Blake Rouse (blake-rouse)
status: New → In Progress
importance: Undecided → Medium
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Mike Pontillo (mpontillo) wrote :

Question: what is the disadvantage of enabling debugging?

Why would users *not* want to always see the additional output?

Mike Pontillo (mpontillo) wrote :

Ah, I think I answered my own question. (the verbose output contains the maas-metadata-credentials.)

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

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

Other bug subscribers