[14:34] <jsheeren> hi all, is there a way to detect if a cloud init has failed, besides polling the log?
[14:35] <rharper> jsheeren: yeah, /var/lib/cloud/data/{result,status}.json
[14:36] <smoser> jsheeren, and those are in /run/cloud-init/ also. i think thats probably preferred place as /var/lib/ could be stale
[14:37] <jsheeren> aha! thanks!
[14:42] <jsheeren> is there a config option somewhere where i can run a program when cloudinit fails?  or is it best to write some sort of daemon who polls the /var/lib/cloud/data/{result,status}.jso files?
[14:43] <rharper> I don't think there's any sort of run this on failure in cloud-init directly;
[14:44] <rharper> I suggest looking at using an inotify watch on those files to get a trigger when they're written
[14:45] <jsheeren> rharper: ok, thanks, i'm going to look into that
[14:47] <smoser> result will be written only once, and atomicly
[14:48] <smoser> but only if cloud-init-final ran
[14:48] <smoser> status is written with each stage.
[16:24] <smoser> rharper, https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/319943 woudl apprecate a review. it wont fix the root cause of bug 1671927 but it will fix something.
[16:30] <rharper> smoser: commented
[16:35] <powersj> magicalChicken: if I start working on the KVM code without some of your new branches, how much hurt will that be?
[16:50] <magicalChicken> powersj: the signature for some of the platform methods changed
[16:50] <magicalChicken> it would probably be best to just base it off the new integration-testing branch
[16:51] <powersj> magicalChicken: this one right? https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+ref/integration-testing
[16:51] <magicalChicken> powersj: also the image config format changed and the config handling changed, which would be an issue
[16:51] <magicalChicken> powersj: yeah
[16:52] <magicalChicken> if you want to start off of that, it should work out ok, i wont rebase again
[16:52] <powersj> so in terms of branches of yours we want to land there are 3? integration-testing, integration-testing-distor-features, and integration-testing-invocation-cleanup?
[16:52] <magicalChicken> integration-testing and integration-testing-invocation-cleanup are the two ready right now
[16:53] <magicalChicken> although i still need to rebase invocation-cleanup
[16:53] <magicalChicken> the distro-features one i'm still debugging some test failures on centos
[16:53] <powersj> ok
[16:53] <powersj> oh what about integration-testing-pylxd?
[16:53] <magicalChicken> oh, that one isn't needed, the pylxd fix is in the main integration-testing
[16:54] <powersj> ok
[16:54] <magicalChicken> i should probably delete that one
[16:54] <powersj> ok, so for now we need smoser to look at integration-testing
[16:55] <magicalChicken> yeah, that's the main thing right now
[16:56] <smoser>  /o\
[16:57] <powersj> is that the reverse of being excited? hands over ears?
[16:57] <magicalChicken> lol
[16:57] <smoser> is your commit message still all correct ?
[16:58] <smoser>    - when using 2.2 the test suite cannot complete large
[16:58] <smoser>      runs without hitting the pylxd too many open files
[16:58] <smoser>      issue, so 2.2 should only be used for development
[16:58] <magicalChicken> smoser: no, thanks for catching that, i hadn't updated the commit message at the top yet
[16:59] <smoser> magicalChicken, but you think that the commit series is sane as they are ?
[16:59] <smoser> ie, i'm ok to do a pull of mlutiple commits in a series here.
[16:59] <magicalChicken> yes, i think so
[16:59] <magicalChicken> i've gone through and rewritteen all the commit messages to make sense from outside the integration-testing dev branch
[17:00] <magicalChicken> and the commits in that series are all pretty well separated from each other
[17:00] <powersj> magicalChicken: why multiple tox entries? Do we really need the old one?
[17:01] <magicalChicken> powersj: i can pull it out
[17:01] <smoser> yeah, i'd drop that.
[17:01] <powersj> +1
[17:01] <magicalChicken> sure, one minute
[17:01] <smoser> and i'd drop support for 2.1 as it seems generally broken
[17:01] <smoser> right?
[17:02] <magicalChicken> smoser: yeah, it doesn't return command exit code which is pretty bad
[17:02] <smoser> if execute('/bin/false') blissfully goes on
[17:02] <smoser> do you have an reason for 'ignore_errors' rather than explicit values like subp ?
[17:03] <magicalChicken> smoser: i could do something more along the lines of subp
[17:03] <smoser> ignore_errors == subp(['/bin/false'], rcs=range(0, 256))
[17:03] <magicalChicken> yeah, that gives us some more control when we need to ignore errors
[17:04] <smoser> ie, if i want to just ignore anything, thats pretty easy to do with an explicit list of rcs
[17:04] <smoser> and  less surprises when somethign returned 14 and we only really expected 0 or 1
[17:04] <magicalChicken> currently the ignore errors is pretty much only used for the actual collect scripts. and i want to remove that eventually, but i haven't gone through all the collect scripts to see what the impact would be
[17:04] <smoser> dont worry about re-writing the commit message at the moment.
[17:05] <magicalChicken> ok
[17:05] <magicalChicken> i was going to rebase to pull out the tox env, do you want me to just add a new commit for it instead?
[18:08] <magicalChicken> smoser: i pushed commits to remove the tox env and switch to rcs=(0,1) for execute(), should be ready to go now
[18:08] <powersj> magicalChicken: thanks!
[18:09] <smoser> ok. i'll oook a bit mroe
[18:09] <magicalChicken> aah, it looks like i may have messed up a bit in the rcs 1, i'm going to amend that real quick
[18:10] <magicalChicken> should be good to go now, i messed up the change in collect and didn't catch it until one of the tests failed a collect script
[19:32] <smoser> rharper, https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+ref/feature/net-render-priority
[19:32] <smoser> that is the branch i have.
[19:32] <rharper> smoser: cool
[19:32] <smoser> but from cloudinit.net import render_factory
[19:33] <smoser> render_factory.select_renderer()
[19:43] <rharper> smoser: and in my branch, I'll insert the netplan stuff
[19:45] <smoser> ok. i have to run for a while, probaly check back in later tonight.
[19:45] <rharper> ok
[19:45] <rharper> I should have an update pushed with unittests
[21:26] <Odd_Bloke> smoser: Can I change the default username from {vendor,user}-data?  I still want my renamed user to get the default SSH keys etc.
[21:31] <Odd_Bloke> Aha, using "user:" rather than "users:" works.
[21:56] <dtp> hello again.  i'm having a problem similar to https://bugs.launchpad.net/cloud-init/+bug/1645597, but i'm on Openstack and ConfigDrive; should i log a new bug or just add on to this one?
[23:54] <rharper> smoser: ok, pushed v2 netconfig branch again, reasonable unittests for v2 rendering and other places;


