emerge-gitclone failed to checkout refs/heads/flatcar-build-2345.3.0

[ofer-tvil]

Hi,

I try to build a kernel module for flatcar-linux container.
I followed this guide:
https://docs.flatcar-linux.org/os/kernel-modules/#prepare-a-flatcar-container-linux-development-container

I see a git checkout error that happens when attempting to checkout refs/heads/flatcar-build-2345.3.0

Can someone check the emerge-gitclone cmd?

Here is the log:

null_resource.run_install_script (remote-exec): Resolving deltas: 100% (53285/53285), done.
null_resource.run_install_script (remote-exec): >>> Git clone in /var/lib/portage/portage-stable successful
null_resource.run_install_script: Still creating... (3m20s elapsed)
null_resource.run_install_script (remote-exec): Note: switching to 'c98cd46975ab04d1178c7edfdefcc07458200d5f'.
null_resource.run_install_script (remote-exec): You are in 'detached HEAD' state. You can look around, make experimental
null_resource.run_install_script (remote-exec): changes and commit them, and you can discard any commits you make in this
null_resource.run_install_script (remote-exec): state without impacting any branches by switching back to a branch.
null_resource.run_install_script (remote-exec): If you want to create a new branch to retain commits you create, you may
null_resource.run_install_script (remote-exec): do so (now or later) by using -c with the switch command. Example:
null_resource.run_install_script (remote-exec):   git switch -c <new-branch-name>
null_resource.run_install_script (remote-exec): Or undo this operation with:
null_resource.run_install_script (remote-exec):   git switch -
null_resource.run_install_script (remote-exec): Turn off this advice by setting config variable advice.detachedHead to false
null_resource.run_install_script (remote-exec): HEAD is now at c98cd4697 2345.3.0
null_resource.run_install_script (remote-exec): >>> Release checkout c98cd46975ab04d1178c7edfdefcc07458200d5f in /var/lib/portage/portage-stable successful]

null_resource.run_install_script (remote-exec): >>> Cloning repository 'coreos' from 'https://github.com/flatcar-linux/coreos-overlay.git'...
null_resource.run_install_script (remote-exec): >>> Starting git clone in /var/lib/portage/coreos-overlay
null_resource.run_install_script (remote-exec): Cloning into '/var/lib/portage/coreos-overlay'...
null_resource.run_install_script (remote-exec): remote: Enumerating objects: 36, done.
null_resource.run_install_script (remote-exec): remote: Counting objects:   2% (1/36)
null_resource.run_install_script (remote-exec): remote: Counting objects:   5% (2/36)

null_resource.run_install_script (remote-exec): Resolving deltas: 100% (45747/45747), done.
null_resource.run_install_script (remote-exec): >>> Git clone in /var/lib/portage/coreos-overlay successful
null_resource.run_install_script (remote-exec): error: pathspec 'refs/heads/flatcar-build-2345.3.0' did not match any file(s) known to git
null_resource.run_install_script (remote-exec): Traceback (most recent call last):
null_resource.run_install_script (remote-exec):   File "/usr/lib/python-exec/python2.7/emerge-gitclone", line 55, in <module>
null_resource.run_install_script (remote-exec):     subprocess.check_call(['git', '-C', repo.location, 'checkout', commit])
null_resource.run_install_script (remote-exec):   File "/usr/lib64/python2.7/subprocess.py", line 190, in check_call
null_resource.run_install_script (remote-exec):     raise CalledProcessError(retcode, cmd)
null_resource.run_install_script (remote-exec): subprocess.CalledProcessError: Command '['git', '-C', u'/var/lib/portage/coreos-overlay', 'checkout', u'refs/heads/flatcar-build-2345.3.0']' returned non-zero exit status 1
null_resource.run_install_script (remote-exec): Container flatcardevelopercontainer.bin failed with error code 1.

[dongsupark]

Thanks.
We are already aware of the issue.
So we fixed the issue via flatcar-linux/flatcar-dev-util#2, for Alpha 2430.0.0 and Edge 2430.99.0.
Next Stable and Beta releases are also going to have the fix.

[dongsupark]

Stable 2345.3.1 was just released, so this issue should be fixed.
If you still see the issue, feel free to reopen it.
Thanks.