=== lachesis_ is now known as lachesis
=== seednode3 is now known as seednode
=== bswinnerton9 is now known as bswinnerton
=== wCPO3 is now known as wCPO
=== hjensas_ is now known as hjensas
[12:10] <testcla234> hi , is possible to retrive the linux distro version with a special alias?
[12:10] <testcla234> same way as special alias "$RELEASE" .
[12:13] <wyoung> like buster-slim ?
[13:23] <oshoval> Hi, we are spinning a machine with cloud-init, installing some drivers / rpm, and then shutting it down, so once we spin it again we have the drivers / rpm installed already. I need also to add a fedora:fedora admin user to it, via the cloud-init, managed to add an additional user but didnt managed yet to update the default user in a manner that will be persistant even after i shutdown the VM and start it again, any tips or guide please
[13:23] <oshoval> ? thanks
[14:11] <chillysurfer> hey, all! could i get this pr re-opened? https://github.com/canonical/cloud-init/pull/780
[14:24] <Odd_Bloke> oshoval: What do you mean by "update the default user"?  Are you using this machine's disk as an image to launch other machines, or strictly booting it for a second time?
[14:24] <Odd_Bloke> chillysurfer: Done.
[14:24] <chillysurfer> thanks, Odd_Bloke !!
[14:48] <oshoval> Odd_Bloke: hope i am not mixing, we are customizing this img, and then run it to launch it again as "other machine" i think, customizing is using with the base image + cloud that was build using cloud-localds, this is the config we are using, and i am trying to update it in a way it will have fedora:fedora even after we shut it down. https://github.com/kubevirt/kubevirtci/blob/master/cluster-provision/images/vm-image-builder/fedora-srio
[14:48] <oshoval> v-lane/cloud-config
[14:48] <oshoval> link splitted - https://github.com/kubevirt/kubevirtci/blob/master/cluster-provision/images/vm-image-builder/fedora-sriov-lane/cloud-config
[14:49] <oshoval> tried to remove the sysprep, and tried to add "users" for the cloud-init, maybe i need to remove the password + chpasswd ?
[15:39] <Odd_Bloke> oshoval: So you're passing that config to the instance you're capturing, or to the instances you're launching from the image?
[15:39] <oshoval> Odd_Bloke - only to the instance i am capturing
[15:50] <Odd_Bloke> oshoval: Could you pastebin /var/log/cloud-init.log from an instance you've launched from the image?
[15:50] <oshoval> Odd_Bloke: sure sec please
[16:01] <oshoval> Odd_Bloke: https://pastebin.com/gPtD7x5m    this is the one with the exact cloud-init of the github, thanks
[16:02] <oshoval> this is from the "child" instances, after provisioning the VM, hope that what you asked
[16:03] <oshoval> (there was a sys-prep between, so it looks like the file is just from the fresh start)
[16:05] <oshoval> forgot to mention, that i am running it with this Cloud init userdata because else i dont have login:
[16:05] <oshoval>         userData: "#!/bin/bash\n\techo \"fedora\" |passwd fedora --stdin\n\techo "
[16:07] <oshoval> must drop now, thanks very much, will return next week, have a nice weekend
[17:15] <Odd_Bloke> OK, well, for reference, cloud-init is locking the default user's password in its default configuration.
=== ijohnson is now known as ijohnson|lunch
=== ijohnson|lunch is now known as ijohnson|groceri
=== seednode4 is now known as seednode
=== benj_- is now known as benj_
=== tds0 is now known as tds
=== paride2 is now known as paride
=== jmcgnh_ is now known as jmcgnh
=== apollo13_ is now known as apollo13
=== ijohnson|groceri is now known as ijohnson
[22:28] <testcla234> is there a way to avoid conflict package manager access ?
[22:29] <testcla234> when it boot there are some other process from azure to install extension  , due get the following error :
[22:29] <testcla234>  [ 78.912417] cloud-init[1470]: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)