-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.14
-
No
-
False
-
Description of problem:
MachineSet/Machine missing after enabling featuregate
Version-Release number of selected component (if applicable):
4.14.0-rc.2,4.14.0-rc.5
How reproducible:
100%
Steps to Reproduce:
1. Enable featureset: ~~~ $ oc edit featuregate cluster apiVersion: config.openshift.io/v1 kind: FeatureGate metadata: name: cluster # ... spec: featureSet: TechPreviewNoUpgrade ~~~ 2. Create a machineset for VSphereStaticIP ~~~ cat machineset.yaml apiVersion: machine.openshift.io/v1beta1 kind: MachineSet metadata: labels: machine.openshift.io/cluster-api-cluster: babbar-8xqnx name: dpateriy-machineset namespace: openshift-machine-api spec: replicas: 1 selector: matchLabels: machine.openshift.io/cluster-api-cluster: babbar-8xqnx machine.openshift.io/cluster-api-machineset: babbar-8xqnx-worker template: metadata: creationTimestamp: null labels: machine.openshift.io/cluster-api-cluster: babbar-8xqnx machine.openshift.io/cluster-api-machine-role: worker machine.openshift.io/cluster-api-machine-type: worker machine.openshift.io/cluster-api-machineset: babbar-8xqnx-worker spec: metadata: creationTimestamp: null labels: node-role.kubernetes.io/worker: "" providerSpec: value: apiVersion: vsphereprovider.openshift.io/v1beta1 credentialsSecret: name: vsphere-cloud-credentials diskGiB: 120 kind: VSphereMachineProviderSpec memoryMiB: 8192 metadata: creationTimestamp: null network: devices: - networkName: "xxxxxx" numCPUs: 4 numCoresPerSocket: 1 snapshot: "" template: <name> userDataSecret: name: worker-user-data workspace: datacenter: xxxx datastore: xxxxx folder: "xxxxx" server: xxxxx $ oc apply -f machineset.yaml machineset.machine.openshift.io/dpateriy-machineset created ~~~ 3. After a while, check machines/machineset ~~~ [root@bastion ocp414]# oc get machines -A No resources found [root@bastion ocp414]# oc get machineset -A No resources found ~~~
Actual results:
Machines/Machineset is not getting displayed.
Expected results:
Machines/Machineset should get displayed
Additional info:
Featuregate enablement creates conflict with same resourcename. $ oc api-resources | grep -iE 'machines|machineset' machines ma cluster.x-k8s.io/v1beta1 true Machine machinesets ms cluster.x-k8s.io/v1beta1 true MachineSet machines machine.openshift.io/v1beta1 true Machine machinesets machine.openshift.io/v1beta1 true MachineSet
Running below command works: $ oc get machineset.machine.openshift.io -A NAMESPACE NAME DESIRED CURRENT READY AVAILABLE AGE openshift-machine-api dpateriy-machineset 1 1 75m openshift-machine-api worker-machineset 1 1 86m $ oc get machines.machine.openshift.io -A NAMESPACE NAME PHASE TYPE REGION ZONE AGE openshift-machine-api dpateriy-machineset-sgl4h Provisioned 76m openshift-machine-api worker-machineset-wsb7v Provisioned 86m
