Conversation
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: cancelled. |
1bd11c7 to
6d9f197
Compare
6d9f197 to
9de979a
Compare
9de979a to
0ad330f
Compare
04f0d08 to
305e615
Compare
7cb7507 to
10338ca
Compare
d513d5a to
fd9de56
Compare
|
Workflow has started. The target step completed with status: failure. |
fd9de56 to
d5991d1
Compare
| vd.WithSize(ptr.To(resource.MustParse(vdsize))), | ||
| vd.WithNamespace(f.Namespace().Name), | ||
| vd.WithDataSourceHTTP(&v1alpha2.DataSourceHTTP{ | ||
| URL: imageURLDebian12, |
There was a problem hiding this comment.
But osType is "Windows".
There was a problem hiding this comment.
It is question for naming this feature, not for used OS. Debian more handy in auto test than Windows, and it is excellent fit purpose of this test.
| Expect(err).NotTo(HaveOccurred()) | ||
|
|
||
| By("Waits QEMU agent to be ready") | ||
| util.UntilVMAgentReady(client.ObjectKeyFromObject(vmTPM), framework.LongTimeout) |
There was a problem hiding this comment.
Is it necessary in this test case?
There was a problem hiding this comment.
In this test I install additional packages in the OS And check result through ssh. I didn't check whether it always works immediately after the virtual machine entered the Running phase, or it could lead to flaky tests.
Create legacy test for check tpm Signed-off-by: Dmitry Prytkov <[email protected]>
Create test with new framework Signed-off-by: Dmitry Prytkov <[email protected]>
Co-authored-by: Roman Sysoev <[email protected]> Signed-off-by: Dmitry Prytkov <[email protected]>
fix Signed-off-by: Dmitry Prytkov <[email protected]>
37bd518 to
e9d6090
Compare
fix Signed-off-by: Dmitry Prytkov <[email protected]>
Description
This PR updates e2e tests to check that VM properly recognizes tpm device.
Checklist