[01:54] <Edgy2> Is anyone else getting a lot of "503 Service Unavailable" errors on Ubuntu Studio's website, or is it just me?
[02:29] <OvenWerks> Edgy2: I don't look at the web site very often, but it seems to be there just now.
[02:30] <flonxxd[m]>  I'll help 10 individuals how to earn $20,000 in just 72 hours  from the crypto market. But you will pay me 10% commission when you receive your profit. if interested send me a direct message via WhatsApp by asking me HOW for more details on how to get started
[02:30] <flonxxd[m]> > +1<PHONE_NUMBER>
[02:33] <arraybolt3[m]> flonxxd: Sorry, we don't like spam here.
[02:34] <OvenWerks> scams eityher
[02:34] <Edgy2> ok i'll stay around for updates.
[02:35] <Edgy2> !ops if that's a thing in this channel, crypto scam above
[02:35] <arraybolt3[m]> I think you gotta put it all by itself.
[02:35] <arraybolt3[m]> !ops
[02:35] <arraybolt3[m]> Crypto scam above.
[02:36] <arraybolt3[m]> Operators: flonxxd has posted a scam/spam message related to crypto.
[02:36] <Edgy2> thank you
[02:36] <OvenWerks> wow some of those names are pretty old
[02:37] <OvenWerks> only one looks like it may be valid within the past year
[02:37] <Edgy2> lol
[02:37] <arraybolt3[m]> OvenWerks: Hmm. Maybe Ubottu needs some help. I'll take it to #ubuntu-ops and see what they can do.
[02:38] <Edgy2> that channel serves #ubuntustudio too?
[02:38] <Edgy2> makes sense. anyways hopefully the site gets back up soon
[02:40] <arraybolt3[m]> Edgy2: Well, Ubuntu Studio is an official Ubuntu flavour, so I think they do. Could be wrong, guess we'll find out.
[02:40] <Eickmeyer> on it.
[02:40] <Edgy2> +++ thanks Eickmeyer
[02:40] <arraybolt3[m]> Eickmeyer: 👍
[02:41] <Eickmeyer> They got K-lined on libera, but that doesn't help matrix.
[02:41] <Eickmeyer> That !ops command is very out-of-date.
[02:41] <OvenWerks> :)
[02:42] <arraybolt3[m]> Based off of what Matrix looks like, I think they were only on Libera, so it shouldn't be a problem.
[02:42] <Edgy2> no idea how matrix works :D
[02:42] <OvenWerks> sounds like something from a movie
[02:43] <arraybolt3[m]> Edgy2: Think what would happen of IRC and iMessage had a baby.
[02:43] <arraybolt3[m]> That's Matrix.
[02:43] <arraybolt3[m]> s/of/if
[02:43] <arraybolt3[m]> Looks like Eickmeyer has even Matrix under control 👏
[02:44] <Eickmeyer[m]> Edgy2: Regarding the 503 on the Ubuntu Studio website, there's nothing we can do. Canonical hosts all of our infrastructure and they've been undergoing a data center move.
[02:44] <OvenWerks> knows who to talk to anyway.
[02:44] <Edgy2> ohh. that makes sense. good to know, thanks!
[02:45] <Eickmeyer[m]> Actually, for the Matrix side, I have full control when it comes to the Ubuntu Studio channels, much like on IRC.
[02:46] <Edgy2> is there no bot that can ban cross-platform? I own an irc network for a gaming network and a bot command in irc can ban in discord and vice versa
[02:46] <Edgy2> never integrated matrix though
[02:46] <Eickmeyer[m]> Only, on IRC, I'm merely an operator as delegated by the IRC Council.
[02:47] <Eickmeyer[m]> Edgy2: Afraid not, because while Libera Staff can K-line someone, the network-wide ban doesn't hit Matrix since it's a separate network.
[02:47] <Edgy2> i was thinking basically channel ban. if a bot were to be in matrix in addition to being on irc
[02:48] <arraybolt3[m]> Eickmeyer: We could code a bot that could take a username and a proof-of-identification signature and then be able to issue bans everywhere. It would take some work and getting a replay-attack-immune ID method might be a challenge, but it might work.
[02:49] <OvenWerks> This doesn't happen that often... and because their are not many working on things... lets use the time to make a better distro.
[02:49] <Eickmeyer[m]> arraybolt3: Unfortunately, that's not how the Matrix-IRC bridge works. It's quite a bit more complicated. IRC sees a username@ip-address, whereas matrix sees a unique identifier.
[02:49] <Eickmeyer[m]> But yeah, we don't see stuff like this often enough to worry about it.
[02:50] <arraybolt3[m]> OvenWerks, Eickmeyer: Good point, sorry for getting off topic. I'll stop being the spammer now LOL
[02:50] <Eickmeyer[m]> Another kicker: all Matrix on the IRC side are seen as the same IP address, so an IP-wide ban doesn't work well in that case. :)
[02:51] <Eickmeyer[m]> Anyhow, I need to get that !ops command fixed. 🤣
[02:51] <Edgy2> here's a good place to start: https://github.com/luk3yx/lurklite that bot's made by one of my network staff and supports being in both discord, matrix, and irc at the same time. you could add a little bit of code to that to get where you want
[02:52] <Edgy2> i only use the discord and irc part of it but it's part of pip3 and relies on miniirc
[02:52] <Edgy2> which is also on pip3
[02:52] <Eickmeyer> Edgy2: I appreciate the heart, but we're such small fries that it doesn't happen nearly often enough. That's the first time in the four years I've been involved that we've had to use the !ops command :)
[02:53] <Edgy2> loll, makes sense
[02:53] <arraybolt3[m]> Wow, and this is the second time I've used it in two months...
[02:54] <Eickmeyer[m]> arraybolt3: First time in this particular channel though, I'm sure.
[03:32] <Edgy2> website is back up
 "Wow, and this is the second time..." <- So you're the common denominator then. They're following you. 😜
