starlingx/k8s-cni-sriov container image reports RHEL7.6 as OS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Steven Webster |
Bug Description
Brief Description
-----------------
The starlingx/
Starlingx doesn't modify the k8s-cni-sriov image. It's built so that it can be locked down on a specific SHA (to align on the code base that was tested).
The upstream docker file is used by starlingx:
$ cat k8s-cni-
BUILDER=docker
LABEL=k8s-cni-sriov
DOCKER_REPO=https:/
DOCKER_
https:/
So the build is using this as the Dockerfile:
https:/
This file is what’s defining the base.
A more recent baseline of this repo appears to have the default image build based on alpine, with RHEL7 as a secondary option.
Severity
--------
This is not a functional issue. It's a licensing issue.
Steps to Reproduce
------------------
Query the OS version in the starlingx/
Expected Behavior
------------------
Only opensource licenses are used in components used by starlingx
Actual Behavior
----------------
The above image is based on enterprise source code.
Reproducibility
---------------
Reproducible
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
master 2019-09-13
Last Pass
---------
This has been an issue since the introduction of the starlingx/
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Other
description: | updated |
Changed in starlingx: | |
assignee: | nobody → Steven Webster (swebster-wr) |
Marking as gating / high priority given this is a licensing issue. Given this is an issue in stx.2.0, the fix should be considered for cherry-picking to that release as well. Need assessment from the developer that this is possible with reasonable effort (confirm the new version of the codebase providing an alpine build will be functionally compatible with the stx.2.0 code base)