Description of problem: Version 3.11.1 from the Fedora package shows very different runtime behavior than the same semantic version from the GitHub release page. Fedora version: $ helm version version.BuildInfo{Version:"v3.11", GitCommit:"", GitTreeState:"", GoVersion:"go1.19.6"} Upstream version: $ ~/helm version version.BuildInfo{Version:"v3.11.1", GitCommit:"293b50c65d4d56187cd4e2f390f0ada46b4c4737", GitTreeState:"clean", GoVersion:"go1.18.10"} I'm working with the following helm repo: $ helm repo add holoplot-registry-creds https://holoplot.github.io/registry-creds The chart in this repo has optional config keys. The Fedora version reports: $ helm install --set-string ecr.accessKeyID=foo --set-string ecr.secretAccessKey=foo --set-string ecr.account=132134 --set-string ecr.region=eu-central-1 registry-creds holoplot-registry-creds/registry-creds Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: unknown object type "nil" in XXXXX ... whereas the upstream version works just fine: $ ~/helm install --set-string ecr.accessKeyID=foo --set-string ecr.secretAccessKey=foo --set-string ecr.account=132134 --set-string ecr.region=eu-central-1 registry-creds holoplot-registry-creds/registry-creds W0412 13:55:21.381381 1528855 warnings.go:70] unknown field "spec.template.spec.resources" NAME: registry-creds LAST DEPLOYED: Wed Apr 12 13:55:21 2023 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None Similarly, what is just a warning in the upstream version is treated as hard error by what Fedora ships: $ helm install registry-creds holoplot-registry-creds/registry-creds --version=0.0.3 Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Deployment.spec.template.spec): unknown field "resources" in io.k8s.api.core.v1.PodSpec $ ~/helm install registry-creds holoplot-registry-creds/registry-creds --version=0.0.3 W0412 13:53:18.461486 1524404 warnings.go:70] unknown field "spec.template.spec.resources" NAME: registry-creds LAST DEPLOYED: Wed Apr 12 13:53:18 2023 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None Are the binaries in the Fedora packages built with any special compile-time flags or downstream patches? I'm also wondering why the git commit is missing in the version reporting.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
FEDORA-2024-1a2ac99e26 (helm-3.15.3-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-1a2ac99e26
Usually go packages in Fedora are built using dependencies that are already packaged for Fedora and can differ from what the package is expecting in `go.mod`. In most of the cases this is not an issue, but I think for packages related to k8s it can cause major issues as they require very specific versions for some modules. I just pushed a new package named `helm` to use vendored builds, which will use what go.mod defines for the package and not what Fedora has packaged. If you're still able to test you can get the update from bodhi or after a few days from the repo and re-test.
FEDORA-2024-1a2ac99e26 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1a2ac99e26` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1a2ac99e26 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-1a2ac99e26 (helm-3.15.3-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.