#11833 Add yselkowitz to list to notify when ELN builds fail
Opened 10 months ago by sgallagh. Modified a month ago

Describe what you would like us to do:


Please add user @yselkowitz to the list of accounts in releng/failed-composes that receive an email notification when the ELN compose fails.

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


When convenient, but preferably by 2024-05-30


Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

10 months ago

Hello @sgallagh!

Thanks to Kevin of course, I got the maintainers file, where can update this so to confirm details here's the concerning PR [1] for this which adds user "Yaakov Selkowitz" with fas "yselkowitz";
Once, I have a +1 on that, we can merge it, and hopefully all good!

[1] https://pagure.io/fedora-kickstarts/pull-request/1029

Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops

10 months ago

Metadata Update from @jnsamyak:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

10 months ago

PR merged, this should be active now. ;)

Let us know if there's any problems with it.

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

10 months ago

I'm still not getting notifications.

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

6 months ago

This appears working now?

At least I see the right stuff in https://pagure.io/releng/failed-composes/issue/6788

Please reopen if there's still anything not right here.

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

5 months ago

@yselkowitz is still not getting notified when ELN composes fail. He reports that he got no email from https://pagure.io/releng/failed-composes/issue/7278

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

3 months ago

I think this might be due to eln changing it's compose id from ELN to eln.

See: https://pagure.io/releng/compose-tracker/blob/main/f/compose_tracker.py#_246

if we lower case that it migth work?

Composes are being detected as failed just fine (https://stg.pagure.io/releng/failed-composes/issue/4670 was opened last night for example), but @yselkowitz is not getting notified.

Ah yeah, the problem is in it's logic. It would currently only notify if there was a specific section that failed, but since thats not the case it doesn't do anything.

I'll see if I can find someone to fix it up.

Ah yeah, the problem is in it's logic. It would currently only notify if there was a specific section that failed, but since thats not the case it doesn't do anything.

I'll see if I can find someone to fix it up.

This is still broken. Can we get this looked at, please? I'm going to be transitioning to a new role in the new year and Yaakov will be taking over full-time responsibility for this.

I know what the problem is, happy to explain it to someone, but I don't have cycles to work on a fix right now...

will try and find someone to work on it.

If this works it's all Kevin's doing, if this fails blame me.

Prefixed with that, an attempt was made: https://pagure.io/releng/compose-tracker/pull-request/56

Unfortunately, both Fedora-eln-20241206.n.0 and Fedora-eln-20241206.n.1 failed today, but I did not receive any notification.

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog