!next

Meeting started at 2026-06-01 19:01:26 UTC

The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'

!chair @nirik:matrix.scrye.com, @phsmoura:fedora.im, @james:fedora.im

The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting

welcome!

Hy

Hey

morning

!next

Run `!ticket #<number>` for each ticket, discuss and classify. DON'T DO THIS FOR PRIVATE TICKETS.

!ticket 13376

● **Opened:** 3 days ago by frostyx

● **Assignee:** Not Assigned

● **Last Updated:** 6 hours ago

**infra/tickets #13376** (https://forge.fedoraproject.org/infra/tickets/issues/13376):**Zabbix monitoring for bugzilla2fedmsg**

yeah, I am not sure what more we need on this one...

low / 1 / day-to-day for now? or just leave it till tomorrow?

yeah, but i guess i would wait on greg if he closes it?

we can leave it for tomorrow

ok

!ticket 13379

● **Opened:** 3 hours ago by andersrh

**infra/tickets #13379** (https://forge.fedoraproject.org/infra/tickets/issues/13379):**[FAS] Request for SonicDE FAS group for Copr**

● **Last Updated:** Never

● **Assignee:** Not Assigned

1 / low / d2d?

+1

!ticket 13380

● **Opened:** 37 minutes ago by kevin

**infra/tickets #13380** (https://forge.fedoraproject.org/infra/tickets/issues/13380):**dist-git lookaside uploads fedora-messaging not functioning**

● **Assignee:** Not Assigned

● **Last Updated:** Never

yeah, I am hoping Aurélien B can look.

med / 3 (or 5) ?

3 for now?

sure)

sure

it might just be the missing user, but I am not sure.

that is all

!next

did you guys vote already? :)

I got sucked into a rabbit hole with that upload messaging issue. ;(

not yet, but it's on my list! :)

you should go (and you can vote for me!) :)

This week for me, helping with updates/reboots, looking at more rhel10 stuff, trying to catch up on old issues/pulls/etc

i was fixing OIDC for hosted weblate with Greg today

it was a missing slash at the end

Yeh, a bunch of things all mass update+reboot related ... Also a few stg vmhost machines came back up but didn't start their VMs.

so currently just waiting if they close the issue

but the login works there

James: odd. were they not marked as autostarted? ansible should do that...

Yeh, just did `virsh list --autostart` and they aren't ... so that explains that.

that can sometimes happen if an install run dies somewhere... because it does that marking after the install finishes and before it starts provisioning.

[root@vmhost-x86-01 ~][STG]#

4 ipa01.stg.rdu3.fedoraproject.org running

5 db03.stg.rdu3.fedoraproject.org running

6 db-fas01.stg.rdu3.fedoraproject.org running

7 db-datanommer01.stg.rdu3.fedoraproject.org running

[root@vmhost-x86-01 ~][STG]# virsh list --autostart

Id Name State

--------------------

```

I don't think it's that. Eg.

```

[root@vmhost-x86-01 ~][STG]# virsh list --all

Id Name State

------------------------------------------------------------

1 rabbitmq01.stg.rdu3.fedoraproject.org running

2 os-control01.stg.rdu3.fedoraproject.org running

3 ocp01.ocp.stg.rdu3.fedoraproject.org running

huh.

- name: Start the vm up and set it to autostart

virt: state=running name={{ inventory_hostname }} autostart=True

anyhow, easy to fix

Marking them as autostart by hand, and I'll make a note to check prod.

I don't think I have anything else off hand right now

i also don't have anything

Nothing here.

well, see you in #noc:fedoraproject.org!