Message Tagging Service SOP

Contact Information


Factory2 Team, Fedora QA Team, Infrastructure Team


#fedora-qa, #fedora-admin


cqi, lucarval, vmaljulin

  • In OpenShift.


Tag module build


Message Tagging Service, aka MTS, is an event-driven microservice to tag a module build triggered by MBS specific event.

MTS basically listens on message bus for the MBS event Once a message is received, the module build represented by that message will be tested if it matches any predefined rules. Each rule definition has destination tag defined. If a rule matches the build, the destination tag will be applied to that build. Only module build in ready state is handled by MTS for now.

Observing Behavior

Login to as root (or, authenticate remotely with openshift using oc login, and run:

oc project mts
oc status -v
oc logs -f dc/mts


MTS does not use database.


Please do remember to increase MTS_CONFIG_VERSION so that Openshift creates a new pod after running the playbook.


You can roll out configuration changes by changing the files in roles/openshift-apps/message-tagging-service/ and running the playbooks/openshift-apps/message-tagging-service.yml playbook.


MTS docker image is built automatically and pushed to upstream By default, tag latest is applied to a fresh image. Tag stg is applied to image, then run the playbook playbooks/openshift-apps/message-tagging-service.yml with environment staging.


If everything works well, apply tag prod to docker image in, then, run the playbook with environment prod.

Update Rules

Rules file is managed along side the playbook role in same repository.

For detailed information of rules format, please refer to documentation under Modularity.


In case of problems with MTS, check the logs:

oc logs -f dc/mts