[stable/prometheus-operator] Prometheus Pod does not start with the right containers in the prometheus pod

[dennisotugo]

Is this a request for help?:
Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report

Version of Helm and Kubernetes:
Helm Version: v2.12.1

Kubernetes Version: v1.11.6

Which chart:
Prometheus-Operator

What happened:
The chart installs but it does not install config-reload and ruler in the Prometheus pod and the pod is not properly named, instead it is named "monitoring-prometheus-oper-operator-7cdb599b77-d7pgs" instead of "prometheus-monitoring-prometheus-oper-prometheus-0".
As a result of this, prometheus does not have any config and does not work, also port forwarding does not work but instead results in an error

E0113 11:26:27.327797   30476 portforward.go:331] an error occurred forwarding 9090 -> 9090: error forwarding port 9090 to pod a2962c6b52c5356f0dc81d33d0095f06d88fcffe0aa87b2a824e59508a9a1d23, uid : exit status 1: 2019/01/13 10:26:27 socat[4973] E connect(5, AF=2 127.0.0.1:9090, 16): Connection refused

What you expected to happen:
For it to install normally with the proper containers in the pod and with the proper naming convention

How to reproduce it (as minimally and precisely as possible):
Install the chart on a new cluster

Anything else we need to know:
I am getting

==> v1/Pod(related)
NAME                                                  READY  STATUS             RESTARTS  AGE
monitoring-prometheus-node-exporter-8465l             0/1    Running            0      4s
monitoring-prometheus-node-exporter-9vfxf             0/1    Running            0      4s
monitoring-prometheus-node-exporter-bckb6             1/1    Running            0      4s
monitoring-prometheus-node-exporter-fxg9c             0/1    Running            0      4s
monitoring-prometheus-node-exporter-nlsw9             0/1    Running            0      4s
monitoring-prometheus-node-exporter-wscmd             0/1    Running            0      4s
monitoring-prometheus-node-exporter-wv2mn             0/1    Running            0      4s
monitoring-grafana-64c7b764db-c8kfh                   0/3    ContainerCreating  0      4s
monitoring-kube-state-metrics-6bd59ffc4d-sx9h6        0/1    Running            0      4s
monitoring-prometheus-oper-operator-7cdb599b77-vbxcv  1/1    Running            0      4s

Instead of

NAME                                                   READY     STATUS    RESTARTS   AGE
alertmanager-prom-prometheus-operator-alertmanager-0   2/2       Running   0          10m
prom-grafana-6c7c9cf8fc-szkpv                          3/3       Running   0          10m
prom-kube-state-metrics-5648859669-lwxmr               1/1       Running   0          10m
prom-prometheus-node-exporter-2896z                    1/1       Running   0          10m
prom-prometheus-node-exporter-2dwcv                    1/1       Running   0          10m
prom-prometheus-node-exporter-6fk24                    1/1       Running   0          10m
prom-prometheus-node-exporter-9kwvh                    1/1       Running   0          10m
prom-prometheus-node-exporter-9w6bc                    1/1       Running   0          10m
prom-prometheus-node-exporter-g9v4v                    1/1       Running   0          10m
prom-prometheus-node-exporter-jqpjk                    1/1       Running   0          10m
prom-prometheus-node-exporter-ph2xz                    1/1       Running   0          10m
prom-prometheus-node-exporter-q46bn                    1/1       Running   0          10m
prom-prometheus-node-exporter-tfdzs                    1/1       Running   0          10m
prom-prometheus-operator-operator-6d645ff4d6-lkc98     1/1       Running   0          10m
prometheus-prom-prometheus-operator-prometheus-0       3/3       Running   1          10m

[dennisotugo]

It just started working for no apparent reason

[briantopping]

@dennisotugo If you are all set, might be good to close this :)

[vsliouniaev]

monitoring-prometheus-oper-operator-7cdb599b77-vbxcv is a prometheus operator pod, not a prometheus pod. You could check the logs from there to find out if the prometheus is being used to create a statefulset properly

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.