[03:17] Bug #1611999 opened: MAAS 2 does not properly probe power state on Cisco UCS systems [03:59] Bug #1612039 opened: MAAS Cannot Commission === mpontillo_ is now known as mpontillo [06:11] Bug #1612064 opened: [2.0 RC4] Can't add VMware chassis - SSL: CERTIFICATE_VERIFY_FAILED

[06:18] Bug #1612064 changed: [2.0 RC4] Can't add VMware chassis - SSL: CERTIFICATE_VERIFY_FAILED

[06:24] Bug #1612064 opened: [2.0 RC4] Can't add VMware chassis - SSL: CERTIFICATE_VERIFY_FAILED

[06:48] Bug #1612078 opened: [2.0 RC4] __init__ error when entering power parameters for manually enlisted ESXi VM

=== frankban|afk is now known as frankban [07:46] kiki [07:47] kiko, === degville- is now known as degville [08:21] interesting [08:21] I am wanting to add all the 'nodes' on an esx server [08:22] I thought I could add '1' chassis to maas with a filter for all images starting with "node" [08:22] but [08:22] Every time I add the esx server as a chassis it adds one node [08:23] I wonder if its because I copied the same node 12 times? [08:23] In esx when I created them [08:23] I am going to import 12 nodes and see what happens [08:27] deleted all 12 nodes [08:27] didnt delete the 3 i added to maas, so i deleted them from maas from gui [08:30] added one node, got an ip address, kernel still missing [08:31] no node in maas [08:35] added 6 nodes all with kernel error, none appear in maas automatically === valeech_ is now known as valeech [11:34] newmember: check logs, that will tel you what's the issue [11:48] Bug #1595379 changed: 2.0 beta7 : having to recommission some nodes multiple times before they're finally ready [11:48] Bug #1612064 changed: [2.0 RC4] Can't add VMware chassis - SSL: CERTIFICATE_VERIFY_FAILED

[11:48] Bug #1612078 changed: [2.0 RC4] __init__ error when entering power parameters for manually enlisted ESXi VM

