Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1769468

Summary:	tuned does not have proper oc explain output
Product:	OpenShift Container Platform	Reporter:	Simon <skordas>
Component:	Node Tuning Operator	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED ERRATA	QA Contact:	Simon <skordas>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	sejug, tbuskey
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-23 11:11:16 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:

Description Simon 2019-11-06 17:00:50 UTC

Description of problem:
Regarding to https://bugzilla.redhat.com/show_bug.cgi?id=1754640

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-02-092336

How reproducible:
100%

Steps to Reproduce:
1.
$ oc explain tuneds.tuned.openshift.io 


Actual results:
KIND:     Tuned
VERSION:  tuned.openshift.io/v1

DESCRIPTION:
     <empty>


Expected results:
oc explain command should return proper description.


Additional info:

Comment 4 Jiří Mencák 2019-11-08 09:07:56 UTC

Fixed in 4.3.0-0.nightly-2019-11-08-015817

$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.3.0-0.nightly-2019-11-08-015817 True False 35m Cluster version is 4.3.0-0.nightly-2019-11-08-015817

$ oc explain tuned
KIND: Tuned
VERSION: tuned.openshift.io/v1

DESCRIPTION:
Tuned is a collection of rules that allows cluster-wide deployment of
node-level sysctls and more flexibility to add custom tuning specified by
user needs. These rules are translated and passed to all containerized
tuned daemons running in the cluster in the format that the daemons
understand. The responsibility for applying the node-level tuning then lies
with the containerized tuned daemons. More info:
https://github.com/openshift/cluster-node-tuning-operator

FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

metadata <Object>
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

spec <Object>
spec is the specification of the desired behavior of Tuned. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status

status <map[string]>
Status is the current state of Tuned. This cannot be overriden.

Comment 5 Tom Buskey 2019-11-15 15:44:21 UTC

Marking verified in comment 4 with cluster version 4.3.0-0.nightly-2019-11-13-233341

Comment 7 errata-xmlrpc 2020-01-23 11:11:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062