Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prometheus when installed to the cluster should start and expose a secured proxy and unsecured metrics #17529

Closed
0xmichalis opened this issue Nov 30, 2017 · 8 comments
Assignees
Labels
area/tests component/metrics kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1

Comments

@0xmichalis
Copy link
Contributor

/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/prometheus/prometheus.go:117
Did not find tsdb_samples_appended_total, tsdb_head_samples_appended_total, or prometheus_tsdb_head_samples_appended_total in:
map[string]*io_prometheus_client.MetricFamily(nil),
Expected
    <bool>: false
to be true
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/prometheus/prometheus.go:83

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17516/test_pull_request_origin_extended_conformance_gce/12132/

@0xmichalis 0xmichalis added kind/test-flake Categorizes issue or PR as related to test flakes. area/tests priority/P1 labels Nov 30, 2017
@theute
Copy link

theute commented Feb 1, 2018

@oourfali it seems to be an installer issue rather than an issue in P8s itself ?

@zgalor
Copy link
Contributor

zgalor commented Feb 1, 2018

@Kargakis was prometheus installed using openshift-ansible?
what inventory file was used?

@0xmichalis
Copy link
Contributor Author

@zgalor this issue comes up in extended_gce. Unclear how Prometheus is installed in that job but I think openshift ansible is used.

cc: @smarterclayton

@smarterclayton
Copy link
Contributor

This is likely caused by #18317. This is the stock prometheus config in origin.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 3, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 2, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tests component/metrics kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1
Projects
None yet
Development

No branches or pull requests

8 participants