You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This {{GITTAG}} may not be work well in a real environment when we are tracking master branch.
So this works when you have tagged a specific release, but when we are tracking master, it will keep changing on a specific commit ID depending on whether the source control has been updated, and a generic import has been done across all the osimages.
And when we try and rinstall we will get this problem:
[root@boston36 xcat_clusters]# rinstall mid21tor24cn04 osimage=demo.xcat.redhat-alt.full.netboot
Provision node(s): mid21tor24cn04
mid21tor24cn04: Did you run "genimage" before running "packimage"? kernel cannot be found at /install/custom/demo.xcat.redhat-alt.full.netboot/36366a9/kernel on boston36
Failed to generate petitboot configurations for some node(s) on boston36. Check xCAT log file for more details.
[root@boston36 xcat_clusters]#
So in this case, the ideal solution is that we would have a latest that doesn't care the git commit tag and it's the "working directory" as we are used to in xCAT to just be able to run genimage/packimage...
This may need more though on the use case..
The text was updated successfully, but these errors were encountered:
This
{{GITTAG}}
may not be work well in a real environment when we are tracking master branch.So this works when you have tagged a specific release, but when we are tracking master, it will keep changing on a specific commit ID depending on whether the source control has been updated, and a generic import has been done across all the osimages.
And when we try and
rinstall
we will get this problem:So in this case, the ideal solution is that we would have a
latest
that doesn't care the git commit tag and it's the "working directory" as we are used to in xCAT to just be able to run genimage/packimage...This may need more though on the use case..
The text was updated successfully, but these errors were encountered: