[07:32] <BlackDex> I created a backup of the maas database because of some trouble. But i see that it is arround 900MB's in size. Are there some ways to clean it before creating a backup?
[13:02] <kiko> BlackDex, most of that is images, which MAAS can resync
[13:03] <BlackDex> the database?
[13:04] <BlackDex> i excluded '/var/lib/maas/boot-resources'
[13:04] <BlackDex> i mean the postgre database
[13:06] <BlackDex> i mean, i can for instance do without the machine events etc..
[14:54] <mup> Bug #1680917 changed: Machine fails to boot if MAAS server is not available <curtin:New> <MAAS:Invalid by blake-rouse> <https://launchpad.net/bugs/1680917>
[14:54] <mup> Bug #1686669 changed: MAAS fails to deploy Ubuntu on host that had CentOS deployed and vice-versa <curtin:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1686669>
[15:27] <mup> Bug #1688588 opened: Scrape pod types from registry for API docs <MAAS:Confirmed> <https://launchpad.net/bugs/1688588>
[16:54] <dannf> is there a way to figure out which boot-kernel corresponds with a boot-resources/snapshot-{ID} ?
[16:55] <dannf> someone reported a maas failure that went away - i have their maas logs, was trying to figure out if we can see if the kernel changed
[17:02] <dannf> smoser: ^
[17:50] <kiko> hmm, maybe grep for the ID in the logs dannf
[17:51] <dannf> kiko: yeah, i did - just don't know how you go from ID to image
[17:51] <mup> Bug #1688588 changed: Scrape pod types from registry for API docs <MAAS:Invalid> <https://launchpad.net/bugs/1688588>
[17:51] <kiko> doesn't the directory name contain the ID?
[17:52] <dannf> kiko: it does - but, w/o access to the system, i can't see what kernel is in it
[17:52] <kiko> dannf, simplestreams?
[17:52] <dannf> kiko: maybe - not sure how to navigate simplestreams
[17:52] <kiko> it's just JSON..
[17:52] <kiko> just grab it and look at it?
[17:53] <dannf> kiko: right - went through maas.io, couldn't find the json. found the index, but not the images. didn't spend a lot of time - i'll try again
[17:54] <mup> Bug #1688588 opened: Scrape pod types from registry for API docs <MAAS:Invalid> <https://launchpad.net/bugs/1688588>
[17:54] <kiko> http://images.maas.io/ephemeral/releases/streams/v1/
[17:55] <kiko> http://images.maas.io/ephemeral-v2/releases/streams/v1/
[17:55] <kiko> http://images.maas.io/ephemeral-v3/daily/streams/v1/
[17:56] <kiko> I think -v2 is what is currently active
[17:56] <kiko> but damn is that directory layout confusing, roaksoax, smoser!!
[17:56] <dannf> kiko: yeah, i think i found it
[17:57] <dannf> kiko: but not seeing anything that maps to the snapshot name. perhaps that is a locally generated id
[17:57] <mup> Bug #1688588 changed: Scrape pod types from registry for API docs <MAAS:Invalid> <https://launchpad.net/bugs/1688588>
[18:03] <mup> Bug #1688588 opened: Scrape pod types from registry for API docs <MAAS:Invalid> <https://launchpad.net/bugs/1688588>
[18:12] <mup> Bug #1688588 changed: Scrape pod types from registry for API docs <MAAS:Invalid> <https://launchpad.net/bugs/1688588>
[18:20] <smoser> kiko, v3 is used by maas 2.2 for sure
[18:20] <smoser> maybe 2.1
[18:34] <roaksoax> kiko: v3 is default for 2.1+
[19:06] <kiko> smoser, roaksoax: hmmm, and can you answer what dannf was asking?
[19:51] <xygnal> mpontillo: get a chance to look further into my bug/fix? just asking :)
[20:24] <mup> Bug #1688644 opened: MAAS not forwarding DNS <MAAS:New> <https://launchpad.net/bugs/1688644>
[23:02] <mpontillo> xygnal: that was the dhcp hostmap issue? I committed a fix earlier tofay
[23:02] <mpontillo> today*
[23:02] <xygnal> mpontillo ty much, will try to test that out ourselves by Monday
[23:03] <mup> Bug #1688661 opened: RSD API composition with remote storage constraints fails when no remote storage is currently being used. <MAAS:In Progress by newell-jensen> <MAAS RSD :In Progress by newell-jensen> <https://launchpad.net/bugs/1688661>