nslcd has been replaced by sssd on Debian. The puppet-nslcd
package is no longer needed. With this change, the package
is no longer built and included in the image.
Test Plan on Debian:
PASS: image build
PASS: After system deployed, verify puppet-nslcd package doesn't
exist.
PASS: openldap functions (user addition, user login on console and
by ssh, etc) work properly.
Story: 2009834
Task: 46174
Depends-On: https://review.opendev.org/c/starlingx/stx-puppet/+/855513
Signed-off-by: Andy Ning <andy.ning@windriver.com>
Change-Id: Ia29dc8e66fc1f7e7c537b4dea87511aba00f2217
This is part of the change to replace nslcd with sssd to
support multiple secure ldap backends.
This change removed nss-pam-ldapd (nslcd, libpam-slapd,
libnss-slapd) on Debian based stx system.
nscd is removed in
https://review.opendev.org/c/starlingx/tools/+/854217
Test Plan on Debian:
PASS: Package build, image build
PASS: System deployment
PASS: Verify nslcd, libpam-slapd, libnss-slapd are not installed.
PASS: ldap functions work properly (ldap user creation, user login
on console and by ssh etc).
Story: 2009834
Task: 46069
Depends-On: https://review.opendev.org/c/starlingx/metal/+/854203
Signed-off-by: Andy Ning <andy.ning@windriver.com>
Change-Id: I87de211876a00c0b0a0d629dde70e13c0feb3df0
It was detected the networking.service is marked as failing after reboot.
It happpens because "ifup -a" is executed by the service.
It starts to run the scripts in /etc/network/interfaces.d/.
But several scripts in ifupdown-extra are not prepared to handle "-all".
In the case of nss-pam-ldapd the script /etc/network/if-up.d/nslcd
is failing when there are loopback interfaces with label (lo:X) as the
script only tests the interface "lo".
Test Plan (Debian only - AIO-SX and AIO-DX)):
PASS Check systemctl status networking.service after unlock
Closes-Bug: #1983503
Change-Id: I1fd9e2ea75233d987d6f1f2aa5a3395ab2885e2b
Signed-off-by: Fabiano Mercer <fabiano.correamercer@windriver.com>
This change adds the gpu-operator package to the Debian build. The
NVIDIA GPU Operator uses the operator framework within Kubernetes to
automate the management of all NVIDIA software components needed to
provision GPU.
The provided patches come from the CentOS port done in
https://review.opendev.org/c/starlingx/integ/+/784144https://review.opendev.org/c/starlingx/integ/+/817725
Test plan (Debian only)
PASS build ISO with the package installed
PASS execute helm install
PASS execute helm uninstall
Story: 2009968
Task: 45976
Signed-off-by: Andre Fernando Zanella Kantek <AndreFernandoZanella.Kantek@windriver.com>
Change-Id: Ic656d764dc3e31dcd89e02b172c14eb6d32743a7
Historically, with CentOS, we had issues related to LV activation
occurring in a non-deterministic way and causing an assortment of
provisioning issues. More deterministic LV activation was achieved by
setting use_lvmetad = 0 in /etc/lvm/lvm.conf
In the migration to Debian, a much more recent version of the lvm2
package is in use. In the intervening versions of lvm2, lvmetad was
removed making use_lvmetad and the associated behavior now obsolete.
In some current random testing scenarios, emergency mode is seen when
booting the Debian ISO. Reviewing the systemd dump of services
initiating when emergency mode occurs, it is observed that LV activation
is occurring at a different time and order vs. a successful boot.
The Debian lvm2 version provides configuration parameter
global/event_activation which when set to 0 will change LV activation
behavior when a PV appears. No noticable change was observed when this
variable is set.
The current upstream version from Debian Bullseye is missing an lvm2
upstream patch the should address this issue.
Patch the Debian lvm2 version with this upstream patch to enable testing
with this enabled.
Test Plan:
PASS - Build ISO, install/provision in AIO-SX virtual/hardware labs
PASS - Perform numerous reboot cycles an observe no issues
PASS - Test on H/W setup that has shown energency mode behavior to
confirm that this version and associated config file change
resolved emergency mode PV/LV activation issues
Change-Id: If22e446126f33c2155bd70988ed9b0444d230730
Partial-Bug: #1979105
Signed-off-by: Robert Church <robert.church@windriver.com>
There is a need to modify the source code of the kdump-tools package to
adapt it to Debian-based StarlingX. This commit replaces the binary
package with a source package.
The default kernel image is located at /boot/vmlinuz-${kernel_version}
in Debian system. But it is /boot/1/vmlinuz-${kernel_version} in the
current starlingx system. In addition, initrd.img is also different
because we use ostree. So this commit creates two soft links for
vmlinuz and initrd.img.
Test Plan:
PASS: Image builds successfully.
PASS: kdump-tools installs successfully.
PASS: Can generate vmcore files in /var/crash after kernel panic.
Story: 2009964
Task: 45623
Depends-On: https://review.opendev.org/c/starlingx/tools/+/845886
Depends-On: https://review.opendev.org/c/starlingx/tools/+/845884
Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
Change-Id: Ifffbf0e436e79d9547a478f8b725e18f283d138e
This commit patches iputils-ping in Debian-based StarlingX so that ping
prints out ICMP echo replies with unexpected/"wrong" source IP addresses
as was done with CentOS 7's version of ping and as is done with more
recent versions of the iputils package. As an example, if the user calls
"ping 192.168.1.1" and the ICMP echo responses are sent by 192.168.1.3,
then the version of ping in Debian 11 currently assumes that no
responses have been received. This issue was discovered while running
the eBPF test cases in the kernel's samples/bpf source sub-directory.
This issue was introduced upstream with the following commit:
5e052ada96c3 ("ping: discard packets with wrong source address")
https://github.com/iputils/iputils/commit/5e052ada96c3
The following commit fixes this issue:
5f6bec5ab57c ("ping: Print reply with wrong source with warning")
https://github.com/iputils/iputils/commit/5f6bec5ab57c
Due to a number of contextual dependencies, we unfortunately cannot
directly cherry-pick the commit that fixes this issue. Hence, we
cherry-pick four patches in total. We did not opt for completely
uprevisioning the iputils package to be able to inherit bug fixes that
Debian may introduce in the future.
We checked the list of commits between the two tags 20210202 and
20211215 using the following command:
git log --oneline refs/tags/20210202..origin/master -- 'ping/*.[ch]'
And we did not find any commits that fix issues in the commits that we
are cherry-picking with this commit.
Testing:
- An ISO image with the standard kernel was successfully incrementally
built with this commit.
- The resulting ISO image was installed onto a qemu/KVM-based virtual
machine and the resulting system was bootstrapped with Ansible and
unlocked.
- The test cases shipped in the kernel repository's samples/bpf
sub-directory were successfully executed in the virtual machine. These
test cases make use of ping in IPv4 and IPv6 mode, which ought to be a
good sanity test.
Partial-Bug: 1977849
Change-Id: I25b42b8de80deec86be0eb504442992863a8d833
Signed-off-by: M. Vefa Bicakci <vefa.bicakci@windriver.com>
The following dependencies were generating the warning
"module 'openstacklib' has unresolved dependencies"
during bootstrap and unlock on Debian:
puppetlabs-openstacklib (v17.4.0) asks for
puppetlabs-postgresql version >=6.4.0 <7.0.0
puppetlabs-mysql (v8.1.0) asks for
puppetlabs-translate version >= 1.0.0 < 2.0.0
Comparing puppetlabs-postgresql v8.0.0 with v6.10.2: It can be
verified that support for Debian 11 was added on v7.4.0, which is
already out of the specified range.
Other than added functionality and fixes, here are the major changes
between v6.10.2(latest version inside of range) and v8.0.0:
v7.0.0 drops support for SLES 11 and RHEL 5, and bumps minimum Puppet
version to 6.0.0 (We are currently using Puppet 5.5.22, but it should
be noted that the minimal version was bumped up because Puppet 5 was
removed from the test cases and not because there are signs of
malfunction).
v8.0.0 drops support for CentOS 6, Debian 6, and Ubuntu 10, which is not
a problem since we are not using any of those OSs.
In conclusion, any version earlier than v7.4.0 should not be used and
there are no known disadvantages to using v8.0.0 instead of v7.4.0.
puppetlabs-translate v2.0.0 removes support for Debian 7 and bumps up
the minimum Puppet version (both of those are irrelevant here since we
are on Debian 11 and the Puppet version is still inside the range).
All other changes introduced from v2.0.0 to v2.2.0 are added support
and minor fixes.
Therefore, it should be safe to use v2.2.0 without a problem.
Debian Bullseye tests:
PASS: Build & install
PASS: Successful Bootstrap
PASS: Successful Unlock
Story: 2009964
Task: 45496
Signed-off-by: Matheus Machado Guilhermino <Matheus.MachadoGuilhermino@windriver.com>
Change-Id: I73fe64b867026ba38b0db7b0a8b34fed388e4d66
This change adds the package k8s-cni-cache-cleanup to StarlingX's
Debian build
Test Plan:
PASS build Debian ISO
PASS install AIO-SX Debian ISO
PASS Check package k8s-cni-cache-cleanup is present
PASS Check presence of script /usr/local/sbin/k8s-cni-cache-cleanup
Story: 2009965
Task: 45461
Signed-off-by: Andre Fernando Zanella Kantek <AndreFernandoZanella.Kantek@windriver.com>
Change-Id: I277937ad1be326f75c3b5fc01a30e775a7b9ca0a
Before Bullseye got released openscap was removed
from the repository because it had some installability
issues according to the bug reports. Most notably it
hard codes to a specific version of Perl.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993328)
This has been fixed in newer versions of openscap,
so in order to make life easier just use the newer
release tarball from Github, along with the Debian
packaging from Debian Experimental. This approach was
taken because the source package was not in versioned
control yet in the Debian's git repository yet. Once
it has been included then the current strategy can
be revisitied. No changes were made to the original
Debian packaging.
Test Plan
Build openscap package.
Install ISO
Run openscap binary
Story: 2009964
Task: 45395
Signed-off-by: Charles Short <charles.short@windriver.com>
Change-Id: I7f646cd940aaa6871f3f184498b3e3f3689724fd
This change add support to accept netmask or prefix-length on the
routes file, internally the commands will use prefix-len
Change the command from "route" to "ip route" as this one have better
support for IPv6 (route --inet6 add is failing on Debian).
Also, on the validation functions, the address family is set to allow
IPv6 route check.
Test Plan:
PASS add IPv6 static routes with system host-route-add
PASS add IPv4 static routes with system host-route-add
PASS remove IPv6 static routes with system host-route-delete
PASS remove IPv4 static routes with system host-route-delete
Closes-Bug: 1974229
Signed-off-by: Andre Fernando Zanella Kantek <AndreFernandoZanella.Kantek@windriver.com>
Change-Id: I33d249892b717f4e808a995ced455c4c9ac763f2
Update puppetlabs-postgresql to 8.0.0, since it fully supports
Debian bullseye, and the version we were using doesn't support it
fully.
This does not affect Centos builds at all.
Test Plan
PASS Build packages
PASS Test ISO install
Story: 2009101
Task: 43326
Depends-On: https://review.opendev.org/c/starlingx/utilities/+/840497
Signed-off-by: Charles Short <charles.short@windriver.com>
Change-Id: I195003be09af86d3430fe901057ec4bf559c51ed
A problem may occur if puppet attempts to inject a firewall rule
while the underlying iptables/ip6tables has existing rules which
use the --random-fully flag in the NAT table.
The issue occurs because puppet-firewall first makes a call to
iptables-save/ip6tables-save to parse the existing rules
(to determine if the rule already exists). If it finds a rule
with --random-fully, it will immediately bail out.
The current version(s) of puppet-firewall in StarlingX are old
enough that they don't have parsing logic for the --random-fully
flag that was initially supported in iptables version 1.6.2+.
Now that StarlingX uses iptables 1.8.4, we must account for the
possibility that various components (ie. kubernetes) will make
use of --random-fully rules.
This feature has been implemented upstream in the following commits:
https://github.com/puppetlabs/puppetlabs-firewall/commits/
9a4bc6a81cf0cd4a56ba458fadac830a2c4df529
0ea2b74c0b4a451a37bae8c2ff105b72481ab485
The above commits have been ported back to:
CentOS: puppet-firewall-1.8.2
Debian: puppetlabs-firewall-1.12.0
Since StarlingX does not currently build it's own version
of puppet-firewall in either CentOS or Debian, this commit
also contains the infrastructure to do so.
Testing:
Note: Since the issue is intermittent on unlock, the functional
tests were performed with a custom runtime manifest that installed
a dummy iptables/ip6tables rule when an interface was modified.
At this time, it was guaranteed that there were rules with
the --random-fully flag present.
CentOS:
Package build: PASS
Present in iso: PASS
IPv4 functional test (iptables): PASS
IPv6 functional test (ip6tables): PASS
Debian:
Package build: PASS
Present in iso: PASS
IPv4 functional test (iptables): PASS
IPv6 functional test (ip6tables): PASS
Closes-Bug: #1971900
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: I7dbb9e1b99d95df0aa5a7db7aa22c3c314253788
Add kpatch 0.9.5 of debian packaging.
The source code package is from
https://github.com/dynup/kpatch/archive/refs/tags/v0.9.5.tar.gz
kpatch is a Linux dynamic kernel patching tool which allows you to
patch a running kernel without rebooting or restarting any processes.
It enables sysadmins to apply critical security patches to the kernel
immediately, without having to wait for long-running tasks to complete,
users to log off, or for scheduled reboot windows.
It gives more control over up-time without sacrificing security or
stability.
Need to work together with the relevant kernel module.
Test Plan:
Pass: Build successfully with 'build-pkgs -p kpatch'
Story: 2009221
Task: 44580
Signed-off-by: Zhixiong Chi <zhixiong.chi@windriver.com>
Change-Id: I664ca39c1cbc7bfdf0f5a57ac10118f4a9b62037
Package haproxy-config add the haproxy init script file, but,
in the debian package it already contains the script file.
In order to avoid using dpkg-divert on haproxy-config package,
this patch was created to remove the script file from original
debian package.
Test:
PASS: built image successfully
PASS: Installed image successfully (with haproxy)
PASS: Bootstrap and unlock successfull
Story: 2009964
Task: 45036
Signed-off-by: aoliveir <adriano.oliveira@windriver.com>
Change-Id: I93e9fd0d2e80d1fd7f509aebe995547fee502229
Python NSS module is not buildable by pip on Debian/bullseye and
requires patches. The debian package for this module contains the
required fixes, but contains 2 other problems:
- it builds only the PY3-version of itself
- it (incorrectly) doesn't install pip metadata, making it "invisible"
by pip
Solution: import python-nss from debian/bullseye + add patches that fix
the above problems.
TESTS
================
Build package in debian environment
Story: 2009897
Task: 44691
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
Change-Id: I65ab9b967e38340939bd99c389b72820ee17571b
To align with k8s 1.21.8 to 1.23.1
Upgrade runc from version 1.0.0-rc95 to 1.0.2
Dependencies are packaged in this change.
Dependencies:
golang-github-checkpoint-restore-go-criu-dev (>= 5.1.0~)
golang-github-coreos-go-systemd-dev (>= 22.3.2~)
golang-github-opencontainers-specs-dev (>= 1.0.2.66~)
golang-github-cilium-ebpf-dev (>= 0.6.2~)
Note:
As of this date, except golang-github-cilium-ebpf-dev,
all other dependencies are new and not available in bullseye
main. They are available in sid though. It was preferred to
package them from source than adding them in base-bullseye.lst.
Also, runc failed to build if newest version (0.7.0) of
golang-github-cilium-ebpf-dev is used. The exact reason is not
clear. So it was preferable to package its minimum required
version.
Test Plan:
runc package builds successfully
All packages build successfully
Image builds successfully
Story: 2009845
Task: 44456
Signed-off-by: Kaustubh Dhokte <kaustubh.dhokte@windriver.com>
Change-Id: I4139f9eb689a9e8c8e18c7a9b15fd2d592752ee5
This commit is a follow-on for d900a5b which introduced
the bond-cni plugin for Centos. In this commit we
introduce the same plugin for Debian.
Since there is no existing Debian package for the bond-cni,
we build it from source (tar.gz) to create the package.
The plugin is installed at /usr/libexec/cni/ to align
with where k8s expects plugins to be in StarlingX.
Testing:
Pass: Build
Pass: bond plugin present at /usr/libexec/cni/
Story: 2009800
Task: 44845
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: Ib9e805d587604f9b0a43a685b9b6970e5be1deb4
In debian builds, patch lsb-base package to add method to
/lib/lsb/init-functions to wrap status calls to use correct method
status_of_proc()
This fixes fm-mgr service failing to recover on host unlock on debian.
Test Plan:
PASS: Package builds and install successfully with debian build
PASS: fm-mgr service recovers on host unlock on debian on AIO-SX
PASS: No impact on centos build, install or provisioning of AIO-SX
Closes-Bug: 1963296
Signed-off-by: Gerry Kopec <gerry.kopec@windriver.com>
Change-Id: I607c4b3b6ed8aaaff2654e97d0baa826c57741a2
This commit uprevs the containernetworking-plugins to 1.0.1 on
Debian.
The version of this package has a Build-Depends on:
golang-github-appc-cni-dev >= 1.0.1
golang-github-vishvananda-netlink-dev >= 1.1.0.125
Currently, the Debian Bullseye release provides:
golang-github-appc-cni-dev = 0.8.1
golang-github-vishvananda-netlink-dev = 1.1.0-2
So in order to build the containernetworking-plugins 1.0.1, this
commit pulls in the appropriate versions of the dependencies
and builds them too.
The other thing to note in this commit is that the plugin install
path has been changed from /usr/lib/cni/ to /usr/libexec/cni/.
This aligns with where k8s expects to find CNI plugins on StarlingX
Testing:
- PASS: downloader -s
- PASS: full build
- PASS: install and ensure the plugins are present
at /usr/libexec/cni/
- PASS: install and ensure the package is the correct version
Story: 2009832
Task: 44635
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: Ic1c9a0d7eb2adb831c6316e1ab72d288ac805929
The following dependency was generating a
"unresolved dependency" warning during bootstrap on Debian:
puppet-stdlib (>= 4.6.0 < 5.0.0)
Debian is currently using puppet-stdlib 5.0.0 and the
most recent version of puppet-etcd asks for puppet-stdlib
(>= 4.6.0 < 5.0.0).
puppet-stdlib 5.0.0 provides the same manifests, classes
and functions as puppet-stdlib 4.25.1, the changes are more
present in the packaging architecture, inclusion of a new function,
and improved and updated documentation.
Updating the dependency declaration to allow version 5.0.0
of puppet-stdlib removes the warning, shows no signs of malfunction,
and does not prevent from successfully bootstraping and unlocking.
For that, the package puppet-etcd-1.12.3 was included and patched.
Debian Bullseye tests:
PASS: Build & install
PASS: Successful Bootstrap
PASS: Successful Unlock
Story: 2009101
Task: 44772
Signed-off-by: Matheus Machado Guilhermino <Matheus.MachadoGuilhermino@windriver.com>
Change-Id: I940faf6c406fa0146da86976154f4e4793621c40
This work is part of Debian integration effort. This work only affects
debian.
We package the same version of ceph for both CentOS and Debian.
Since we know the puppet-ceph module on CentOS is supposed to work,
use this on Debian also to reduce testing and possible issues.
Patches were copied from CentOS and not touched.
Drop one patch to metadata.json, we know we have some work to do in
that area to clear puppet warnings, but will be done part of a
generic clearing puppet warnings effort.
The sources need to be patched to work with debhelper-compat 13, which
we don't care now.
There are some integration issues, but testing so far revealed that
during a puppet replay for aio manifest ceph data and ceph journal
partitions were created.
Story: 2009101
Task: 43431
Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com>
Change-Id: I90adc736ea52e6c4f9946520156f53e572c224cc
This work is part of the Debian integration efforts
This work only affects Debian.
Depends-On: https://review.opendev.org/c/starlingx/integ/+/831738
Debian tests:
PASS: build-pkgs
PASS: build-image
PASS: install
Story: 2009101
Task: 44402
Signed-off-by: Chuck Short <charles.short@windriver.com>
Change-Id: I48c513dba0fb07edc5413e8ba3b139430e53c8bd
This is a transient work that enables us to progress Debian
integration. This work affects only Debian.
Sysinv loads stevedore plugins. The logic is based on the fact that
the source files are listed in SOURCES.txt which is included in the
egg. The package that provides a plugin is determined by parsing
entry_point and distribution data. Distribution data loads
information from SOURCES.txt.
dh-python is used during build and silently removes the file that
sysinv expects to be present.
Patch the package to keep the file.
Skip CentOS tests because this is a Debian only package.
Debian tests:
PASS: build python package, build non-package python
PASS: SOURCES.txt present in .egg-info in python package
Partial-Bug: https://bugs.launchpad.net/starlingx/+bug/1955648
Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com>
Change-Id: Id45b1ba93f9ee88cc01a9cb1fb25527b8a5f1e19
This is a transient work that enables us to progress Debian
integration. This work affects only Debian.
Sysinv loads stevedore plugins. The logic is based on the fact that
the source files are listed in SOURCES.txt which is included in the
egg. The package that provides a plugin is determined by parsing
entry_point and distribution data. Distribution data loads
information from SOURCES.txt.
Setuptools doesn't copy the desired file to egg.
Patch python3-setuptools so it copies the file to egg.
Skip CentOS tests because this is a Debian only package.
Debian tests:
PASS: build python package, build non-package python
PASS: SOURCES.txt present in .egg-info in python package
Partial-Bug: https://bugs.launchpad.net/starlingx/+bug/1955648
Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com>
Change-Id: Ia318aa0ca6825adfa3d23159691486067d96d475
This work is part of Debian integration efforts.
This work affects only Debian
Enable grubby to be built.
Debian tests:
PASS: build-pkgs
PASS: build-image
PASS: install
PASS: bootstrap
Story: 2009101
Task: 44402
Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com>
Change-Id: I567f51828b6e10f3b0be2d404f1870829b0c9399
This package was created to direct
/ect/init.d/functions to lib/lsb/init-functions
This was done to avoid altering files that
are relevant to CentOS.
Test Plan:
PASS: Package installed and ISO built successfully
Story: 2009101
Task: 44380
Signed-off-by: Matheus Machado Guilhermino <Matheus.MachadoGuilhermino@windriver.com>
Change-Id: I6738cee99337aab7c6aa669f60a5a134929ac5cf
In testing K8s 1.21.8 used less CPU than 1.21.3, so we are moving to
the newer version.
This has been booted in vbox and a basic pod has been started.
A full regression will be performed.
Depends-On: https://review.opendev.org/c/starlingx/compile/+/824802
Partial-Bug: 1957994
Signed-off-by: Chris Friesen <chris.friesen@windriver.com>
Change-Id: I64e4a64c90ef7591aeee52742dfcba9fdd8e5063
We now support multiple kubernetes versions,
and the common configuration/environment
files have been moved to a new package named
kubernetes-unversioned in CentOS
https://review.opendev.org/c/starlingx/integ/+/804243.
This commit will port kubernetes-unversioned to Debian.
- Did build-pkg
- Did build-img
- Verified if the package was installed correctly
- Verified the permissions of the installed files
Story: 2009101
Task: 44008
Change-Id: I65a9817d7f09736919453c0e81221f1fa1c590f5
Signed-off-by: Mihnea Saracin <Mihnea.Saracin@windriver.com>
dh clean
make: dh: No such file or directory
make: *** [debian/rules:4: clean] Error 127
And clean up the Lintian issues, also update
the debian_pkg_dirs
Test Plan: verify initramfs
Pass: successfully build initramfs
Pass: successfully boot using initramfs
Story: 2009221
Task: 43324
Signed-off-by: Yue Tao <yue.tao@windriver.com>
Change-Id: Ifc5fa4e0d5f7273df2e6b0859bc7b3babbb0cf6e
Dependencies:
- some upstream debian packages:
cherry-pick https://review.opendev.org/c/starlingx/tools/+/817042
debdownloader $MY_REPO_ROOT_DIR/stx-tools/debian-mirror-tools/config/debian/common/base-bullseye.lst
- golang 1.16.6
cherry-pick https://review.opendev.org/c/starlingx/compile/+/809321
add it to 'debian_pkg_dirs' in the compile folder
build-pkgs -p golang 1.16.6
Build-image dependencies:
- etcd
- runc
- containerd
Skipped the generation of the man pages, focused
only on building the package.
Did build-pkgs
Did build-iso
Story: 2009101
Task: 43945
Change-Id: I5024e65f8c84d7b5d57e2a47b060b6ef4416053a
Signed-off-by: Mihnea Saracin <Mihnea.Saracin@windriver.com>