[04:23] Bug #1545645 changed: [1.9] Failed to deploy Ubuntu on IBM x3850 via MAAS v1.9.0 [04:23] Bug #1579729 changed: DHCP Snippets: The toggle buttons cannot be deactivated [09:03] can somebody help me with that? http://askubuntu.com/questions/805564/ubuntu-maas-does-not-recognize-nodes-storage-disks [10:02] can somebody help me with that? http://askubuntu.com/questions/805564/ubuntu-maas-does-not-recognize-nodes-storage-disks === KpuCko is now known as asfjsdfmsdf [11:30] can somebody help me with that? http://askubuntu.com/questions/805564/ubuntu-maas-does-not-recognize-nodes-storage-disks === asfjsdfmsdf is now known as KpuCko [13:30] roaksoax: Hi. MAAS not able to detect nodes storage devices? I am using MAAS Version 1.9.3+bzr4577-0ubuntu1 (trusty1). can you please help me in this? [13:41] siva: 1. what storage devices are you using. 2. do you have logs ? [13:42] siva i have same problem [13:42] in the lshw log of the node im seeing the hard disks, but the maas dashboard shows 0.0 at the storage column [13:43] im using ubuntu 16.04 LTS with maas package shiped with distribution. [13:45] maas doesn't get the storage information from lshw [13:45] lshw is completely unreliable [13:45] did you guys file a bug ? [13:46] roaksoax: I am using SATA disks and SAS. I am using Dell machines. Logs : http://paste.openstack.org/show/545127/ [13:47] kpuCko: I am using ubuntu 14.04. For me also in MAAS UI it shows 0.0 at storage column. [13:50] roaksoax: And without listing hard disks the tranaction moved from new to ready. But the power state is On. When I click on "Check now" then also power is in "On" state. [13:50] siva: the logs you provide wont give m much. I need cloud-init logs [13:51] siva: while it is commissioning, you can ssh into the commissioning environment (enabling the opttion), and after it finishes [13:51] you can grab /var/log/cloud-init* [13:51] roaksoax i'm speaking about lshw because it output is shown at the maas dashboard on the node tab [13:51] KpuCko: we dont get the storage info from lshw [13:52] KpuCko: we collect lshw as part of the process [13:52] but storage is not from lshw [13:52] also when i start the node i can ssh to the box and see the linux os recognize the disks correctly [13:52] so what i have to do to figure out this issue? [13:57] roaksoax: cloud-init logs http://paste.openstack.org/show/545134/ [13:59] siva: can you attach those to the bug report I'll send your way in a sec [13:59] KpuCko: https://bugs.launchpad.net/maas/+bug/1604393/comments/11 [13:59] siva: https://bugs.launchpad.net/maas/+bug/1604393/comments/11 [13:59] attach all of those logs [14:00] roaksoax: OK. i will attach. [14:00] thansk [14:06] Bug #1608545 opened: "sudo maas createadmin" instructions need --username [14:09] another of my problem is that i cannot use wake on lan feature [14:09] KpuCko: wake on lan is no longer suipported [14:09] does anybody knows why? I can't find it on the power profiles on the node confiug [14:11] hmmm, why? you mean i have to wake my boxes only from console? via wakeonlan or etherwake [14:13] KpuCko: MAAS no longer supports wake on lan [14:13] ok, thanks [14:13] in fact, using WoL was really unreliable [14:44] roaksoax: Hi. I attached all the logs you mentioned http://paste.openstack.org/show/545140/ [14:50] roaksoax, i tested with 14.04 LTS - it works. [14:50] I can see the nodes storages to the dashboard. [14:50] So this is bug in 16.04 LTS version of maas (maas 2.0) [14:51] i have to go, thanks for support roaksoax [14:54] Bug #1608555 opened: Error when using dhcp range with pre-existing dynamic reservation [15:13] Bug #1608557 opened: [UI, UX] MAAS doesn't tell the user if a dynamic range was already created when trying to enable DHCP. [15:13] Bug #1608559 opened: [UI, UX] Bad error message when failing to create a range because another already exists [15:16] Bug #1608557 changed: [UI, UX] MAAS doesn't tell the user if a dynamic range was already created when trying to enable DHCP. [15:16] Bug #1608559 changed: [UI, UX] Bad error message when failing to create a range because another already exists [15:25] Bug #1608557 opened: [UI, UX] MAAS doesn't tell the user if a dynamic range was already created when trying to enable DHCP. [15:25] Bug #1608559 opened: [UI, UX] Bad error message when failing to create a range because another already exists [15:46] roaksoax: While commissioning MAAS not able to list hard disks. But with the assigned dhcp IP I can able to login to that machine. And I am able to perform all actions generally what we can perform after installing a OS. After commissioning power state is "On". [15:47] siva: , ok, someone will look at it later this week [15:47] but the info we needed is ther [15:55] roaksoax: OK. the info we needed means? generally after OS deployed by the OS we can do all actions. Once OS is deployed Power state should be "ON". yesterday I tried . for two OS deployment failed with Curtin failed: configuring storage. For one node it is successful. When I was trying to debug setup went wrong. Then I reinstalled MAAS. And I started again the same process. This time I faced the mentioned issues. From my previous setup [16:01] roaksoax: Ok. Thank you for your support. [17:40] Bug #1608629 opened: UI does not allow for tag management [17:55] Bug #1608629 changed: UI does not allow for tag management [18:01] Bug #1608629 opened: UI does not allow for tag management [18:37] Bug #1608639 opened: ssl error vmware vcenter 6 connection [19:04] Bug #1608639 changed: [2.0rc3] SSL verification error when connecting to VMware vCenter === Beret- is now known as Beret