[Starlingx-discuss] Building openstack-helm under OpenSUSE OBS after option serve has been removed from helm fails
Hello, The building process of the package openstack-helm under the OpenSUSE OBS is expecting the option 'serve' of the helm command to be available. The option 'serve' has been removed from helm (commit b8eb479a4f3b1934770c75ed9013dfe263d8940f from April 2018) and that change has now surfaced in OpenSUSE packages. Would some be able to indicate a viable alternative to the mode "helm serve --local-repo" -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre
In Centos, openstack-helm is installing this version in mock: helm-2.13.1-0.tis.2.x86_64 1560862674 37163874 f8bf2d311350ac6b6b4c3059b16cf54d installed However the spec file we use does not actually specify an upper version value for helm, so presumably if we were to update our rpm repo and pick up a higher version of helm we would likely hit the same issue. https://opendev.org/starlingx/upstream/src/branch/master/openstack/openstack... For now, I'd suggest setting a max version of helm for in your spec file to 2.13 for that BuildRequires Al -----Original Message----- From: Dominig ar Foll (Intel Open Source) [mailto:dominig.arfoll@fridu.net] Sent: Monday, July 22, 2019 12:13 PM To: Starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Building openstack-helm under OpenSUSE OBS after option serve has been removed from helm fails Hello, The building process of the package openstack-helm under the OpenSUSE OBS is expecting the option 'serve' of the helm command to be available. The option 'serve' has been removed from helm (commit b8eb479a4f3b1934770c75ed9013dfe263d8940f from April 2018) and that change has now surfaced in OpenSUSE packages. Would some be able to indicate a viable alternative to the mode "helm serve --local-repo" -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 23/07/2019 16:10, Bailey, Henry Albert (Al) wrote:
In Centos, openstack-helm is installing this version in mock: helm-2.13.1-0.tis.2.x86_64 1560862674 37163874 f8bf2d311350ac6b6b4c3059b16cf54d installed It's coming. Just a question of time. However the spec file we use does not actually specify an upper version value for helm, so presumably if we were to update our rpm repo and pick up a higher version of helm we would likely hit the same issue. https://opendev.org/starlingx/upstream/src/branch/master/openstack/openstack... I am afraid that a solution not using "serve" will be required. For now, I'd suggest setting a max version of helm for in your spec file to 2.13 for that BuildRequires As a work around, I have built an a version 2.13 of helm for 15.0 and 15.1
If the multiOS team wants it, they have to update their meta file to reflect the following repos referencing. <repository name="openSUSE_Leap_15.1"> <path project="Cloud:OpenStack:Stein" repository="openSUSE_Leap_15.1"/> <path project="home:dominig:helm-backport" repository="openSUSE_Leap_15.1"/> <path project="openSUSE:Leap:15.1:Update" repository="standard"/> <path project="openSUSE:Leap:15.1" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.0"> <path project="Cloud:OpenStack:Stein" repository="openSUSE_Leap_15.0"/> <path project="home:dominig:helm-backport" repository="openSUSE_Leap_15.0"/> <path project="openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE:Leap:15.0" repository="standard"/> <arch>x86_64</arch> </repository> </project> -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre
participants (2)
-
Bailey, Henry Albert (Al)
-
Dominig ar Foll (Intel Open Source)