Hi, My change  to enable a consistent tracing mechanism for the many scripts diskimage-builder runs during its build seems to have hit a stalemate.
I hope we can agree that the current situation is not good. When trying to develop with diskimage-builder, I find myself constantly going and fiddling with "set -x" in various scripts, requiring me re-running things needlessly as I try and trace what's happening. Conversley some scripts set -x all the time and give output when you don't want it. Now nodepool is using d-i-b more, it would be even nicer to have consistency in the tracing so relevant info is captured in the image build logs. The crux of the issue seems to be some disagreement between reviewers over having a single "trace everything" flag or a more fine-grained approach, as currently implemented after it was asked for in reviews. I must be honest, I feel a bit silly calling out essentially a four-line patch here. But it's been sitting around for months and I've rebased it countless times. Please diskimage-builder +2ers, can we please decide on *something* and I'll implement it. -i  https://review.openstack.org/#/c/119023/ _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev