fedora-infrastructure

#12808 Disable RabbitMQ queue osci-pipelines-queue-6
Closed: Fixed by zlopez. Opened by lecris.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

The queue is used in dist-git-trigger/pull-request job (see also jenkins page). However, that queue is not actually used doing anything right now, and as I look back in datagrepper to find any message that it would be checking there is none

$ http get https://apps.fedoraproject.org/datagrepper/v2/search    delta==1814400    category==bodhi   topic=="org.fedoraproject.prod.buildsys.task.state.change"
{
    "arguments": {
        "agents": [],
        "categories": [
            "bodhi"
        ],
        "contains": [],
        "delta": 1814400.0,
        "end": 1758279863.988569,
        "meta": [],
        "not_agents": [],
        "not_categories": [],
        "not_packages": [],
        "not_topics": [],
        "not_users": [],
        "order": "desc",
        "packages": [],
        "page": 1,
        "rows_per_page": 25,
        "start": 1756465463.988569,
        "topics": [
            "org.fedoraproject.prod.buildsys.task.state.change"
        ],
        "users": []
    },
    "count": 0,
    "pages": 0,
    "raw_messages": [],
    "total": 0
}

Reading the implementation it is supposed to be listening to events of PR scratch-builds finishing, but those are already covered in more detail here. So I would like to instead move forward to decommissioning this queue

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

Not urgent, but how do we coordinate? Do I disable the Jenkins job first and when the queue is disabled everything left in there is dropped, or do we do it the other way around?

Not urgent, but how do we coordinate? Do I disable the Jenkins job first and when the queue is disabled everything left in there is dropped, or do we do it the other way around?

Correct, when no consumer is reading from this queue I can delete it server-side.

Metadata Update from @abompard:
- Issue assigned to abompard

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

Metadata Update from @abompard:
- Issue tagged with: rabbitmq

The consumer was dropped so I went and deleted it. :)

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

Issue status updated to: Open (was: Closed)

Metadata Update from @zlopez:
- Issue tagged with: sprint-0

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

Metadata Update from @zlopez:
- Issue untagged with: sprint-0
Metadata

low-trouble medium-gain ops rabbitmq

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.