I'm fairly certain it was 10.5.1005.4864. I don't have access to that particular system now, but
pretty positive that was it. That's the version I'm running in a test VM I setup and I set the other
one up about the same time.
The test script I wrote to validate the issue contains:
job = self.shark.create_job(ifc, name, size, indexing_size_limit='1GB', start_immediately=False)
If I remove the job.stop() line, the job will be running when I look at it through the web interface.
Paul M. Toutant
Sr. Computer Scientist
EPG-FHFO, ManTech, Bldg 91061
COM: (254) 288-0245, DSN: 738-0245
CELL: (254) 681-8017
Turns out that there was bug in Python code -- basically a disagreement between the defaults in Python for "start_immediately" vs what the REST API was expecting.
This has been fixed in steelscript.netshark v0.9.2 -- let me know if you need it back ported to flyscript, as its a pretty trivial change.
Thanks for reporting it!