<@phsmoura:fedora.im>
20:00:40
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
20:00:41
Meeting started at 2024-12-05 20:00:40 UTC
<@meetbot:fedora.im>
20:00:41
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@phsmoura:fedora.im>
20:00:45
!info meeting is 30 minutes MAX. At the end of 30, its stops
<@phsmoura:fedora.im>
20:00:45
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
20:00:45
!info agenda is at https://board.net/p/fedora-infra-daily
<@phsmoura:fedora.im>
20:00:45
!chair nirik smooge phsmoura
<@phsmoura:fedora.im>
20:00:45
<@phsmoura:fedora.im>
20:00:45
!info reminder: speak up if you want to work on a ticket!
<@meetbot:fedora.im>
20:00:46
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
20:00:52
hello
<@nirik:matrix.scrye.com>
20:01:50
morning
<@phsmoura:fedora.im>
20:04:36
no new issues today
<@phsmoura:fedora.im>
20:04:38
!topic Planning, Upcoming work and Open floor
<@nirik:matrix.scrye.com>
20:05:11
great. :)
<@nirik:matrix.scrye.com>
20:05:55
so for me, continuing to try and fix openshift stg cluster upgrade (I asked internally about it with no reply yet), then next on my list is finally trying to setup some riscv vm's...
<@nirik:matrix.scrye.com>
20:06:34
I might try and make a pass over tickets later today... I think we have some that can be closed...
<@nirik:matrix.scrye.com>
20:07:39
anyhow, anything else anyone would like to discuss? Happy to...
<@phsmoura:fedora.im>
20:09:58
nirik: still cant ping ipa servers at f41 test instance.. I added bastion and gateway to etc/hosts
<@nirik:matrix.scrye.com>
20:10:24
phsmoura: did you try the 'nmcli c up eth0' thing?
<@phsmoura:fedora.im>
20:10:34
ah it still didnt resolve bastion :/
<@phsmoura:fedora.im>
20:10:39
yes, I did
<@nirik:matrix.scrye.com>
20:10:54
huh, I can take a look...
<@nirik:matrix.scrye.com>
20:11:57
yeah, somehow dns is not right...
<@nirik:matrix.scrye.com>
20:12:04
look at output of 'resolvectl'
<@nirik:matrix.scrye.com>
20:12:11
DNS Domain: us-west-2.compute.internal
<@nirik:matrix.scrye.com>
20:12:50
I think you may have to manually fix it... with some resolvectl commands?
<@nirik:matrix.scrye.com>
20:13:41
or change it in NetworkManager with nm-tui or nm-cli might fix it too...
<@nirik:matrix.scrye.com>
20:14:21
I don't recall the resolvectl command to set domains search, but it should be: vpn.fedoraproject.org fedoraproject.org
<@phsmoura:fedora.im>
20:14:37
weird, f40 has the same config
<@nirik:matrix.scrye.com>
20:15:14
huh, yeah.
<@nirik:matrix.scrye.com>
20:15:26
so how did it work? it's always DNS
<@phsmoura:fedora.im>
20:17:13
I have no idea.. checked the config and theyare all the same
<@phsmoura:fedora.im>
20:17:31
in both f40 and f41
<@phsmoura:fedora.im>
20:18:13
but will change to vpn.fedoraproject.org fedoraproject.org
<@nirik:matrix.scrye.com>
20:18:20
hum, looking
<@nirik:matrix.scrye.com>
20:20:24
ok, yeah, it's dns... I got the vpn to come up by dropping the .fedoraproject.org from bastion01 in /etc/hosts...
<@nirik:matrix.scrye.com>
20:21:05
it was trying to lookup 'bastion-iad01.us-west-2.compute.internal' which didn't resolve
<@nirik:matrix.scrye.com>
20:21:53
So, yeah, I'd say, try and configure dns search and hopefully that would fix it.
<@phsmoura:fedora.im>
20:23:05
I dont have anything else
<@nirik:matrix.scrye.com>
20:23:20
me too either. :)
<@phsmoura:fedora.im>
20:23:49
ok, thanks nirik :)
<@phsmoura:fedora.im>
20:23:59
!endmeeting