[01:07] <vibol> Don't know where to boot the image in maas lastest version!
[01:07] <vibol> Anyone here ?
[01:11] <catbus1> vibol: what do you mean?
[01:11] <vibol> the old version there and botton on the gui to import boot image
[01:12] <vibol> but the new gui don't see where to import the boot image... let me screenshot it for u
[01:12] <catbus1> vibol: Do you see the Images tab on the top? The third one from the left
[01:13] <vibol> yeb i got to http://ip/MAAS/image
[01:14] <vibol> http://postimg.org/image/4javz73h5/ catbus1
[01:15] <catbus1> it says there is no boot sources to download the images from
[01:15] <catbus1> let me see what the official doc says about creating boot source
[01:16] <vibol> Thank for help @catbus1
[01:20] <catbus1> vibol: that's odd, a default boot source should come with the maas install.
[01:21] <vibol> yes! this is i already espected
[01:21] <vibol> i'm really don't about this
[01:21] <vibol> don't understand*
[01:22] <catbus1> vibol: I have the same 1.8 version, but it was an upgrade from 1.7. One thing we can do here is to manually add the source via CLI.
[01:23] <catbus1> https://maas.ubuntu.com/docs/bootsources.html#adding-a-source
[01:24] <vibol> so i don't see where is the configure file located let me see!!
[01:30] <vibol> That strenge @catbus1
[01:31] <vibol> the boot image source is already configure the the correct url http://postimg.org/image/j4i5o96n3/
[01:33] <catbus1> it is configured.
[01:35] <catbus1> maybe it's something between clusterd and regiond
[01:36] <catbus1> I'd look at /var/log/maas/clusterd.log and /var/log/maas/regiond.log to see if there is any error messages about boot sources
[01:39] <catbus1> dinner
[01:40] <vibol> hmm.. nothing wrong on the log
[02:25] <vibol> ..........
[04:29] <mup> Bug #1439476 changed: Editing a cluster interface can cause an internal server error <oil> <MAAS:Expired> <https://launchpad.net/bugs/1439476>
[04:29] <mup> Bug #1457585 changed: 1.8b7: Empty list of all nodes and incorrect number of total nodes shown in UI <oil> <MAAS:Expired> <https://launchpad.net/bugs/1457585>
[13:28] <mup> Bug #1481759 opened: boot-images reports images, but pxe boot fails with no-such-image <landscape> <MAAS:New> <https://launchpad.net/bugs/1481759>
[13:31] <mup> Bug #1481759 changed: boot-images reports images, but pxe boot fails with no-such-image <landscape> <MAAS:New> <https://launchpad.net/bugs/1481759>
[13:37] <mup> Bug #1481759 opened: boot-images reports images, but pxe boot fails with no-such-image <landscape> <MAAS:New> <https://launchpad.net/bugs/1481759>
[15:22] <mup> Bug #1481813 opened: Failed trusty deployment on Lenovo X3650 M5 in UEFI mode <oil> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1481813>
[18:20] <mup> Bug #1481874 opened: New node cannot enlist due to internal server error <MAAS:New> <https://launchpad.net/bugs/1481874>
[20:35] <mup> Bug #1384453 changed: Feature: it would be nice if the summary page (the pie-chart page) showed how many total cores, ram and GB of storage we have. <MAAS:Fix Released> <https://launchpad.net/bugs/1384453>
[20:35] <mup> Bug #1386923 changed: It would be nice to have an easier way to see a node's status (ready vs deployed vs whatever) <confusing-ui> <MAAS:Fix Released> <https://launchpad.net/bugs/1386923>
[20:35] <mup> Bug #1389103 changed: Unable to install TD350 Server in EFI mode using MAAS <server-hwe> <MAAS:Invalid> <https://launchpad.net/bugs/1389103>
[22:47] <mup> Bug #1481940 opened: Failure in MAAS startup messages <MAAS:New> <https://launchpad.net/bugs/1481940>
[22:59] <mup> Bug #1481940 changed: Failure in MAAS startup messages <MAAS:New> <https://launchpad.net/bugs/1481940>
[23:05] <mup> Bug #1481940 opened: Failure in MAAS startup messages <MAAS:New> <https://launchpad.net/bugs/1481940>
[23:35] <mup> Bug #1481970 opened: VM stuck in comissioning - 500 Server error /metadata/2012-03-01 <MAAS:New> <https://launchpad.net/bugs/1481970>