ts-debian-di-install: Don't set runvars for netboot kernel+ramdisk as outputs

Currently these runvars are either URLs provided by the definition
(e.g. make-flight) or output controller-relative paths created by the
execution (in the case where they aren't from the definition).

This wierd dual-semantics is confusing and wrong, and in particular is
broken if the test step is rerun (e.g. in standalone mode).

In the case where they are outputs only  these paths is information
only. The information is already available in the full logs so
dropping the runvars here merely removes the information from the
summary table. It's not so useful that this is an issue.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

diff --git a/ts-debian-di-install b/ts-debian-di-install
index a9b3b200c598cd558238209ef8031068a73018b6..96acd0e71d1583b4e97983fe2f37263b5fccf284 100755 (executable)
--- a/ts-debian-di-install
+++ b/ts-debian-di-install
@@ -163,9 +163,6 @@ sub setup_netboot($$$)
 
        target_putfile_root($ho, 60, $kernel, "$didir/kernel_${suite}_${arch}");
        target_putfile_root($ho, 60, $ramdisk, "$didir/ramdisk_${suite}_${arch}");
-
-       store_runvar("$gho->{Guest}_netboot_kernel", $kernel);
-       store_runvar("$gho->{Guest}_netboot_ramdisk", $ramdisk);
     }
 
     return <<END;