[15:00] <BrianHechinger[m> Soaking of bots my discord bot is kicking my backside currently.
[15:00] <BrianHechinger[m> s/Soaking/speaking/
[18:38] <b[m]> "yeaa" supercool THIS is the first support chat button that landed in maaatriix ;) every day i talk to supports and tell them.. go in matrix... so this is a premier sup chat surprise 🥰   and sure a friendly "hello" to the group ++
[18:40] <b[m]> ..but of course, i have a "tiny" problem... is here anyone that have running ubuntu studio on a server with GPU nvidia ?!?
[18:41] <b[m]>  * 20.04
[18:41] <b[m]> ..but of course, i have a "tiny" problem... is here anyone that have running ubuntu studio on a server with GPU nvidia ?!?
[19:05] <tomreyn> b[m]: you can wait ans see whether someone has exactly the configuration you're asking about, or you can discuss the issue you're facing and see whether someone who does or doesn't have this exact configuration knows how to fix it. the latter would give you a much better chance of making progress.
[19:07] <b[m]> tomreyn: ...the hope die at last ... but waiting is also a pain .. i go crazy with this GPU server .. perhaps install windows-server is more easy..:/
[19:11] <tomreyn> b[m]: maybe this was too complicated, let me rephrase: i think you should just describe the issue. so far, you have not, so no one can help.
[19:11] <b[m]> * more easy..:/  by the way its a frsh new server with A4000 and only one app UE5.0.2 and it not find his GPU.. Google say`s its a GUI problem .. so i decide for the studio.. but its same..
[19:17] <tomreyn> b[m]: does lspci list it, though? and is the headless nvidia proprietary driver installed?
 "b: does lspci list it, though..." <- the server provider have now one week hands on this fresh server... also 2 friends... i the absolute windows user say the system not know anything about the nice GPU...   we was one time at the point that UE was starting but on CPU.. after installed CUDA openkernel and DLSS and nothing runs.. now i have no clue perhaps must do compile anything new or whatever... :(   so in "system" its still
[19:22] <b[m]> talking about 256bits graphics and if i do tiny bechmark for gpu it makes test on cpu .. BUT for me totally not to understand is "why a GUI can be the problem" .. but google say this allover...
[19:25] <tomreyn> i do not know what this would mean in terms of a grpahics card either. maybe what they mean is that the application does not support this hardware and environment.
[19:26] <b[m]> i have no clue.. two days ago thy installed a display dummy and say THIS is the solution...
[19:49] <tomreyn> this sounds like those managing the system for you should be seeking the support, not you
[19:51] <b[m]> normally YESS 100% right  but thy give also a lot of time in .. and sure this is a provider special for gpu servers... ... but under the line, i as gnome and indie garage production lost time and cash .. so i TRY to assist so good i can ... NO one thought before that a server install will bring so much pain ...
[20:00] <tomreyn> a cursory web search looks like the problem is with nvidia and their drivers.
[20:08] <tomreyn> b[m]: on a second look, all of those reports were old or referred to other situations, so i guess it should just work now - if firmwares are up to date and the hardware is fine, too.
[20:11] <b[m]> sounds cool so then i hope tomorrow any last round install compile and it will be run .. ;)
[20:12] <tomreyn> https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa has the latest drivers
[20:12] <tomreyn> but 510 series are in 22.04 proper
[20:13] <b[m]> so you think a dist-upgrade to 22.04 make sens for the gpu stuff?
[20:13] <tomreyn> maybe, maybe not, it's worth a try.
[20:14] <tomreyn> when it comes togeneral driver support #ubuntu may be the better place by the way
[20:14] <tomreyn> just because it's more busy and the foundation of all supported ubuntu flavors is the same
[20:15] <b[m]> problem is ALL is a try .. starts up with doc from UE with all time on top !! BETA and on BOTTOM oh docs are not for version 5.0 and we have newer so 5.0.2 = noo docs nothing .. and nvidia open kernel also no real hints and infos ..
[20:23] <tomreyn> it will be way too early for the open drivers
[20:23] <b[m]> aah OK ;) a good hint ++
[20:27] <tomreyn> and maybe not: it is listed as "compatible" on https://github.com/NVIDIA/open-gpu-kernel-modules (but then nvidia has shown to have a rather loose handle what is compatible and what is not in the past)
[20:30] <b[m]> ok i post all the new tips and infos links to the provider THANKS a LOT.. i come back if it runs ... ;)
[20:31] <tomreyn> i'm pretty clueless about nvidia really, chances are your support folks have a better understanding of it.
[20:34] <b[m]> i hope any day the open kernel will be have a big community and then of course it will be going fast forwards ...  UE is more for windows and nvidia also consumer mass stuff orientated...