add the telemetry to the default list of dataplane-operator services #392
Conversation
|
This depends on PR openstack-k8s-operators/edpm-ansible#312 to merge. |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/8151a725b11c4c99bf51ebdcda9723d0 ✔️ dataplane-operator-docs-preview SUCCESS in 1m 48s |
|
/hold We are holding dataplane-operator PRs until the CI stabilizes after merging #303. The /hold will be dropped here once all PRs are in to support 303. |
|
/unhold rdoproject.org/github-check jobs should be passing now. |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/03dd263239eb4553942872acce19798a ✔️ dataplane-operator-docs-preview SUCCESS in 1m 47s |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/38b3d45e31294dcbb040cb8ccc65ce9f ✔️ dataplane-operator-docs-preview SUCCESS in 1m 48s |
|
The CI failure here needs to be fixed, I think it's on the edpm-ansible side. [pod/dataplane-deployment-telemetry-openstack-edpm-kfgz7/openstackansibleee] �[0;31mfailed: [edpm-compute-0] (item={'src': '/var/lib/config-data/merged/ceilometer.conf', 'dest': '/var/lib/openstack/config/ceilometer/ceilometer.conf'}) => {"ansible_loop_var": "item", "changed": false, "item": {"dest": "/var/lib/openstack/config/ceilometer/ceilometer.conf", "src": "/var/lib/config-data/merged/ceilometer.conf"}, "msg": "Could not find or access '/var/lib/config-data/merged/ceilometer.conf' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}�[0m |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/5bd7dc26000a4a06b8054cef891e49da ✔️ dataplane-operator-docs-preview SUCCESS in 1m 47s |
jlarriba
force-pushed
the
telemetry-service
branch
from
c843e22 to
eeb25b1
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/4947d2d7daa9431b96b778e69e9d1d53 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 56s |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/caa4f45fea9b43688662baf2b9ec3e29 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 37m 08s |
jlarriba
force-pushed
the
telemetry-service
branch
from
7d75a69 to
34bfad7
Compare
jlarriba
force-pushed
the
telemetry-service
branch
from
34bfad7 to
a28cb5b
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fao89, jlarriba The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/01b7e7af94244616a6926669a2e2fad1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 20s |
|
The error is: Could not find or access '/var/lib/openstack/config/telemetry/polling.yaml' on the Ansible Controller While the polling.yaml file is mounted in /var/lib/openstack/configs/telemetry/polling.yaml. Small typo, look at the config vs configs. I have submitted the appropiate fix to edpm_ansible: https://github.com/openstack-k8s-operators/edpm-ansible/pull/368/files |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/4b225abc1d8b45b2a938a04a9cdf9a34 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 36m 42s |
|
recheck Looks like openstack-k8s-operators/edpm-ansible#368 has been merged. |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/d0682813f64b406092c91edd240cd616 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 28s |
|
Indeed, working on it. The fix: openstack-k8s-operators/edpm-ansible#370 |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/46b5127b19494ab2b378883157247c2e ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 44m 43s |
|
Working on the error |
|
podman_containers is presenting a strange behaviour when executed in ansibleEE containers. This fails because node_exporter is not being created. According to the logs: As we can see, it is running a podman rm -f node_exporter and then a creation. When I run the same playbook using standalone ansible, the podman rm does not happen and the container is happily created. As we are in the verge of DP2, I have submitted a PR (openstack-k8s-operators/edpm-ansible#372) to edpm_ansible to replace the usage of podman_containers and use command instead until we can figure out what configuration in ansibleEE is making this behave differently. |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/3cfbc8b733a24c0f8a1b3194449933a1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 04m 53s |
|
This is still broken. Now, with the new code to just create node_exporter, the log says: How is it possible that node_exporter container is already running if we have not deployed it before? Is the test also testing ansible idempotence? However, I created a new PR on edpm_ansible to achieve the playbook idempotence: openstack-k8s-operators/edpm-ansible#377 |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/5566923735714adda98a99c5c8094185 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 01s |
|
recheck |
openshift-merge-robot
merged commit d032d41
into
openstack-k8s-operators:main
No description provided.