Bug 1889275
Summary: | The sctp validation phase fails if there is at least one machine config configured with no raw config (i.e. machine configs containing only kernel arguments) | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yurii Prokulevych <yprokule> | |
Component: | CNF Platform Validation | Assignee: | Federico Paolinelli <fpaoline> | |
Status: | CLOSED ERRATA | QA Contact: | Nikita <nkononov> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.6 | CC: | aos-bugs, fpaoline, omarzian, tradej | |
Target Milestone: | --- | |||
Target Release: | 4.7.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
Cause:
Any machine config configured with no raw config makes the sctp validation step fail.
Consequence:
The validation step fails.
Workaround (if any):
Delete the offending machine config, change it with a dummy config value or skip the sctp tests using the ginkgo.skip parameter.
Result:
|
Story Points: | --- | |
Clone Of: | ||||
: | 1889276 (view as bug list) | Environment: | ||
Last Closed: | 2021-09-28 10:28:04 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1889276, 1889744 |
Description
Yurii Prokulevych
2020-10-19 08:54:17 UTC
The offending MC is apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"machineconfiguration.openshift.io/v1","kind":"MachineConfig","metadata":{"annotations":{},"labels":{"machineconfiguration.openshift.io/role":"worker-lb"},"name":"99-worker-lb-disable-smt"},"spec":{"kernelArguments":["nosmt"]}} creationTimestamp: "2020-10-12T07:50:13Z" generation: 1 labels: machineconfiguration.openshift.io/role: worker-lb managedFields: - apiVersion: machineconfiguration.openshift.io/v1 fieldsType: FieldsV1 fieldsV1: f:metadata: f:annotations: .: {} f:kubectl.kubernetes.io/last-applied-configuration: {} f:labels: .: {} f:machineconfiguration.openshift.io/role: {} f:spec: .: {} f:kernelArguments: {} manager: kubectl-client-side-apply operation: Update time: "2020-10-12T07:50:13Z" name: 99-worker-lb-disable-smt resourceVersion: "1390127" selfLink: /apis/machineconfiguration.openshift.io/v1/machineconfigs/99-worker-lb-disable-smt uid: 93e2faa6-64b1-468f-8b81-a2b51ceb0cbb spec: kernelArguments: - nosmt This happens if the cluster has (at least) one machine config with no config section. I tested with a machine config like the one in Federico's comment(a machine config with no config in spec other than kernelArguments) Bug is Verified and is not reproducible anymore Technical Details: ------------------ CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.7.0-1 IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs Client Version: 4.6.0-202005061824-29e9a33 Server Version: 4.6.0-rc.4 Kubernetes Version: v1.19.0+d59ce34 |