I suspect it is because your oc is outdated.

Here's mine:

oc v1.5.0-alpha.0+3b2bbe5
kubernetes v1.4.0+776c994
features: Basic-Auth

Server https://192.168.1.15:8443
openshift v1.5.0-alpha.0+3b2bbe5
kubernetes v1.4.0+776c994

H-Metrics: 0.21.5.Final

----- Original Message -----
> [theute@localhost vertx-opentracing]$ oc version
> oc v1.3.1
> kubernetes v1.3.0+52492b4
> features: Basic-Auth GSSAPI Kerberos SPNEGO
>
> Server https://10.202.9.50:8443
> openshift v1.5.0-alpha.1+9e682de-55
> kubernetes v1.4.0+776c994
>
>
> and Hawkular Metrics 0.21.5.Final
>
> Thomas
>
> On Wed, Jan 11, 2017 at 3:20 PM, Matt Wringe <mwringe@redhat.com> wrote:
>
> > ----- Original Message -----
> > > From: "John Mazzitelli" <mazz@redhat.com>
> > > To: "Discussions around Hawkular development" <
> > hawkular-dev@lists.jboss.org>
> > > Sent: Wednesday, 11 January, 2017 8:52:59 AM
> > > Subject: Re: [Hawkular-dev] Hawkular in OpenShift
> > >
> > > > When I use:
> > > > oc cluster up --metrics=true
> > > >
> > > > Hawkular metrics fails until I do:
> > > > oc adm policy add-role-to-user view
> > > > system:serviceaccount:openshift-infra:hawkular -n openshift-infra
> > > >
> > > > Should that last command be part of the --metrics=true magic ?
> > >
> > >
> > > I do not have to do that. But then, I'm running from a local master
> > build so
> > > I have the latest-n-greatest - maybe you have an older version?
> >
> > I suspect you are using an older version of 'oc'. Can you let us know
> > which version you are using? And can you also let us know what version the
> > Hawkular Metrics docker image is?
> >
> > If its a released version of 'oc' it should only ever use a versioned
> > Hawkular Metrics which matches the version of OpenShift.
> >
> >
> > >
> > > I know when I do "cluster up" I usually have to wait a bit for metrics to
> > > fully start and only then do I see metrics in the UI (sometimes this
> > takes a
> > > few minutes on a slow machine). And before its ready, I get a warning
> > > message at the top of the UI and it only goes away until metrics is ready
> > > AND I browse to the metrics status page.
> > >
> > > I do, however, give my "admin" user full cluster-admin rights just so I
> > can
> > > see everything when I log into the UI:
> > >
> > >    $ oc adm policy add-cluster-role-to-user cluster-admin admin
> > >
> > > For the record, I have a script I use to run "cluster up" - I don't just
> > run
> > > it "oc cluster up --metrics". There are other things that have to be
> > done to
> > > make sure it all works (at least that's been my experience - mainly, I
> > have
> > > to turn off firewalld) - this is what I use:
> > >
> > > https://github.com/hawkular/hawkular-openshift-agent/blob/
> > master/hack/cluster-openshift.sh
> > >
> > > This also has a convenient "status" option so I can get a few status
> > things
> > > and it has "down" which also does some other things to clean up in
> > addition
> > > to
> > > "oc cluster down"
> > > _______________________________________________
> > > hawkular-dev mailing list
> > > hawkular-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
>