<@phsmoura:fedora.im>
19:03:17
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:03:18
Meeting started at 2024-02-05 19:03:17 UTC
<@meetbot:fedora.im>
19:03:18
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@leo:fedora.im>
19:03:23
!hi
<@zodbot:fedora.im>
19:03:23
Leo Puvilland (leo) - he / him / his
<@phsmoura:fedora.im>
19:03:26
!chair nirik smooge phsmoura
<@nirik:matrix.scrye.com>
19:03:35
oh right, was distracted again. ;)
<@phsmoura:fedora.im>
19:03:35
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@nirik:matrix.scrye.com>
19:03:37
!hi
<@zodbot:fedora.im>
19:03:38
Kevin Fenzi (kevin) - he / him / his
<@phsmoura:fedora.im>
19:03:43
hello
<@phsmoura:fedora.im>
19:03:52
!info meeting is 30 minutes MAX. At the end of 30, its stops
!info agenda is at https://board.net/p/fedora-infra-daily
!info reminder: speak up if you want to work on a ticket!
<@phsmoura:fedora.im>
19:03:59
!topic Tickets needing review
<@phsmoura:fedora.im>
19:04:07
!info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
<@phsmoura:fedora.im>
19:04:28
!ticket 11754
<@zodbot:fedora.im>
19:04:28
**fedora-infrastructure #11754** (https://pagure.io/fedora-infrastructure/issue/11754):**Planned Outage - server updates - 2024-02-07 22:00 UTC**
● **Opened:** 2 hours ago by kevin
● **Last Updated:** 27 minutes ago
● **Assignee:** kevin
<@nirik:matrix.scrye.com>
19:04:47
If someone(s) could review this and make sure I didn't make any typos/date errors that would be great...
<@nirik:matrix.scrye.com>
19:04:50
then I can send it.
<@nirik:matrix.scrye.com>
19:04:57
med med outage
<@aheath1992:matrix.org>
19:05:09
!hi
<@zodbot:fedora.im>
19:05:12
Andrew Heath (aheath1992)
<@smooge:fedora.im>
19:05:39
There will be an outage starting at 2024-0207 22:00UTC,
<@smooge:fedora.im>
19:05:45
missed a -
<@smooge:fedora.im>
19:06:48
also "Most services will be affected for a short time, but end user facing services (mirrorlists, websites) should not be affected." if the DB servers are down, won't that affect websites
<@smooge:fedora.im>
19:06:54
aka wiki
<@nirik:matrix.scrye.com>
19:07:10
no on websites, they do not use any database .
<@nirik:matrix.scrye.com>
19:07:18
wiki yes.
<@smooge:fedora.im>
19:07:33
ok that was all I could see. better than my usual one
<@smooge:fedora.im>
19:07:44
all in the same century and times
<@nirik:matrix.scrye.com>
19:08:14
fixed missing -... thanks!
<@phsmoura:fedora.im>
19:08:38
!ticket 11755
<@zodbot:fedora.im>
19:08:38
**fedora-infrastructure #11755** (https://pagure.io/fedora-infrastructure/issue/11755):**vmhost-x86-copr02 hardware issues**
● **Opened:** an hour ago by kevin
● **Last Updated:** Never
● **Assignee:** kevin
<@nirik:matrix.scrye.com>
19:09:27
med med ops... I will try and get dell to respond again later today.
<@phsmoura:fedora.im>
19:10:04
ok, moving to releng
<@phsmoura:fedora.im>
19:10:05
!info https://pagure.io/releng/issues?status=Open
<@phsmoura:fedora.im>
19:10:29
!11929
<@phsmoura:fedora.im>
19:10:43
!releng 11929
<@zodbot:fedora.im>
19:10:43
**releng #11929** (https://pagure.io/releng/issue/11929):**No space left on s390x builder**
● **Opened:** 2 days ago by qulogic
● **Last Updated:** 2 days ago
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
19:11:09
We can close this I guess. I need to file a bug on dnf5 for not cleaning up it's caches... or it might be koji / dnf5...
<@smooge:fedora.im>
19:12:00
I wonder if it is a separate setting to clean up dnf cache with 5
<@phsmoura:fedora.im>
19:12:10
Do you want to close it nirik ?
<@nirik:matrix.scrye.com>
19:13:10
I can...
<@phsmoura:fedora.im>
19:14:29
!releng 11930
<@zodbot:fedora.im>
19:14:30
**releng #11930** (https://pagure.io/releng/issue/11930):**f40 repo broken**
● **Opened:** a day ago by raveit65
● **Last Updated:** a day ago
● **Assignee:** Not Assigned
<@phsmoura:fedora.im>
19:15:40
is it upstream?
<@nirik:matrix.scrye.com>
19:16:32
yes, close it upstream is my vote
<@phsmoura:fedora.im>
19:17:48
closing.. waiting pagure to respond
<@phsmoura:fedora.im>
19:18:03
!releng 11932
<@zodbot:fedora.im>
19:18:04
**releng #11932** (https://pagure.io/releng/issue/11932):**dozens of f39 builds mis-tagged, getting ejected from f39-stable bodhi pushes**
● **Opened:** 7 hours ago by decathorpe
● **Last Updated:** an hour ago
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
19:18:59
med med ops... we need to sort out tagging on them.
<@phsmoura:fedora.im>
19:20:55
!releng 11933
<@zodbot:fedora.im>
19:20:56
**releng #11933** (https://pagure.io/releng/issue/11933):**python-hiredis accidentally had tar ball added to git on new import package**
● **Opened:** 2 hours ago by pwouters
● **Last Updated:** Never
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
19:21:34
low low ops... we have a script to deal with this I think... (moves the thing to a archive branch)
<@phsmoura:fedora.im>
19:22:42
!topic Planning, Upcoming work and Open floor
<@phsmoura:fedora.im>
19:22:49
anything for open floor?
<@phsmoura:fedora.im>
19:24:53
Im having troble with ocp stg routes from planet disappeared and now I cant see project status it has a TypeError page. Also, doing a research few places point to a bug in ocp? If any of you know what I did wrong otherwise I can hit fedora noc...
<@phsmoura:fedora.im>
19:25:08
Im having troble with ocp stg. Routes from planet disappeared and now I cant see project status it has a TypeError page. Also, doing a research few places point to a bug in ocp? If any of you know what I did wrong otherwise I can hit fedora noc...
<@phsmoura:fedora.im>
19:25:25
Im having troble with ocp stg. Routes from planet disappeared and now I cant see project status. It has a TypeError page. Also, doing a research few places point to a bug in ocp? If any of you know what I did wrong otherwise I can hit fedora noc...
<@nirik:matrix.scrye.com>
19:25:38
I have... a lot this week: update koji in stg, mass update/reboots, upgrade builders to f39 probibly, test new sigul again, mailman staging deployment, new s390x builder lpars install, install 4 new aarch64 boxes, reinstall abunch of other aarch64 boxes, and enable kiwi in first stg and then prod. ;)
<@nirik:matrix.scrye.com>
19:26:06
huh, not sure. I can look... the default route should always be there I thought?
<@leo:fedora.im>
19:26:33
not much from me...
<@nirik:matrix.scrye.com>
19:28:01
hey leo... if you have some time I have a thing you could poke at... the sha1 dnssec zones... we sign a bunch of zones, but they don't have DS records, so it's pointless... could you look at a patch that just removes signing from those zones?
<@leo:fedora.im>
19:28:16
yeah, will take a look
<@nirik:matrix.scrye.com>
19:29:13
that would be great... thanks.
<@phsmoura:fedora.im>
19:29:39
nirik: yes, it was there before. I think this started after the update.. not sure tho.. just remember seeing update warnings
<@nirik:matrix.scrye.com>
19:31:16
phsmoura: huh, so the route you setup we need to add in dns... planet.stg.fedoraproject.org doesn't resolve... but the default one... planet.apps.ocp.stg.fedoraproject.org should work, but it's saying unavailable...
<@nirik:matrix.scrye.com>
19:31:46
oh weird. it's stuck in 'containercreating'
<@phsmoura:fedora.im>
19:32:06
yep
<@nirik:matrix.scrye.com>
19:32:25
ah, it's complaining about the krb volume
<@nirik:matrix.scrye.com>
19:32:33
look at 'events' in the web interface.
<@phsmoura:fedora.im>
19:33:10
there is that issue as well, but the name in configmap and deployment is the same
<@phsmoura:fedora.im>
19:33:30
maybe we can continue in fedora noc?
<@nirik:matrix.scrye.com>
19:35:24
sure, I think there's something wrong with naming... but I think this is the entire problem, the container never comes up because of it.
<@nirik:matrix.scrye.com>
19:35:35
nothing else from me and we are over time.
<@phsmoura:fedora.im>
19:36:23
Thanks everyone
<@phsmoura:fedora.im>
19:36:24
!endmeeting