<@phsmoura:fedora.im>
19:00:40
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:00:41
Meeting started at 2024-07-08 19:00:40 UTC
<@meetbot:fedora.im>
19:00:41
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@phsmoura:fedora.im>
19:00:44
!info reminder: speak up if you want to work on a ticket!
<@phsmoura:fedora.im>
19:00:44
!chair nirik smooge phsmoura
<@phsmoura:fedora.im>
19:00:44
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
19:00:44
!info meeting is 30 minutes MAX. At the end of 30, its stops
<@phsmoura:fedora.im>
19:00:44
!info agenda is at https://board.net/p/fedora-infra-daily
<@meetbot:fedora.im>
19:00:45
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
19:00:54
hello
<@smooge:fedora.im>
19:01:42
hi phsmoura
<@smooge:fedora.im>
19:01:59
there is an outage problem with pagure.io currently.
<@phsmoura:fedora.im>
19:03:20
is it related with a message you metioned in noc? Sorry, I just saw it before this meeting
<@smooge:fedora.im>
19:03:33
it is
<@phsmoura:fedora.im>
19:04:04
I can access pagure tho and status is showing only the planned outage tomorrow
<@phsmoura:fedora.im>
19:04:21
how can I help with this?
<@smooge:fedora.im>
19:05:18
well currently not much. the updated routes have been pushed to the internet so most places can get to pagure again. Some people can't log in to pagure and others just get a blank page
<@smooge:fedora.im>
19:07:06
at the moment, it would need to see if someone could ssh into pagure.io and see what might be the problem but that might ened sysadmin-main and root ssh from batcave to work
<@phsmoura:fedora.im>
19:10:10
I think I have perms
<@phsmoura:fedora.im>
19:10:35
we have only 1 issue to review
<@phsmoura:fedora.im>
19:10:43
lets do that and talk in open floor
<@phsmoura:fedora.im>
19:11:07
!topic Tickets needing review
<@phsmoura:fedora.im>
19:11:47
!ticket 12041
<@zodbot:fedora.im>
19:11:48
● **Assignee:** kevin
<@zodbot:fedora.im>
19:11:48
**fedora-infrastructure #12041** (https://pagure.io/fedora-infrastructure/issue/12041):**Planned Outage - Server updates/reboots - 2024-07-10 21:00 UTC**
<@zodbot:fedora.im>
19:11:48
<@zodbot:fedora.im>
19:11:48
● **Opened:** a day ago by kevin
<@zodbot:fedora.im>
19:11:48
● **Last Updated:** Never
<@phsmoura:fedora.im>
19:12:03
med med ops outage
<@smooge:fedora.im>
19:12:10
+1
<@phsmoura:fedora.im>
19:14:06
I can access it but its taking time to respond
<@phsmoura:fedora.im>
19:14:16
!topic Planning, Upcoming work and Open floor
<@phsmoura:fedora.im>
19:14:27
just ssh to it
<@phsmoura:fedora.im>
19:15:04
waiting to respond..
<@smooge:fedora.im>
19:15:36
ok if you get a $ or # prompt then its time to see what uptime says
<@phsmoura:fedora.im>
19:18:08
Stephen J Smoogen: up 8 days, 20:27, 1 user, load average: 0.97, 1.41, 1.57
<@smooge:fedora.im>
19:18:34
ok for something so slow that doesn't sound right
<@smooge:fedora.im>
19:19:17
could you try some `host proxy01.fedoraproject.org` and `host proxy01.vpn.fedoraproject.org` to see if those work?
<@phsmoura:fedora.im>
19:20:59
no it doesnt. timed out, servers couldnt be reached
<@smooge:fedora.im>
19:21:28
ok what does /etc/resolv.conf say ( I think that is what is used on the box unless its using systemd stuff)
<@phsmoura:fedora.im>
19:22:11
nameserver 8.8.8.8
<@phsmoura:fedora.im>
19:22:11
```
<@phsmoura:fedora.im>
19:22:11
nameserver 1.0.0.1
<@phsmoura:fedora.im>
19:22:11
```
<@phsmoura:fedora.im>
19:22:11
search vpn.fedoraproject.org fedoraproject.org
<@smooge:fedora.im>
19:23:16
ok also try `resolvectl status` in case it is not using that
<@smooge:fedora.im>
19:23:35
but could you see if `traceroute -n 8.8.8.8` stops somewhere?
<@smooge:fedora.im>
19:24:33
and thanks phsmoura
<@phsmoura:fedora.im>
19:25:41
np, lets continue on noc
<@phsmoura:fedora.im>
19:26:05
!endmeeting