Bug 1809282
Summary: | Missing properties in Etcd OpenSpec API | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jason Boxman <jboxman> |
Component: | Etcd Operator | Assignee: | Dan Mace <dmace> |
Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | dmace, mfojtik, rpattath, skolicha |
Target Milestone: | --- | Keywords: | UpcomingSprint |
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Missing properties in etcd spec
Consequence: The command `oc explain etcd` doesn't list properties typically seen with specs.
Fix: Fill out the CRD to describe the properties.
Result: The explain command fully describes the properities of etcd.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:17:25 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
Jason Boxman
2020-03-02 19:04:07 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing severity from "medium" to "low". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Hi, this is still an issue in 4.4.3, assuming we want output for `oc explain`. ``` oc explain Etcd KIND: Etcd VERSION: operator.openshift.io/v1 DESCRIPTION: <empty> ``` ``` oc version Client Version: 4.4.3 Server Version: 4.4.3 Kubernetes Version: v1.17.1 ``` I’m adding UpcomingSprint, because the team occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. We will revisit this bug next sprint. I think the CRD[1] probably needs moved to openshift/api and cleaned up. This would include adding the preserveUnknownFields property. [1] https://github.com/openshift/cluster-etcd-operator/blob/master/manifests/0000_12_etcd-operator_01_config.crd.yaml # oc get clusterversions.config.openshift.io NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-26-112702 True False 78m Cluster version is 4.5.0-0.nightly-2020-05-26-112702 # oc explain Etcd KIND: Etcd VERSION: operator.openshift.io/v1 DESCRIPTION: Etcd provides information to configure an operator to manage kube-apiserver. 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> -required- status <Object> 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:2409 This comment was flagged a spam, view the edit history to see the original text if required. |