dustymabe changed the topic of #fedora-coreos to: Fedora CoreOS :: Find out more at https://getfedora.org/coreos/ :: Logs at https://libera.irclog.whitequark.org/fedora-coreos
gursewak has quit [*.net *.split]
jlebon has quit [*.net *.split]
mock has quit [*.net *.split]
misuto has quit [*.net *.split]
misuto has joined #fedora-coreos
gursewak has joined #fedora-coreos
michele has quit [Remote host closed the connection]
bgilbert has quit [Remote host closed the connection]
bgilbert_ has joined #fedora-coreos
michele has joined #fedora-coreos
jlebon has joined #fedora-coreos
plarsen has quit [Quit: NullPointerException!]
mheon has quit [Ping timeout: 244 seconds]
stephan has quit [Ping timeout: 268 seconds]
stephanepoq has joined #fedora-coreos
bytehackr has joined #fedora-coreos
paragan has joined #fedora-coreos
arnulfo_7 has quit [Read error: Connection reset by peer]
arnulfo_7 has joined #fedora-coreos
arnulfo_7 has quit [Changing host]
arnulfo_7 has joined #fedora-coreos
bytehackr has quit [Ping timeout: 255 seconds]
bytehackr has joined #fedora-coreos
paragan has quit [Ping timeout: 252 seconds]
paragan has joined #fedora-coreos
gursewak has quit [Ping timeout: 248 seconds]
plundra has quit [Remote host closed the connection]
plundra has joined #fedora-coreos
bgilbert_ has quit [Ping timeout: 248 seconds]
gursewak has joined #fedora-coreos
jcajka has joined #fedora-coreos
jpn has joined #fedora-coreos
gursewak has quit [Ping timeout: 260 seconds]
c4rt0 has joined #fedora-coreos
wolfshappen has quit [Ping timeout: 248 seconds]
wolfshappen has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
bytehackr has quit [Ping timeout: 255 seconds]
wolfshappen has quit [Client Quit]
wolfshappen has joined #fedora-coreos
jpn has joined #fedora-coreos
bytehackr has joined #fedora-coreos
Betal has quit [Quit: WeeChat 3.6]
arnulfo_7 has quit [Read error: Connection reset by peer]
arnulfo_7 has joined #fedora-coreos
arnulfo_7 has quit [Changing host]
arnulfo_7 has joined #fedora-coreos
vgoyal has joined #fedora-coreos
crobinso has joined #fedora-coreos
mockgeek has joined #fedora-coreos
mockgeek is now known as mock
jpn has quit [Ping timeout: 260 seconds]
nalind has joined #fedora-coreos
plarsen has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
ravanelli has joined #fedora-coreos
jpn has joined #fedora-coreos
crobinso has quit [Read error: Connection reset by peer]
arnulfo_7 has quit [Read error: Connection reset by peer]
mheon has joined #fedora-coreos
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
<dustymabe> jlebon: we DO need to download the `ostree` artifact here, correct? https://github.com/coreos/fedora-coreos-pipeline/blob/main/jobs/kola-aws.Jenkinsfile#L68
<dustymabe> is that for the upgrade test?
nbsadminaccount- has joined #fedora-coreos
dustymabe has quit [Quit: WeeChat 3.5]
dustymabe has joined #fedora-coreos
<jlebon> dustymabe: yeah, exactly. we start from the old AMI, upload the ostree, then rebase
<jlebon> dustymabe: can you restamp https://github.com/coreos/coreos-assembler/pull/3042 ?
<dustymabe> jlebon: i'm working on adding "image upload" support to our aws/gcp kola jenkins tests
<dustymabe> similar to what is done today for azure/openstack
<dustymabe> it will enable us to start testing rawhide/branched without leaving AMIs permanently in the account
<jlebon> i wouldn't mind uploading AMIs for those... if we had GC. i think gursewak recently started looking at that again.
<dustymabe> yeah
<dustymabe> maybe I shouldn't go down this path
ravanelli has quit [Remote host closed the connection]
<dustymabe> let's just enable it anyway?
<dustymabe> I kind of want to get some indication of how healthy they are on the cloud platforms
<jlebon> i guess branched is ok because it's temporarily enabled
<jlebon> wow, testing-devel is up to 994 builds. soon to hit the 1k milestone!
<dustymabe> 💯
<dustymabe> 💯0
<walters> dustymabe: one thing related to this, with https://github.com/coreos/coreos-assembler/pull/3004 we can test the non-firstboot tests without disk images
<dustymabe> walters: that does seem interesting.. highly test dependent, though. A lot of our tests are firstboot tests, right?
<dustymabe> i was thinking - it would be really nice if we were able to apply oscontainers in the initrd (before real root switch)
<dustymabe> similar to our open ticket about package layering in the initrd
<dustymabe> I honestly think this would cut down on some "derivative projects" need to build "bootimages" for their offering
<jlebon> if we do one, we could probably do the other since both involve calling rpm-ostree from the initrd
<dustymabe> exactly
<jlebon> dustymabe: did you see my msg higher up about restamp ?
<dustymabe> jlebon: nope
<walters> without a mechanism to apply configuration to the initramfs (repo files, TLS certificates, mirroring) that can't work
<dustymabe> jlebon: my bouncer went down (new FCOS update - woohoo!)
<dustymabe> let me check the logs
<dustymabe> ok I see it now
<jlebon> walters: i was thinking we'd chroot, not run in the the initrd userspace
<dustymabe> jlebon: stamped
<jlebon> we do that for a few things today
<jlebon> dustymabe: thanks!
<dustymabe> walters: thanks for the `--oscontainer` link - i might try to play around with it
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 268 seconds]
ravanelli has joined #fedora-coreos
aaradhak[m] has joined #fedora-coreos
jcajka has quit [Quit: Leaving]
<dustymabe> hey aaradhak[m] - according to https://bugzilla.redhat.com/show_bug.cgi?id=2080043#c19 the issue is at least fixed in rawhide - so we can validate the test you wrote (on testing-devel the test should fail and on rawhide it should pass)
<aaradhak[m]> HI dustymabe : I will need to work on writing the test case for checking the existence of /etc/issue.d/22_clhm_ens6.issue. If it is required to be verified manually in the meantime, I shall look into it.
<dustymabe> not required to be verified manually
<dustymabe> thanks aaradhak[m]
<walters> who has the perms to execute on https://github.com/coreos/fedora-coreos-tracker/issues/1256 again?
<dustymabe> I don't think I do
<jlebon> walters: cverna should be able to
<travier[m]> Colin Walters: We have a procedure for that in the internal repo :)
<walters> ok right I'd seen that but couldn't find it. A bit odd to document public GH repository ops in an internal repo, but eh
<walters> btw there's https://url.corp.redhat.com/ for sending internal URLs across public media
<walters> it seems though this does still then go to cverna - will give him a bit to see/reply
<travier[m]> Agree that it's weird but it references internal resources to update
<travier[m]> we could probably move some of it externaly
u1106 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
paragan has quit [Quit: Leaving]
u1106 has joined #fedora-coreos
jbrooks has joined #fedora-coreos
<dustymabe> aaradhak davdunc dustymabe gursewak jaimelm jbrooks jcajka jdoss jlebon jmarrero lorbus miabbott nasirhm ravanelli saqali skunkerk walters
<dustymabe> FCOS community meeting in #fedora-meeting-1
<dustymabe> If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt
aaradhak has joined #fedora-coreos
bgilbert_ has joined #fedora-coreos
bgilbert_ is now known as bgilbert
jpn has quit [Ping timeout: 255 seconds]
crobinso has joined #fedora-coreos
gursewak has joined #fedora-coreos
guesswhat has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
<guesswhat> hello, question, how can i use https://coreos.github.io/afterburn/usage/attributes/#metadata-attributes in ignition ? thanks
bytehackr has quit [Ping timeout: 255 seconds]
jpn has joined #fedora-coreos
<dustymabe> guesswhat: hmm. I'm not sure that information is available at the time Ignition runs
jpn has quit [Ping timeout: 260 seconds]
<bgilbert> guesswhat: you can use Ignition to write out systemd units that use the metadata attributes
<bgilbert> but Ignition doesn't itself know about the attributes
<jlebon> bgilbert: could we detect a previously installed CoreOS on firstboot with extra partitions and error out if it'll get wiped? that would break another set of reprovisioning users, but at least we err on the side of data loss prevention.
<jlebon> s/it'll/the extra partitions will/
<bgilbert> on firstboot? if we're in the reprovisioning case, coreos-installer has already wiped the partition table by then
<guesswhat> bgilbert: write out systemd unit ? do we have any example? thanks
<bgilbert> guesswhat: well, that's exciting. looks like we never documented this in FCOS docs
<bgilbert> guesswhat: the (brief) instructions at the top of https://coreos.github.io/afterburn/usage/attributes/ may be all we have right now
ravanelli has joined #fedora-coreos
<jlebon> bgilbert: was thinking about live env, but right yeah. coreos-installer would have to also purposely break for this where it didn't before
<bgilbert> jlebon: yup
jpn has joined #fedora-coreos
<jlebon> i guess one hack is to put the old partition table in a file in /boot and the first boot code analyzes that too
<dustymabe> bgilbert: we never documented "write out systemd unit" example ?
<jlebon> anyway, just brainstorming here. i feel like we should be able to find a path forward where we do require user changes without risking data loss.
<bgilbert> I'm in favor of that if we can think of a path, but there are some fundamental constraints here
<dustymabe> bgilbert: jlebon: I think this is what I was alluding to when I said it would be useful to enumerate the cases and identify ones where data loss could occur during a reprovision
<bgilbert> the whole point of a user data partition is that we shouldn't decide later that it's actually ours
ravanelli has quit [Ping timeout: 268 seconds]
<bgilbert> dustymabe: I'm open to that, sure
<dustymabe> i.e. we can talk through the specific contstraints in each scenario and thus maybe come up with a possible solution that accounts for them
<guesswhat> bgilbert: oh, afterburn is disabled by default, /run/metadata/afterburn env file is okish for me :) thanks
<bgilbert> guesswhat: +1
<dustymabe> we document how to write and run a systemd service in the tutorial: https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-services/
<jlebon> dustymabe: yeah, i think that'd be a useful exercise
* jlebon goes for food
jpn has quit [Ping timeout: 268 seconds]
* dustymabe also goes for food
guesswhat has quit [Quit: Leaving]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
agners has joined #fedora-coreos
ravanelli has joined #fedora-coreos
<dustymabe> MichaelArmijo[m]: any updates that need to be made to https://github.com/coreos/fedora-coreos-streams/blob/main/RELEASE.md ?
jpn has joined #fedora-coreos
<MichaelArmijo[m]> dustymabe: yes, just 1. I'll open a PR.
jpn has quit [Ping timeout: 248 seconds]
<MichaelArmijo[m]> I just opened https://github.com/coreos/fedora-coreos-streams/pull/554/files to update the jenkins URL
<dustymabe> jlebon: ravanelli: review ^^
jpn has joined #fedora-coreos
aaradhak has quit [Quit: Connection closed for inactivity]
<jlebon> merged! thanks MichaelArmijo[m] for doing the releases!
<MichaelArmijo[m]> jlebon: Of course! Thanks.
<lorbus> Hey team, is there an ETA for the next rpm-ostree release cut? Having support for `ex module` in a container is needed for our story to migrate OKD/FCOS over to layered images.
<dustymabe> not that I know of
<jlebon> yeah, i'd say we're overdue at this point. i think walters may do one soon for other layering-related things.
nalind has quit [Quit: bye]
ravanelli has quit [Remote host closed the connection]
<lorbus> thanks, that sounds promising :)
jpn has quit [Quit: Lost terminal]
ravanelli has joined #fedora-coreos
ravanelli has quit [Ping timeout: 260 seconds]
c4rt0 has quit [Ping timeout: 260 seconds]
crobinso has quit [Remote host closed the connection]
mheon has quit [Ping timeout: 268 seconds]
bgilbert has quit [Ping timeout: 268 seconds]