error: the path "/tmp/local-volume.yaml" does not exist (sometimes) about kubevirtci

[rmohr]

/assign @awels

This happens pretty often on the openshift nodes (never saw it on the k8s ones). Do you have any idea why this coul happen?

[awels]

Maybe it is a case of OS-3.11 vs OS-3.11-multus, I see their provision script is slightly different. However I think this is where we copy the manifests into the VM: https://github.com/kubevirt/kubevirtci/blob/master/cluster-provision/cli/cli#L188 and that is the same for all providers.

But I thought the 'cli' script was being deprecated, so I am confused now.

[rmohr]

But I thought the 'cli' script was being deprecated, so I am confused now.

It is still used for provisioning.

[awels]

Okay, then I am not sure what is going on, as line 188 is called whenever a new image is created, and thus every VM should have that file in /tmp, unless there is something that removes it, but I haven't found anything like that anywhere.

[awels]

Btw the token for the link is expired so I can't look at the actual log file.

[rmohr]

ah, just remove the token. It is public accessible.

[rmohr]

Maybe there is something strange happening, like that they are copied to /tmp/tmp or so ...
We probably need to put some debug statements in a PR.

[awels]

Did you notice that there is an error in the log ahead of the missing /tmp/local-volume?

TASK [openshift_manage_node : Wait for sync DS to set annotations on all nodes] *** that fails

[rmohr]

Oh, then things start to make sense. 👍

[awels]

You need me to look into something more, or will you figure out why that is failing? I am guessing that is causing the additional failure with local volume.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.