#9714 Restart the ftbfs bugzilla spam cron and/or help me debug it
Closed: Fixed 3 years ago by churchyard. Opened 3 years ago by churchyard.

  • Describe the issue

I've updated the ftbfs spam cron script config in https://pagure.io/fedora-infra/ansible/pull-request/206#request_diff

The script is:

https://pagure.io/fedora-infra/ansible/blob/master/f/roles/releng/files/ftbfs.cron
https://pagure.io/fedora-infra/ansible/blob/master/f/roles/releng/files/ftbfs.sh

But so far there have been no reminders. I believe they should have happened already.

Could you please help me debug this problem?

  • When do you need this? this or next week

  • When is this no longer needed or useful? when it starts working or when all F33FTBF bugzillas are fixed :)

  • If we cannot complete your request, what is the impact? packagers won't be reminded about the problem and many packages will get retired before F34 branching.


Issue status updated to: Open (was: Closed)

3 years ago

The problem was the playbook wan't run after the change.

I just ran the playbook and it updated the config. We should be good.

Closing the ticket, if you find any issues, please reopen.

Thanks.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
- Issue tagged with: groomed, medium-gain, medium-trouble, ops

3 years ago

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

3 years ago

Right, that seems obvious now. Will try to remember to (ask you to) do it the next time.

There were supposed to be comments happening on Sunday, but they didn't :(

I have no idea how to see what's wrong.

Metadata Update from @churchyard:
- Issue status updated to: Open (was: Closed)

3 years ago

Usually what we do for releng scripts is set a MAILTO=releng-cron@lists.fedoraproject.org and then the output goes to that list and everyone can look at it.

But in this case I can't find any output...

it ran:

Sep 13 04:22:01 compose-x86-01.iad2.fedoraproject.org su[235315]: (to ftbfs) root on none
Sep 13 04:22:01 compose-x86-01.iad2.fedoraproject.org su[235315]: pam_unix(su-l:session): session opened for user ftbfs by (uid=0)
Sep 13 04:22:02 compose-x86-01.iad2.fedoraproject.org su[235315]: pam_unix(su-l:session): session closed for user ftbfs
Sep 13 04:22:02 compose-x86-01.iad2.fedoraproject.org run-parts[235362]: (/etc/cron.weekly) finished ftbfs.cron

perhaps it exited due to:

Only run every third week, see https://pagure.io/releng/issue/8915

test $(($(date +%W | sed s.^0..) % 3)) -eq 0 || exit 0

?

$(date +%W | sed s.^0..) % 3 was 0 this Sunday. If not, it must have been 0 some Sunday since this was deployed 21 days ago.

Can you see the logs from the last 3 runs?

Nope, I can't see any logs. ;(

Shall I try running it manually?

and/or should we add a MAILTO=releng-cron@lists.fedoraproject.org to the cron file?

It might be not outputting anything to stdout, only stderr?

I'd run the script manually but I prefer the comments to be from the RelEng Bugzilla account.

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

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done