ATF Scripted step output not returned for next step

[Ron28]

I configured a server script ATF step where I get information from the hardware table PRD instance, compare this to what is defined in the instance the test is run on to identify IP addresses that I can run a first discovery on automatically.  While the script worked fine, I have an issue where I assign an IP address to an output variable which does not show in the step output when it is run. And subsequently, no value is passed to the Quick Discovery step and thus that step is failing. 

I've created a simplified version of assigning just a hardcoded output variable in a test server scripted config to eliminate any issue with the code:



But when running this step in a test, I am expecting IP Address to be assigned the value set. The step result is success, I would assume then that outputs.u_ip_address has a value. But it isn't showing in the step output:

When passing that value to a next step, that step fails as the mandatory input is missing. 

What am I doing wrong?

Thanks
Ron

[lauri457 · Accepted solution]

The value is just not stored, it should still work as an input. You can try by passing it to some random oob step

[Ron28]

Thanks Lauri, I didn't think of that. I do have a next OOB step to schedule a quick discovery, this step received an error and failed. I assumed that was due to the IP address being missing. 
The Discovery.Schedule.QuickDiscovery step has an issue "The step result was not set correctly, all steps must be set to success or failed". That's a different issue.

Thanks again!
Ron

[Ron28]

And just an update on the "Discovery.Schedule.QuickDiscovery" step, it wasn't exactly an out of the box step. It missed the stepResult setting completely.
Ron