[Failing Test] multi ci gce-cos-k8sbeta-*

[pacoxu]

Which jobs are failing?

https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-alphafeatures
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-default
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-ingress
https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-reboot

Which tests are failing?

kubetest.IsUp

Since when has it been failing?

05-06

Testgrid link

https://testgrid.k8s.io/sig-release-1.30-blocking#gce-cos-k8sbeta-reboot

Reason for failure (if possible)

Specify --start=72893 in the next get-serial-port-output invocation to get only the new output starting from here.
/usr/bin/scp: /var/log/cluster-autoscaler.log*: No such file or directory
/usr/bin/scp: /var/log/fluentd.log*: No such file or directory
/usr/bin/scp: /var/log/kubelet.cov*: No such file or directory
/usr/bin/scp: /var/log/startupscript.log*: No such file or directory
ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1].
Dumping logs from nodes locally to '/logs/artifacts'

{ error during ./hack/e2e-internal/e2e-status.sh: exit status 1}

Anything else we need to know?

No response

Relevant SIG(s)

No response

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[pacoxu]

Is it related to #124519?

[aojea]

it is passing now

[neolit123]

/sig cloud-provider
/area provider/gcp
/close

[k8s-ci-robot]

@neolit123: Closing this issue.

In response to this:

/sig cloud-provider
/area provider/gcp
/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-sigs/prow repository.