Installer: Unable to retrieve available updates: unexpected HTTP status: 404 Not Found

[davivcgarcia]

Version?

$ ./openshift-install version
./openshift-install v0.6.0
Terraform v0.11.10

Platform?

AWS

What happened?

In a fresh install on AWS, the cluster is not able to retrieve Red Hat CoreOS updates, leading to an error in the interface:

In the command line we see:

[fedora@ip-10-0-0-94 auth]$ oc describe clusterversions --all-namespaces
Name:         version
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  config.openshift.io/v1
Kind:         ClusterVersion
Metadata:
  Creation Timestamp:  2018-12-11T00:36:16Z
  Generation:          1
  Resource Version:    9099
  Self Link:           /apis/config.openshift.io/v1/clusterversions/version
  UID:                 c4eda596-fcdc-11e8-acfe-0293e13bf75c
Spec:
  Channel:     fast
  Cluster ID:  22dfa834-742a-4157-8352-8fb76f620c19
  Overrides:
    Kind:       APIService
    Name:       v1alpha1.packages.apps.redhat.com
    Unmanaged:  true
  Upstream:     http://localhost:8080/graph
Status:
  Available Updates:  <nil>
  Conditions:
    Last Transition Time:  2018-12-11T00:43:34Z
    Message:               Done applying 0.0.1-2018-12-08-172651
    Status:                True
    Type:                  Available
    Last Transition Time:  2018-12-11T00:43:34Z
    Status:                False
    Type:                  Failing
    Last Transition Time:  2018-12-11T00:43:34Z
    Message:               Cluster version is 0.0.1-2018-12-08-172651
    Status:                False
    Type:                  Progressing
    Last Transition Time:  2018-12-11T00:36:34Z
    Message:               Unable to retrieve available updates: unexpected HTTP status: 404 Not Found
    Reason:                RemoteFailed
    Status:                False
    Type:                  RetrievedUpdates
  Current:
    Payload:     quay.io/openshift-release-dev/ocp-release@sha256:4f02d5c7183360a519a7c7dbe601f58123c9867cd5721ae503072ae62920575b
    Version:     0.0.1-2018-12-08-172651
  Generation:    1
  Version Hash:  sfP4jQcd4Zg=
Events:          <none>

What you expected to happen?

The cluster should be able to check for updates.

[crawford]

This is expected (for now). We haven't yet exposed the update infrastructure publicly. Let's leave this open until that is actually enabled.

[davivcgarcia]

@crawford thanks for the feedback! Just out of curiosity, what is the timeframe for that?

[wking]

I don't know if we have a committed timeframe for this. But we'll post to this issue when there's a pull-request somewhere to look at ;).

[jatanmalde]

I am seeing the same issue on the cluster I deployed.

[root@localhost testing]# ./openshift-install version
./openshift-install v0.7.0
[root@localhost testing]# ./oc version
oc v4.0.0-0.79.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

This is expected (for now). We haven't yet exposed the update infrastructure publicly. Let's leave this open until that is actually enabled.

As per this, once the updates are publically exposed, the tab should go? How could I debug more into the clusterversion operator.

Thanks.

[eparis]

It is possible now to pick a different channel.