| BlackDex | hello there. I have installed a maas server, but i don't seem to have a commissioning release available | 09:42 |
|---|---|---|
| BlackDex | How can i manually download this? | 09:42 |
| D4RKS1D3 | BlackDex, it also happens to be and I realized that you need to download 14.04 (not higher) to do the commissioning (I'm using MaaS 1.9.0) | 12:39 |
| BlackDex | D4RKS1D3: Ah, that could explain it :). Seems to be working with the 14.04LTS :) | 13:14 |
| mup | Bug # changed: 1321023, 1381058, 1386327, 1389806, 1415820, 1419041, 1423691 | 13:59 |
| nagyz | hey guys | 14:01 |
| nagyz | any developers around? :) | 14:01 |
| nagyz | I think I've managed to stumble upon some bugs in the latest 1.9 | 14:01 |
| mup | Bug #1475977 changed: filenames for user-defined preseeds when booting using the debian installer are not correct. <MAAS:Invalid> <MAAS 1.7:New> <https://launchpad.net/bugs/1475977> | 14:30 |
| mup | Bug #1481992 changed: Upgrade of grub-pc during install fails <canonical-bootstack> <MAAS:Invalid> <curtin (Ubuntu):New> <https://launchpad.net/bugs/1481992> | 14:30 |
| mup | Bug #1475977 opened: filenames for user-defined preseeds when booting using the debian installer are not correct. <MAAS:Invalid> <MAAS 1.7:New> <https://launchpad.net/bugs/1475977> | 14:36 |
| mup | Bug #1481992 opened: Upgrade of grub-pc during install fails <canonical-bootstack> <MAAS:Invalid> <curtin (Ubuntu):New> <https://launchpad.net/bugs/1481992> | 14:36 |
| mup | Bug #1475977 changed: filenames for user-defined preseeds when booting using the debian installer are not correct. <MAAS:Invalid> <MAAS 1.7:New> <https://launchpad.net/bugs/1475977> | 14:39 |
| mup | Bug #1481992 changed: Upgrade of grub-pc during install fails <canonical-bootstack> <MAAS:Invalid> <curtin (Ubuntu):New> <https://launchpad.net/bugs/1481992> | 14:39 |
| mup | Bug #1475977 opened: filenames for user-defined preseeds when booting using the debian installer are not correct. <MAAS:Invalid> <MAAS 1.7:New> <https://launchpad.net/bugs/1475977> | 14:45 |
| mup | Bug #1481992 opened: Upgrade of grub-pc during install fails <canonical-bootstack> <MAAS:Invalid> <curtin (Ubuntu):New> <https://launchpad.net/bugs/1481992> | 14:45 |
| mup | Bug # changed: 1475977, 1481992, 1484268, 1488594, 1494955 | 14:51 |
| mup | Bug #1484268 opened: MAAS not auto-detecting/auto-entering credentials for HP Proliant ML310E G8 V2 server <MAAS:Invalid by newell-jensen> <maas (Ubuntu):Expired> <https://launchpad.net/bugs/1484268> | 14:54 |
| mup | Bug #1488594 opened: Nodes cannot boot after a storage disk replacement <ceph> <disaster-recovery> <storage> <MAAS:Invalid> <syslinux (Ubuntu):New> <https://launchpad.net/bugs/1488594> | 14:54 |
| mup | Bug #1494955 opened: MAAS reports duplicate MAC on commissioning <canonical-bootstack> <MAAS:Invalid> <MAAS 1.8:Triaged> <https://launchpad.net/bugs/1494955> | 14:54 |
| mup | Bug # changed: 1484268, 1488594, 1494955, 1508565, 1513224 | 15:00 |
| mup | Bug #1508565 changed: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power <blocks-hwcert-server> <MAAS:Invalid> <maas-images:Confirmed> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1508565> | 15:03 |
| mup | Bug #1508565 opened: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power <blocks-hwcert-server> <MAAS:Invalid> <maas-images:Confirmed> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1508565> | 15:18 |
| mup | Bug #1508565 opened: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power <blocks-hwcert-server> <MAAS:Invalid> <maas-images:Confirmed> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1508565> | 15:18 |
| mup | Bug #1513224 opened: 1.9b2: node details storage displays big json blob <landscape> <MAAS:Won't Fix> <https://launchpad.net/bugs/1513224> | 15:18 |
| mup | Bug #1508565 changed: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power <blocks-hwcert-server> <MAAS:Invalid> <maas-images:Confirmed> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1508565> | 15:21 |
| mup | Bug #1508565 changed: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power <blocks-hwcert-server> <MAAS:Invalid> <maas-images:Confirmed> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1508565> | 15:21 |
| mup | Bug #1513224 changed: 1.9b2: node details storage displays big json blob <landscape> <MAAS:Won't Fix> <https://launchpad.net/bugs/1513224> | 15:21 |
| mup | Bug #1537789 opened: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source <MAAS:New> <https://launchpad.net/bugs/1537789> | 15:30 |
| mup | Bug #1537789 changed: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source <MAAS:New> <https://launchpad.net/bugs/1537789> | 15:33 |
| mup | Bug #1537789 opened: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source <MAAS:New> <https://launchpad.net/bugs/1537789> | 15:36 |
| === roaksoax is now known as roaksoax-brb | ||
| mup | Bug #1537789 changed: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source <MAAS:New> <https://launchpad.net/bugs/1537789> | 15:42 |
| mup | Bug #1508501 changed: maas dns entry missing <adoption> <charmers> <cpp> <MAAS:Invalid> <MAAS 1.8:Triaged> <https://launchpad.net/bugs/1508501> | 15:51 |
| mup | Bug #1537789 opened: MAAS dhcp fails to start on up-to-date Xenial with MAAS built from source <MAAS:New> <https://launchpad.net/bugs/1537789> | 15:51 |
| mup | Bug #1508501 opened: maas dns entry missing <adoption> <charmers> <cpp> <MAAS:Invalid> <MAAS 1.8:Triaged> <https://launchpad.net/bugs/1508501> | 15:54 |
| === kwmonroe_ is now known as kwmonroe | ||
| mup | Bug #1508501 changed: maas dns entry missing <adoption> <charmers> <cpp> <MAAS:Invalid> <MAAS 1.8:Triaged> <https://launchpad.net/bugs/1508501> | 16:00 |
| lovea | Hi, Trying to use ProLiant DL160 Gen9 servers in a MAAS set up. They have hpdsa drivers detected. So far so good. Then I use Juju to deploy a 15.10 Wily charm and the deploy fails because the hpdsa drivers are requested from http://downloads.linux.hp.com/SDR/repo/ubuntu-hpdsa/dists/wily/main/binary-amd64/Packages. This doesn't exist. HP only has a 14.04 Trusty repo. Any ideas how I can proceed? | 16:08 |
| === narindergupta is now known as narindergupta_aw | ||
| * jmalcaraz Hi | 16:56 | |
| timello | Hi there, I'm trying to deploy ubuntu on POWER8 box using maas. I'm wondering if there's anything I should do in the POWER box before issuing the commission... In the ipmi console log, I don't see anything in the 'Kernel command line:' | 17:31 |
| timello | MaaS can power on/off, but commission fails | 17:32 |
| timello | Nothing in the logs other than: ERROR: Section post-commit `Chassis_Boot_Flags'] | 17:33 |
| timello | And: [WARNING] Failed to change the boot order to PXE <IP> | 17:33 |
| bdx | hey whats up everyone? Is there a maas/next repo for xenial? | 18:59 |
| roaksoax-brb | bdx: we are testing a xenial release as of now. We should have something up this week | 19:02 |
| bdx | roaksoax-brb: sweet! thanks! | 19:02 |
| nagyz | so something changed and (even after a reinstall!) my enlistment and commissioning runs into errors when trying to get an IP for the node :/ | 20:42 |
| nagyz | according to maas's log, dhcp is ACKing it, but the node never sees it (or just ignores it) | 20:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!