libvirt: clusterstorage-controller reports unsupported platform

[dcritch]

Version

$ openshift-install version
unreleased-master-488-g27b9175c6f4076bd8ad19183f4fa53e2e7b1062e

Platform (aws|libvirt|openstack):

libvirt

What happened?

Attempting to install on libvirt results is not successful. The storage operator fails to initialise. Logs point to the clusterstorage-controller:

{"level":"info","ts":1551720561.785977,"logger":"controller_clusterstorage","msg":"Reconciling ConfigMap","Request.Namespace":"kube-system","Request.Name":"cluster-config-v1"}
{"level":"error","ts":1551720561.8227792,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"clusterstorage-controller","request":"kube-system/cluster-config-v1","error":"unsupported platform","stacktrace":"github.com/openshift/cluster-storage-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/openshift/cluster-storage-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215\ngithub.com/openshift/cluster-storage-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158\ngithub.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\ngithub.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134\ngithub.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until\n\t/go/src/github.com/openshift/cluster-storage-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

What you expected to happen?

Successful installation of OCP4 on libvirt

How to reproduce it (as minimally and precisely as possible)?

$ TAGS=libvirt hack/build.sh
$ ./bin/openshift-install  create cluster

[abhinavdahiya]

openshift/cluster-storage-operator#14 should have fixed the error.

[cynepco3hahue]

The problems still exist under the master, but I do not sure if openshift/cluster-storage-operator#14 fixed it
Under the cluster version, I can see

kubectl get clusterversion version -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterVersion
metadata:
  creationTimestamp: 2019-03-05T08:53:04Z
  generation: 1
  name: version
  resourceVersion: "22903"
  selfLink: /apis/config.openshift.io/v1/clusterversions/version
  uid: 16c146b7-3f24-11e9-86ea-52fdfc072182
spec:
  channel: fast
  clusterID: a2ecd131-1a88-443d-8bd6-c25c308eda55
  desiredUpdate: null
  upstream: https://api.openshift.com/api/upgrades_info/v1/graph
status:
  availableUpdates: null
  conditions:
  - lastTransitionTime: 2019-03-05T08:53:04Z
    status: "False"
    type: Available
  - lastTransitionTime: 2019-03-05T09:25:01Z
    message: Cluster operator storage is still updating
    reason: ClusterOperatorNotAvailable
    status: "True"
    type: Failing
  - lastTransitionTime: 2019-03-05T08:53:04Z
    message: 'Unable to apply 4.0.0-0.alpha-2019-03-05-054505: the cluster operator
      storage has not yet successfully rolled out'
    reason: ClusterOperatorNotAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: 2019-03-05T08:53:04Z
    message: 'Unable to retrieve available updates: unknown version 4.0.0-0.alpha-2019-03-05-054505'
    reason: RemoteFailed
    status: "False"
    type: RetrievedUpdates
  desired:
    image: registry.svc.ci.openshift.org/openshift/origin-release@sha256:2d8b4cd1969346e6165eb3226e4d573cd0722e3ee28b7b9ddd7e014fedf7183e
    version: 4.0.0-0.alpha-2019-03-05-054505
  history:
  - completionTime: null
    image: registry.svc.ci.openshift.org/openshift/origin-release@sha256:2d8b4cd1969346e6165eb3226e4d573cd0722e3ee28b7b9ddd7e014fedf7183e
    startedTime: 2019-03-05T08:53:04Z
    state: Partial
    version: 4.0.0-0.alpha-2019-03-05-054505
  observedGeneration: 1
  versionHash: WPvb9vOx4iw=

But I can see that storage operator is available

kubectl get clusteroperator -o 'custom-columns=name:metadata.name,status:status.conditions[*].status,type:status.conditions[*].type' | grep Available
cluster-autoscaler                    True,False,False           Available,Progressing,Failing
console                               False,True,False,Unknown   Failing,Progressing,Available,Upgradeable
dns                                   False,False,True           Failing,Progressing,Available
image-registry                        True,False,False           Available,Progressing,Failing
ingress                               False,False,True           Failing,Progressing,Available
kube-apiserver                        False,False,True,True      Failing,Progressing,Available,Upgradeable
kube-controller-manager               False,False,True,True      Failing,Progressing,Available,Upgradeable
kube-scheduler                        False,False,True,True      Failing,Progressing,Available,Upgradeable
machine-api                           False,True,False           Progressing,Available,Failing
machine-config                        True,False,False           Available,Progressing,Failing
marketplace-operator                  False,True,False           Progressing,Available,Failing
monitoring                            True,False,False           Available,Progressing,Failing
network                               False,False,True           Failing,Progressing,Available
node-tuning                           True,False,False           Available,Progressing,Failing
openshift-apiserver                   False,False,True,True      Failing,Progressing,Available,Upgradeable
openshift-authentication              False,False,True,Unknown   Failing,Progressing,Available,Upgradeable
openshift-cloud-credential-operator   False,False,True           Failing,Progressing,Available
openshift-controller-manager          False,False,True,Unknown   Failing,Progressing,Available,Upgradeable
openshift-samples                     True,False,False           Available,Progressing,Failing
operator-lifecycle-manager            False,False,True           Progressing,Failing,Available
service-ca                            False,False,True,True      Failing,Progressing,Available,Upgradeable
storage                               False,True,False           Progressing,Available,Failing

kubectl describe clusteroperator storage
Name:         storage
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  config.openshift.io/v1
Kind:         ClusterOperator
Metadata:
  Creation Timestamp:  2019-03-05T09:07:11Z
  Generation:          1
  Resource Version:    8814
  Self Link:           /apis/config.openshift.io/v1/clusteroperators/storage
  UID:                 0faf51a3-3f26-11e9-bc22-664f163f5f0f
Spec:
Status:
  Conditions:
    Last Transition Time:  2019-03-05T09:07:11Z
    Status:                False
    Type:                  Progressing
    Last Transition Time:  2019-03-05T09:07:11Z
    Message:               Unsupported platform for storageclass creation
    Status:                True
    Type:                  Available
    Last Transition Time:  2019-03-05T09:07:11Z
    Status:                False
    Type:                  Failing
  Extension:               <nil>
  Related Objects:         <nil>
  Versions:                <nil>
Events:                    <none>

[zeenix]

@cynepco3hahue is this still reproducible?

[cynepco3hahue]

@zeenix I did not see it under v0.16.1, do not aware regarding the master.

[zeenix]

@cynepco3hahue thanks. @abhinavdahiya let's close it then for now.

[abhinavdahiya]

/close

[openshift-ci-robot]

@abhinavdahiya: Closing this issue.

Details

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.