#11644 Error in `alertmanager.yml` while running openscanhub playbook
Closed: Fixed a year ago by svashisht. Opened a year ago by svashisht.

Describe what you would like us to do:


Running below command:

sudo rbac-playbook -l staging  openshift-apps/openscanhub.yml

ends with this error:

Thursday 23 November 2023  17:02:50 +0000 (0:00:00.067)       0:00:11.746 ***** 
fatal: [os-control01.stg.iad2.fedoraproject.org]: FAILED! => {"changed": true, "cmd": "oc -n openscanhub apply --validate=strict -f /etc/openshift_apps/openscanhub/alertmanager.yml", "delta": "0:00:00.459606", "end": "2023-11-23 17:02:51.152992", "msg": "non-zero return code", "rc": 1, "start": "2023-11-23 17:02:50.693386", "stderr": "Error from server (BadRequest): error when creating \"/etc/openshift_apps/openscanhub/alertmanager.yml\": AlertmanagerConfig in version \"v1beta1\" cannot be handled as a AlertmanagerConfig: strict decoding error: unknown field \"spec.route.repeat_interval\"", "stderr_lines": ["Error from server (BadRequest): error when creating \"/etc/openshift_apps/openscanhub/alertmanager.yml\": AlertmanagerConfig in version \"v1beta1\" cannot be handled as a AlertmanagerConfig: strict decoding error: unknown field \"spec.route.repeat_interval\""], "stdout": "", "stdout_lines": []}

which means that the repeat_interval field does not exist in the AlertmanagerConfig.

When do you need this to be done by? (YYYY/MM/DD)


asap


Possible fix: https://pagure.io/fedora-infra/ansible/pull-request/1665

I have not tested this change, so please test before merging.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

a year ago

Hi @svashisht , merged your PR, and ran the playbook, seemed to go through this time, can you check this is resolved now?

I am able to run playbooks on both staging and production.

Metadata Update from @svashisht:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog