mup | Bug #1576006 opened: 1.9.1: trying to save an overlapping network in the cluster generates ugly 500 <landscape> <MAAS:New> <https://launchpad.net/bugs/1576006> | 02:49 |
---|---|---|
mup | Bug #1576116 opened: MAAS adds regions controller as DNS resolver <MAAS:New> <https://launchpad.net/bugs/1576116> | 09:36 |
mup | Bug #1576116 changed: MAAS adds regions controller as DNS resolver <MAAS:New> <https://launchpad.net/bugs/1576116> | 09:42 |
mup | Bug #1576116 opened: MAAS adds regions controller as DNS resolver <MAAS:New> <https://launchpad.net/bugs/1576116> | 09:54 |
mup | Bug #1576146 opened: test 5 <MAAS:New> <https://launchpad.net/bugs/1576146> | 11:06 |
mup | Bug #1576194 opened: Enlistment via DHCP fails because DNS has bogus PTR record <landscape> <MAAS:New> <https://launchpad.net/bugs/1576194> | 12:57 |
mup | Bug #1575693 changed: test 2 <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1575693> | 13:28 |
mup | Bug #1575693 opened: test 2 <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1575693> | 13:37 |
mup | Bug # changed: 1575692, 1575693, 1575696, 1576146 | 13:40 |
mup | Bug #1575692 opened: this is a test <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1575692> | 13:49 |
mup | Bug #1575696 opened: test 3 <design> <MAAS:Invalid> <https://launchpad.net/bugs/1575696> | 13:49 |
mup | Bug #1576146 opened: test 5 <MAAS:Invalid> <https://launchpad.net/bugs/1576146> | 13:49 |
mup | Bug #1575692 changed: this is a test <ui> <MAAS:Invalid> <https://launchpad.net/bugs/1575692> | 13:58 |
mup | Bug #1575696 changed: test 3 <design> <MAAS:Invalid> <https://launchpad.net/bugs/1575696> | 13:58 |
mup | Bug #1576146 changed: test 5 <MAAS:Invalid> <https://launchpad.net/bugs/1576146> | 13:58 |
mup | Bug #1576267 opened: [UI 2.0b3] interface addresses on rack controller details page not updated automatically <MAAS:Triaged> <https://launchpad.net/bugs/1576267> | 15:10 |
mup | Bug #1576357 opened: Determine a method for how to reconnect a deleted rack controller <MAAS:New for ltrager> <https://launchpad.net/bugs/1576357> | 18:08 |
mup | Bug #1508741 changed: IPMI driver does not handle timeouts correctly <MAAS:Fix Released by newell-jensen> <https://launchpad.net/bugs/1508741> | 18:44 |
mup | Bug #1576370 opened: Create node lifecycle models for region and rack controllers <MAAS:New for ltrager> <https://launchpad.net/bugs/1576370> | 18:53 |
mup | Bug #1576146 opened: test 5 <MAAS:New> <https://launchpad.net/bugs/1576146> | 19:17 |
mup | Bug #1576146 changed: test 5 <MAAS:Invalid> <https://launchpad.net/bugs/1576146> | 19:47 |
DavidRama | hi all | 20:32 |
DavidRama | I've been struggling for days, having servers that do not provision without amy reason (got same hardware based server that are correctly provisionned). If I look at the IPMI Console I see that the deploy works fine but Maas still seems to wait for something. Looking at the server logs on Maas last command pass is : Node installation - 'curtin' curtin command block-meta . | 20:34 |
DavidRama | I can log to the deply stuck server using ssh | 20:35 |
roaksoax | DavidRama: so, your machines enlist, commission but don't deploy ? | 20:37 |
roaksoax | DavidRama: do they switch from Deploying to Failed Deployment ? | 20:37 |
maileh | h | 20:37 |
DavidRama | at the end yes | 20:38 |
roaksoax | DavidRama: hwat version of MAAS? 2.0 or 1.9 ? | 20:39 |
roaksoax | DavidRama: can you please share the installation log ? (it is in the webUI at the bottom) | 20:40 |
roaksoax | DavidRama: also, the full node event log ? | 20:40 |
maileh | DEBUG: 04-22 00:59:20, multi.py:135] Problem during bootstrap: '{'err': 'Bootstrapping environment "maas"\nStarting new instance for initial state server\nLaunching instance\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrary node\nWARNING no architecture was specified, acquiring an arbitrar | 20:42 |
maileh | maas version 1.9 | 20:42 |
roaksoax | maileh: do you have images imported ? is the cluster controller connected ? | 20:43 |
maileh | i just read this now https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out ... do i need to adjust my | 20:43 |
maileh | server | 20:44 |
maileh | roaksoax: yes everything looks normal ... nodes was successfully list and commissioned with the CPU and RAM info display but not the storage or the disk it is appear as zero | 20:45 |
maileh | it has the same error as juju complain above of the ui | 20:46 |
mup | Bug #1573046 opened: 14.04 images not available for commissioning as distro-info --lts now reports xenial <landscape> <sts> <MAAS:Fix Released by andreserl> <maas (Ubuntu):New for freyes> <maas (Ubuntu Trusty):New> <maas (Ubuntu Wily):New> <https://launchpad.net/bugs/1573046> | 20:47 |
mup | Bug #1576370 changed: Create node lifecycle models for region and rack controllers <MAAS:Invalid by ltrager> <https://launchpad.net/bugs/1576370> | 20:47 |
maileh | roaksoax: here is the nodes on the maas web interface Search nodes Submit FQDN MACPowerStatusOwnerCoresRAM (GiB)DisksStorage (GB) ACER-PC1-FG.KalianetCLOUD.toReady2100.0 HP-SRV1-FG.KalianetCLOUD.toReady4200.0 | 20:48 |
maileh | if you can see the 0.0 as the end are for the disk and storage | 20:49 |
maileh | any update guyss | 20:51 |
roaksoax | maileh: did you configure the storage of your servers | 20:52 |
roaksoax | maileh: Specify a storage device to be able to deploy this node.", "Mount the root \'/\' filesystem to be able to deploy this node. | 20:52 |
maileh | no i did not | 20:52 |
roaksoax | maileh: it seems you dont have a / mounted to be able to deploy your machjine | 20:53 |
maileh | where can i do that | 20:53 |
maileh | should i partition and format my hd before add to maas | 20:53 |
roaksoax | maileh: no | 20:53 |
roaksoax | maileh: go to your machine in MAAS, one that's on Ready state | 20:53 |
roaksoax | maileh: and check the storage section | 20:54 |
roaksoax | maileh: what do you have there ? | 20:54 |
maileh | this is the error on my machine page Storage No storage information. Commissioning this node will gather the storage information. Specify a storage device to be able to deploy this node. Mount the root '/' filesystem to be able to deploy this node. | 20:54 |
maileh | but it was successfully commisioned and READY state | 20:54 |
maileh | that's why i am confused | 20:55 |
roaksoax | maileh: go to the commissioning output at the bootom | 20:55 |
roaksoax | maileh: but either way, it seems it failed to discover your devices | 20:55 |
roaksoax | maileh: what type of hardware is it, and what storage devices are they ? | 20:55 |
maileh | HP Proliant G4 is the model | 20:56 |
maileh | sorry the model is DL380 G5 | 20:57 |
maileh | HP Proliant | 20:57 |
roaksoax | maileh: do they have properietary storage array or something ? that requires a proprietary hardware ? | 20:57 |
roaksoax | blake_r: whywould it not discover storage ? | 20:58 |
roaksoax | DavidRama: if you can pastebin the output, it would be great (in the UI, at the bottom, you'll have the installation log) | 20:58 |
roaksoax | DavidRama: and the full node event log, there's a link to open it fully | 20:58 |
roaksoax | DavidRama: pastebin.ubuntu.com | 20:58 |
maileh | roaksoax: label on disk is Dual port 10K SAS 72G | 20:59 |
maileh | i have 4 of those on my server | 20:59 |
roaksoax | blake_r: ^^ | 20:59 |
maileh | roaksoax: i believe the parts number for these disk is 389346-001 | 21:00 |
roaksoax | maileh: so go to the bottom of your machine | 21:00 |
roaksoax | maileh: there's a dropdown | 21:01 |
roaksoax | maileh: check the commissioning output | 21:01 |
roaksoax | the storage section | 21:01 |
maileh | ok will do that and let you know | 21:01 |
maileh | fyi this is my cluster detail Clusters NameConnectedStatusManaged interfacesNodesImages Cluster master✓Enabled12Syncededit delete | 21:01 |
roaksoax | marlinc: 00-maas-07-block-devices.out | 21:02 |
roaksoax | err | 21:02 |
roaksoax | maileh: 00-maas-07-block-devices.out | 21:02 |
roaksoax | 00-maas-07-block-devices.err | 21:02 |
roaksoax | those two | 21:02 |
DavidRama | roaksoax: my deploy hangs at this step in the gui log: TFTP Request - libutil.c32 after PXE Request - local boot | 21:04 |
DavidRama | mmm looks like it maas srv still sees the server as powered on but node is off | 21:08 |
maileh | roaksoax: this is 00-maas-07-block-devices.out ... this is its content : [ { "BLOCK_SIZE": "4096", "NAME": "sda", "ID_PATH": "/dev/disk/by-id/wwn-0x3000000300000001", "PATH": "/dev/sda", "ROTA": "1", "RM": "0", "MODEL": "VIRTUAL-DISK", "RO": "1", "SERIAL": "3000000300000001", "SIZE": "1468006400" }, { "BLOCK_SIZE": "4096", "NAME": "cciss!c0d0", "ID_PATH": "/dev/disk/by-id/wwn-0x600508b100104d395 | 21:08 |
DavidRama | Installation finished. | 21:10 |
DavidRama | but node hangs in "deploying status" (5 minutes now) | 21:10 |
DavidRama | ok node off in real but showed as on in the GUI | 21:11 |
maileh | i have only one line with .err ...00-maas-03-install-lldpd.err ...it's content is initctl: Unknown job: lldpd stop: Unknown instance: | 21:11 |
maileh | roaksoax: ....?? | 21:12 |
maileh | roaksoax: this is for my other server , actually it is an ACER PC .....[ { "BLOCK_SIZE": "4096", "NAME": "sda", "ID_PATH": "/dev/disk/by-id/wwn-0x3000000300000001", "PATH": "/dev/sda", "ROTA": "1", "RM": "0", "MODEL": "VIRTUAL-DISK", "RO": "1", "SERIAL": "3000000300000001", "SIZE": "1468006400" } ] | 21:13 |
maileh | roaksoax: there is no 00-maas-07-block-devices.err to both of them ... | 21:14 |
roaksoax | DavidRama: when the installation fininshes, the node reboots | 21:17 |
roaksoax | DavidRama: and loads the deployed environment | 21:17 |
roaksoax | DavidRama: and contact's maas again to tell it the deployment finished | 21:18 |
roaksoax | DavidRama: if that's not ahppeneing, there may be a reason for that | 21:18 |
maileh | roaksoax: any suggestion yet | 21:20 |
roaksoax | maileh: i'd suggest you file a bug report, with the details of your hardware, and attach that file you are pastebinbing | 21:22 |
roaksoax | or pasting | 21:22 |
DavidRama | roaksoax: is there a place to look for this kind of failure ? | 21:22 |
DavidRama | having this issue on 4 nodes and not on 12 others sitting in the same place | 21:23 |
DavidRama | same hardware | 21:23 |
roaksoax | DavidRama: i'd wathc the console | 21:23 |
maileh | roaksoax: can you suggest how to do that ... sorry but i have not file a bug before .... hope you can help ... thanks | 21:23 |
roaksoax | DavidRama: can you watch the console to see what's going on while the machine deploys ? | 21:23 |
roaksoax | maileh: https://bugs.launchpad.net/maas/+filebug | 21:24 |
DavidRama | I can | 21:24 |
DavidRama | need to start java | 21:24 |
DavidRama | @roaksoax: WARN: No MBR magic | 21:26 |
mup | Bug #1576417 opened: rack controllers and region controllers should not be visible to non-admins <MAAS:New> <https://launchpad.net/bugs/1576417> | 21:32 |
maileh | roaksox: also what's your best shot ... is it my hardware does not support or is it that i need | 21:51 |
mup | Bug #1576427 opened: juju bootstrap error complaining about my storage <MAAS:New> <https://launchpad.net/bugs/1576427> | 22:09 |
=== CyberJacob is now known as zz_CyberJacob | ||
=== zz_CyberJacob is now known as CyberJacob |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!