Skip to content

[It] podman machine cp fails when run on windows-2025 GH runner for 5.5.0-rc2 #26056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
arixmkii opened this issue May 2, 2025 · 2 comments · Fixed by #26176
Closed

[It] podman machine cp fails when run on windows-2025 GH runner for 5.5.0-rc2 #26056

arixmkii opened this issue May 2, 2025 · 2 comments · Fixed by #26176
Labels
kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote windows issue/bug on Windows

Comments

@arixmkii
Copy link
Contributor

arixmkii commented May 2, 2025

Issue Description

This test started to fail with error message assertions, when run on windows-2025 runner (details in result logs).

Steps to reproduce the issue

Steps to reproduce the issue

  1. Build Podman from 5.5.0-rc2 (or rc1) tag on windows-2025 runner
  2. Set VM provider to hyperv
  3. execute ./winmake localmachine "cp_test.go"

Describe the results you received

Assertion failed

   STEP: attempt copying file to a new directory - D:/a/qcw/qcw/podman-release/pkg/machine/e2e/cp_test.go:345 @ 05/02/25 16:40:59.803
  D:\a\qcw\qcw\podman-release\bin\windows\podman.exe machine cp --quiet C:\Users\RUNNER~1\AppData\Local\Temp\ginkgo2009196272\foo.txt 3fff3510aaff:~/directory/
  scp: dest open "directory/": Failure
  scp: failed to upload file C:/Users/RUNNER~1/AppData/Local/Temp/ginkgo2009196272/foo.txt to ~/directory/
  Error: copy failed: exit status 1
  D:\a\qcw\qcw\podman-release\bin\windows\podman.exe machine cp --quiet 3fff3510aaff:~/foo.txt C:\Users\RUNNER~1\AppData\Local\Temp\ginkgo3792166612\directory\
  scp: open local "C:/Users/RUNNER~1/AppData/Local/Temp/ginkgo3792166612/directory/": Unknown error
  Error: copy failed: exit status 1
  [FAILED] Expected
      <string>: scp: open local "C:/Users/RUNNER~1/AppData/Local/Temp/ginkgo3792166612/directory/": Unknown error
      Error: copy failed: exit status 1
      
  to contain substring
      <string>: scp: open local "C:/Users/RUNNER~1/AppData/Local/Temp/ginkgo3792166612/directory/": No such file or directory
  In [It] at: D:/a/qcw/qcw/podman-release/pkg/machine/e2e/cp_test.go:362 @ 05/02/25 16:41:05.038

  Full Stack Trace
    github.com/containers/podman/v5/pkg/machine/e2e_test.init.func8.2()
    	D:/a/qcw/qcw/podman-release/pkg/machine/e2e/cp_test.go:362 +0x1b2d
  < Exit [It] podman machine cp - D:/a/qcw/qcw/podman-release/pkg/machine/e2e/cp_test.go:229 @ 05/02/25 16:41:05.039 (1m10.974s)

Example run with windows-2025 https://github.com/arixmkii/qcw/actions/runs/14800785991/job/41558841884

Describe the results you expected

No error
Example run with windows-2022 runner https://github.com/arixmkii/qcw/actions/runs/14800643299/job/41558373745

podman info output

5.5.0-rc2 built from tag

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Standard github runner environment, runner windows-2025

Additional information

Issue is specific for windows-2025 runner, probably something specific to Windows 2025 server or some specifics of the scp bundled with that runner.

@arixmkii arixmkii added the kind/bug Categorizes issue or PR as related to a bug. label May 2, 2025
@arixmkii
Copy link
Contributor Author

arixmkii commented May 2, 2025

Created as a placeholder. This needs to be tested with Windows Server 2025 host to see if this is reproducible outside of the runner image.

@mheon mheon added remote Problem is in podman-remote windows issue/bug on Windows labels May 5, 2025
@l0rd
Copy link
Member

l0rd commented May 21, 2025

I have reproduced this same error while testing if e2e tests work on arm64 Windows (I have reproduced it on a Windows 11 Pro version 10.0.26100 build 26100). I am preparing a PR to fix it.

l0rd added a commit to l0rd/podman that referenced this issue May 21, 2025
The podman machine copy test "attempt copying file to a new directory"
was failing because on recent version of Windows the error message
doesn't match the expected error message. To make it work on new and
old version of Windows both old and new error messages are now
considered as valid.

Fixes containers#26056

Signed-off-by: Mario Loriedo <[email protected]>
l0rd added a commit to l0rd/podman that referenced this issue May 21, 2025
The podman machine copy test "attempt copying file to a new directory"
was failing because on recent version of Windows the error message
doesn't match the expected error message. To make it work on new and
old version of Windows both old and new error messages are now
considered as valid.

Fixes containers#26056

Signed-off-by: Mario Loriedo <[email protected]>
l0rd added a commit to l0rd/podman that referenced this issue May 21, 2025
The podman machine copy test "attempt copying file to a new directory"
was failing because on recent version of Windows the error message
doesn't match the expected error message. To make it work on new and
old version of Windows both old and new error messages are now
considered as valid.

Fixes containers#26056

Signed-off-by: Mario Loriedo <[email protected]>
l0rd added a commit to l0rd/podman that referenced this issue May 21, 2025
The podman machine copy test "attempt copying file to a new directory"
was failing because on recent version of Windows the error message
doesn't match the expected error message. To make it work on new and
old version of Windows both old and new error messages are now
considered as valid.

Fixes containers#26056

Signed-off-by: Mario Loriedo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote windows issue/bug on Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants