CC: @RoyalOughtness maybe it's worth adding a service file (see: the PR link above) to secureblue, i
CC: @RoyalOughtness maybe it's worth adding a service file (see: the PR link above) to secureblue, idk
Tdo you know why we have this on bluefin?
Janything in blame?
T@M2 m2 shall be blamed for this
Awhat does that mean-
TANot sure if that'd be an issue tho, secureblue having this issue kinda suggest it is an upstream thing (or maybe it is a seperate issue with the same symptom 
)
)TOH im sorry this isnt related to what we are talking about
Tman even centos got that issue
Tits definitely something upstream
Aoh I'm srry
Tmaybe podman?
Tno idea.
Tdw
MOkay, I wonder if a version of distrobox volume mounted /etc/hostname
Mname of the offending distrobox replace fedora toolbox
RThe problem is only when a Distrobox was created when os-release hostname was present, then it was removed. Because the bind mounts no longer work
MRSo the real fix is finding what removes /etc/os-release /etc/hostname
M/etc/os-release is a symlink
Mthe error says cannot stat /etc/hostname
Ti do wonder like
Tdid we run into an ostree regression?
Tdoesnt seem like it
TGitHub
The previous change here was a no-op for two reasons:
It's actually usr/etc at this point
We were operating on the wrong rootfs
Fixes: 57bd0dc
It's actually usr/etc at this point
We were operating on the wrong rootfs
Fixes: 57bd0dc
JTHERE SHE IS!!!!!!!!!!!!!!
Tmaybe thats it?
Tthe changes seem a bit unrelated
Tbut man it would make a lot of sense for this thing to be a bootc regression
RSo the file was managed by bootc, then the file was removed from the images
Jtimeline matches
Jand we just got 1.1.7 recently everywhere
TYES.
JI remember reading the changelog with p5 in it. 
Jok is our workaround still valid?
Ti think so
RIMO it's not really a regression, but rather fixing something that shouldn't have been there in the first place.
But fixing that caused the issue
But fixing that caused the issue
RNew installs probably don't have this problem
Jalright then
Jlet's roll with this workaround
JLTS is a beta so no problemo there, once this merges I'll repush gts and stable and then we'll be done.
AT@j0rge
T@bsherman we can now default to systemd-resolved on bluefin LTS
Jwait what are we using now?
Tnetworkmanager's default resolv.conf thing
Joh
Jew
Tyes.
Ti hate it too
Tand it breaks tailscale
