[01:48] <eternal_> Hi, is there a fix for the no-such-image boot problem?  I've been looking around but can't seem to find a solution.  Each time I PXE boot my machines say Loading ubuntu/amd64/generic/trusty/no-such-image/boot-kernel which fails.
=== kdavyd_ is now known as kdavyd
=== plars_ is now known as plars
=== jefferai_ is now known as jefferai
[04:21] <mup> Bug #1491831 changed: maas-cli should allow to specify a cluster controller for a new node <MAAS:Expired> <https://launchpad.net/bugs/1491831>
[04:24] <mup> Bug #1491831 opened: maas-cli should allow to specify a cluster controller for a new node <MAAS:Expired> <https://launchpad.net/bugs/1491831>
[04:30] <mup> Bug #1491831 changed: maas-cli should allow to specify a cluster controller for a new node <MAAS:Expired> <https://launchpad.net/bugs/1491831>
[04:33] <mup> Bug #1491831 opened: maas-cli should allow to specify a cluster controller for a new node <MAAS:Expired> <https://launchpad.net/bugs/1491831>
[04:36] <mup> Bug #1491831 changed: maas-cli should allow to specify a cluster controller for a new node <MAAS:Expired> <https://launchpad.net/bugs/1491831>
[07:00] <mup> Bug #1512959 opened: MAAS should not offer EXT3, rather VFAT, EXT2, EXT4 <MAAS:New> <https://launchpad.net/bugs/1512959>
[07:03] <mup> Bug #1512959 changed: MAAS should not offer EXT3, rather VFAT, EXT2, EXT4 <MAAS:New> <https://launchpad.net/bugs/1512959>
[07:06] <mup> Bug #1512959 opened: MAAS should not offer EXT3, rather VFAT, EXT2, EXT4 <MAAS:New> <https://launchpad.net/bugs/1512959>
[09:58] <mup> Bug #1512891 changed: MAAS storage partitioning does not allow formatting as Swap <MAAS:Won't Fix> <https://launchpad.net/bugs/1512891>
[10:01] <mup> Bug #1512891 opened: MAAS storage partitioning does not allow formatting as Swap <MAAS:Won't Fix> <https://launchpad.net/bugs/1512891>
[10:13] <mup> Bug #1512891 changed: MAAS storage partitioning does not allow formatting as Swap <MAAS:Won't Fix> <https://launchpad.net/bugs/1512891>
[10:16] <mup> Bug #1512891 opened: MAAS storage partitioning does not allow formatting as Swap <MAAS:Won't Fix> <https://launchpad.net/bugs/1512891>
[10:19] <mup> Bug #1512891 changed: MAAS storage partitioning does not allow formatting as Swap <MAAS:Won't Fix> <https://launchpad.net/bugs/1512891>
[10:28] <mup> Bug #1463176 changed:  modprobe hpvsa fails after installing hpvsa <hp> <hpvsa> <MAAS:Invalid> <https://launchpad.net/bugs/1463176>
[10:28] <mup> Bug #1512825 changed: Deployment of Wily from Release Stream fails because of Cloud-Init <MAAS:Won't Fix> <maas-images:New> <https://launchpad.net/bugs/1512825>
[10:28] <mup> Bug #1512890 changed: Way too complicated workflow to remove default LVM partition scheme on 1.9 <MAAS:New> <https://launchpad.net/bugs/1512890>
[11:34] <mup> Bug #1501112 changed: Node Networking - Users can edit network info while commissioning <MAAS:Invalid by blake-rouse> <https://launchpad.net/bugs/1501112>
[11:55] <devop> HELP
[12:05] <devop> Hello
[12:05] <devop> Somepeople
[12:06] <devop> can help me?
[12:12] <roaksoax> !ask
[12:12] <roaksoax> !question
[12:12] <roaksoax> !help
[12:12] <mup> roaksoax: Run "help <cmdname>" for details on: bug, contrib, echo, help, infer, login, poke, register, run, sendraw, sms
[12:12] <roaksoax> argh
[12:13] <roaksoax> devop: plase ask your question and if someone knows the answer they'll help
[12:19] <devop> help
[12:20] <devop> I have one problem with the nodes
[12:20] <devop> not working
[12:20] <devop> i ready every documentation in internet
[12:20] <devop> but my nodes not working yet
[12:21] <devop> can you help me?
[12:21] <roaksoax> devop: TBH, with the information you've provided I cannot help
[12:21] <roaksoax> devop: if you were to expand what's actually not working, I'd be able to know whether I can help
[12:22] <devop> the problem is 	Failed commissioning
[12:23] <devop> i installed everything
[12:23] <roaksoax> devop: there are many reasons why it could fail
[12:24] <roaksoax> devop: 1. what version of MAAS
[12:24] <roaksoax> 2. what type of machine is it
[12:24] <devop> the last
[12:24] <roaksoax> 3. can MAAS power control these machines ?
[12:24] <devop> my machine is one dell power edge r220
[12:24] <roaksoax> devop: i dunno what you mean with last, it could be last one in tursty, (1.7), last one stable in ppa (1.8), last one in development (1.9)
[12:25] <roaksoax> devop: can MAAS power control them? as in, whne you click commission, do they actually turn on?
[12:25] <devop> this is MAAS Version 1.8.3+bzr4053-0ubuntu1 (tru
[12:25] <devop> not
[12:26] <roaksoax> devop: so MAAS cannot power control them?
[12:26] <devop> really
[12:26] <devop> can not power
[12:27] <roaksoax> devop: how did you add the machines to MAAS? via WebUI ?
[12:27] <devop> yes via web
[12:27] <devop> i created two nodes
[12:28] <roaksoax> devop: ok, go to the node details page, and on the top, there's a button that says "check power"
[12:28] <roaksoax> what's the result of that?
[12:28] <devop> one the power type wake on lan and the other vish
[12:28] <roaksoax> devop: ah!
[12:29] <roaksoax> devop: then that's probably the problem
[12:29] <roaksoax> devop: if it is a dell, doesn't it have IPMI ?
[12:29] <devop> i used the ubuntu image personalized for dell power edge r220
[12:30] <devop> ok one moment
[12:30] <devop> i ll try
[12:33] <devop> this the log
[12:33] <devop> Powering node on	Wed, 04 Nov. 2015 13:32:03 Node changed status - From 'New' to 'Commissioning'
[12:36] <devop> comissioning... but not ready
[12:37] <devop> the status is commisioning always
[12:37] <devop> 3 days looking a solution for this problem
[12:38] <devop> I need nodes ready for install openstack and juju
[12:40] <devop> failed now
[12:40] <devop> Failed to power on node - Timed out	Wed, 04 Nov. 2015 13:37:03 Node changed status - From 'Commissioning' to 'Failed commissioning'	
[12:40] <devop> Andres i m spanish too
[12:40] <devop> where are you from
[12:47] <devop> que desesperacion
[13:51] <devop> somepeople can help me?
[14:00] <marka13> Question: I have landscape juju and maas on one machine.  When I perform an openstack install, it gets to the very end of the installation where it is going to import images.  But something is changing the IP of eth0 and I am thinking that is what is failing the last step
[14:00] <marka13> anyone seen that behavior before?
[14:01] <marka13> twisted.python.failure.Failure <class 'twisted.internet.error.ConnectionDone
[14:21] <marka13> I can't seem to find in the logs where the ip was changed, the interfaces file is 10.0.0.9, but for some reason the ip got changed to 0.26
[14:21] <marka13> weird
[14:44] <mup> Bug #1511713 changed: udev rules not updated to reflect MAC change in node <sts> <MAAS:Invalid> <https://launchpad.net/bugs/1511713>
[14:44] <mup> Bug #1513085 opened: Partitioning should align for performance <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1513085>
[14:56] <mup> Bug #1513095 opened: MAAS should prevent deploying nodes with PXE interface 'unconfigured' (or all NIC's as 'Unconfigured') <networking> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1513095>
=== jfarschman is now known as MilesDenver
[15:10] <marka13> no one around?
[15:17] <MilesDenver> no one
[15:26] <marka13> lol
[15:26] <marka13> Just trying to figure out what had happened
=== jfarschman is now known as MilesDenver
[15:41] <mup> Bug #1513111 opened: When a bond is created all IP address associated with the bond members should be removed <networking> <MAAS:Triaged> <https://launchpad.net/bugs/1513111>
[15:44] <mup> Bug #1513111 changed: When a bond is created all IP address associated with the bond members should be removed <networking> <MAAS:Triaged> <https://launchpad.net/bugs/1513111>
[15:50] <mup> Bug #1513111 opened: When a bond is created all IP address associated with the bond members should be removed <networking> <MAAS:Triaged> <https://launchpad.net/bugs/1513111>
[19:50] <mup> Bug #1512029 changed: maasserver.models.tests.test_interface:TestReleaseAutoIPs.test__calls_update_host_maps_for_next_ip_managed_subnet randomly fails <tech-debt> <tests> <MAAS:Invalid> <https://launchpad.net/bugs/1512029>
[20:21] <mup> Bug #1513198 opened: maas needs to install wsmancli as a dependency <MAAS:New> <https://launchpad.net/bugs/1513198>
[20:24] <mup> Bug #1513198 changed: maas needs to install wsmancli as a dependency <MAAS:New> <https://launchpad.net/bugs/1513198>
[20:27] <mup> Bug #1513198 opened: maas needs to install wsmancli as a dependency <MAAS:Won't Fix> <https://launchpad.net/bugs/1513198>
[20:30] <mup> Bug #1513198 changed: maas needs to install wsmancli as a dependency <MAAS:Won't Fix> <https://launchpad.net/bugs/1513198>
[20:42] <mup> Bug #1513198 opened: maas needs to install wsmancli as a dependency <MAAS:New> <https://launchpad.net/bugs/1513198>
[20:48] <mup> Bug #1513198 changed: maas needs to install wsmancli as a dependency <MAAS:New> <https://launchpad.net/bugs/1513198>
[21:33] <mup> Bug #1513214 opened: Unable to remove bond in the UI <networking> <ui> <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1513214>
[21:33] <mup> Bug #1513224 opened: 1.9b2: node details storage displays big json blob <landscape> <MAAS:New> <https://launchpad.net/bugs/1513224>
[23:18] <mup> Bug #1513214 changed: Unable to remove bond in the UI <networking> <ui> <MAAS:Invalid by ltrager> <https://launchpad.net/bugs/1513214>
[23:18] <mup> Bug #1513258 opened: CSS Broken for Bond Network Device <networking> <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1513258>