V4.0 and Hyper-V - "diagnostics.py run"

What error do you get? It works on my box with 4.0.1 and Hyper-V

Essentially that it "can't create container" when it starts the process of trying to create what it needs for the tests. Running it from SSH to one of the CSVs. Didn't have a problem at any point on vSphere with 3.x as I haven't done many of these yet, so was just making sure it shouldn't be problem. You aren't doing anything special to run it right?

Hi ozzy01,

The "diagnostics.py run" script should run without issues on Hyper-V and NOS 4. A few questions for you:

1) What exact errors are you seeing when running the command?

2) Did you run the script in the past without running the cleanup (diagnostics.py cleanup) at the end?

Plain text or screen shots should suffice.

Thanks,
Tony

Im not onsite today, but seeing if i can get customer to run it again for us and send me the exact screenshot for you. stand by..

Here is screenshot of error. Tried from another CVM to make sure:

Interesting, looking at the output there it seems that the diagnostic VM is corrupted, maybe there was an issue with the pheonix ISO.

Here's the md5sum from my 4.0.1 lab system which works:

6b1441c998d1280ab248be481da0853d

Run md5sum ~/data/images/diagnostics/diagnostics_uvm.vhd.gz on one of the CVMs and compare it. I upgraded from 3.5.4, but I think these should still match

Do you know what Pheonix ISO was used to install this?
Did they upgrade to 4.0.1 or fresh install?

We can probably just replace the image with a good one and then the tests will complete. The best way to do this would be to open a case so that we can investigate and get him the right file.

Ok, I will let the customer know. This was for a PoC and wanted to make sure we ran the test to show the random read and write IOPS. I will have him open up a case as that would be good for him to go through that process anyway next week so they can see how good and helpful your support is 🙂