[11:48] Bug #1612203 opened: [Trunk] MAchine unable to pxe with no-such-image while non-related images rae being imported [11:48] Bug #1612209 opened: can't change image used for commissioning [11:48] Bug #1612213 opened: dhcpd leases are not cleaned up properly [11:54] Bug #1612209 changed: can't change image used for commissioning [12:06] Bug #1612209 opened: can't change image used for commissioning [12:18] Bug #1612209 changed: can't change image used for commissioning [12:18] Bug #1612213 changed: dhcpd leases are not cleaned up properly [13:37] Bug #1612248 opened: MAAS doesn't have debug logging for power actions making it impossible to effectively debug [13:43] Bug #1612248 changed: MAAS doesn't have debug logging for power actions making it impossible to effectively debug [13:55] Bug #1612248 opened: MAAS doesn't have debug logging for power actions making it impossible to effectively debug [14:04] newmember, did you import the i386 images? [14:38] roaksoax: Hi. I have a question. From MAAS UI I want to select power type as VMware. Now I want to add VMware VM manually to MAAS by providing VMware details(for power) and VMware vm details. Can I do like this? Is it work? [14:40] roaksoax: Because In MAAS UI we can find VMware as power type Option. [14:44] Actually, we have OpenStack autopilot testdrive option for VMware VMs. But I don't want to use Openstack autopilot testdrive. Can I enlist and commissiom VMware VMs as we did for Physical servers. [14:45] roaksoax: Using MAAS [14:47] siva, good question -- I don't know whether auto-enlistment works on VMs [14:47] siva, if not, just specify the power details manually [14:47] roaksoax: If we can't do , why we have VMware as power type Option. [14:53] Kiko: Hi. Actually, I manually added VMware vm to MAAS. When I click on "Save changes". Power error install "python-pyvmomi" package on MAAS installed node. I installed . then It started commissioning. [14:55] kiko: Immediately status moved from commissioning to failed commissioning. Failed to power on node - Node could not be powered on: Failed talking to node's BMC for an unknown reason. [14:57] From maas log; It was showing Marking node failed: Node could not be powered on: Failed talking to node's BMC for an unknown reason. [15:02] looks like the information you've configured MAAS with isn't correct [15:11] Kiko: I have a question here. If we take openstack autopilot testdrive for VMware VMs , How MAAS will manage Power settings and boot settings. I think there we will run autopilot script while running the script it will ask power details.... How we can set boot option as PXE in VMware vm. I provided power details is correct. Am I enable anything else in vm for power. [15:13] siva, just a sec [15:21] From VMware vm , I observed power management : "standby". I am not able to change anything here. But I can enable PXE boot. [15:28] Bug #1612293 opened: [1.9] eth0 tried to get a DHCP IP, no matter what [15:36] Hi. if any one tried with the above approach[selecting power type as VMware and moving further instead of openstack autopilot test drive]. Please provide me info. [16:06] siva, can you send me a screenshot of what you've configured on MAAS for the vmware power driver? [16:10] kiko : Ok. How to send a screenshot in chat? [16:12] Kiko: I don't know how to send a scrrenshot. I send the entered Power details. [16:18] kiko: http://paste.openstack.org/show/554223/ [16:31] kiko, yes I imported the i386 image [16:32] I am using MAAS Version 1.8.2+bzr4041-0ubuntu1 (trusty1), so I thought I better do a "apt-get upgrade. [16:33] Maybe I would get maas 2.0 [16:33] I did after ready a few of issues looked to be discussed in 'askubuntu' [16:33] eg [16:33] http://askubuntu.com/questions/790768/commissioning-vmware-machines-not-visible-in-maas-using-autopilot-vmware-applian [16:35] currently its timing out on some of the respositories [16:35] http://picpaste.com/Capture3-rxtn7viq.PNG [16:36] oh [16:36] newmember, you should be using at least 1.9 [16:37] kiko: I send the power details and virtual machine details. [16:37] I downloaded the autopilot fresh from ubuntu just a few days ago [16:43] newmember, your internet connectivity from the nodes is not working [16:43] newmember, is the default gateway correct, and is it correctly firewalling/NATting the traffic? [16:43] newmember, I'm happy you are past the original problem you had though! [16:44] siva, the VMWare username is really root? [16:44] kiko, yes yes [16:44] kiko, well nodes are still not starting [16:44] and [16:44] newmember, they aren't starting because they can't get outside [16:45] newmember, can you dhcp a laptop from the MAAS server and see if it can get to the Internet? [16:45] kiko, autopilot is 'auto' discovering the nodes [16:45] newmember, I understand, but if your uplink isn't working, nothing will work [16:45] the entire subnet can reach the internet and dns works and dhcp yada yada [16:45] siva, the VMware credentials there are for the vsphere [16:46] newmember, why is the archive access failing, then? [16:46] its not responding [16:46] the first archives responded very quickly [16:47] newmember, my guess-blame is a problem upstream [16:47] kiko: yes. username is root. [16:47] newmember, if a laptop is able to do an apt-get update when DHCPing from MAAS, then I would agree I'm wrong [16:48] http://picpaste.com/Capture4-FkIVKyYu.PNG [16:48] kiko: yes that VMware vSphere client credentials. [16:48] siva, hmm, interesting. what do your MAAS logs say? [16:49] newmember, a ping is not an apt-get update :) [16:49] kiko, hey thanks for even just chatting about it, its best I second guess everything [16:49] kiko, I can resolve the hostname and reach the host, yes the apt-get has to the next thing. [16:49] newmember, the apt-get update will tell us if HTTP works [17:06] siva, could you be encountering this bug? https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1608639 [17:06] siva, check the logs [17:11] newmember, anyway, you should move from 1.8 to at least 1.9 === frankban is now known as frankban|afk [17:15] Kiko: At starting I got the same issue. Then I manually added vm to maas. Then It was showing From maas log; It was showing Marking node failed: Node could not be powered on: Failed talking to node's BMC for an unknown reason. [17:16] siva, check the logs [17:25] Kiko: Actually, I have one Openstack autopilot setup with 5 physical servers. But I should release two 3 servers for other purpose. Due to this we are planning to use VMware VMs. From my existing MAAS node I just tried to add a new node[that is VMware vm]. [17:25] gotcha [17:26] siva, I unfortunately don't know enough about vmware to help you, so if you can't check the logs to see what error messages are somebody else will need to look into it [17:26] kiko: I just faced the mentioned issues. [17:31] Kiko: Thanks kiko for your valuable information. I will try with a fresh setup using VMware VMs. Then it will be good. with respect to your info. I confirmed that we can enlist and commission VMware VMs. I will try this. Thank you. [17:32] siva, ah, cool -- thanks! [18:31] Bug #1611999 changed: [2.0] MAAS cannot power query with Cisco UCSM power driver [18:47] siva, what maas version are you using? [20:04] is there any aversion to using MaaS in a virtual machine ? [20:04] to be more specific, running a cluster controller in a VM ? [20:38] jwitko: you can use maas in virtual machines [20:38] jwitko: or you can use virtual machines with maas [20:43] roaksoax thanks :) === icey is now known as icey|vacation [23:42] Hey roaksoax, not sure if you're still around but I have a question for HA MaaS setup. Currently my needs are for a single subnet of < 500 physical machines. So I was going to run the region controller and cluster controller on the same machine. [23:42] if I have two machines running both region and cluster controllers can they be set up in HA? or does it require the region controller to be separated from the cluster controllers? [23:43] and also could the postgres SQL servers also run on those two boxes in HA mode? [23:43] not sure if that introduces a risk of data loss in the event of a crash