=== med_ is now known as Guest34220 [05:29] Bug #1654929 opened: Node page should display spaces [05:29] Bug #1654930 opened: VLAN listing should be sorted as a number === deej` is now known as deej [08:05] Kildurin: Check out the command "maas my-profile interface update -h" You can update some bond parameters there === zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_CyberJacob === zz_CyberJacob is now known as CyberJacob [10:15] Bug #1654981 opened: creating a bridge on a device doesn't inherit device config or allow configuring during creation [10:24] Bug #1654981 changed: creating a bridge on a device doesn't inherit device config or allow configuring during creation [10:27] Bug #1654981 opened: creating a bridge on a device doesn't inherit device config or allow configuring during creation [12:43] hey! trying to setup maas in a shared datacenter - is this even possible? [12:44] the first issue im facing is that there already is a dhcp server running [12:45] i also want to restrict my maas nodes to only use a certain ip range, but when im trying to create a subnet, i only see an option to do so using a CIDR [12:57] SimonKLB: you can create a subnet, and create a "reserved" range in the subnet, so that MAAS doesnt use that range of the subnet [12:57] SimonKLB: and MAAS can stil work if you already have a dhcp server [12:57] SimonKLB: depends how you configure it [13:03] roaksoax: ah, so you kind of bans ranges rather than create ranges [13:05] SimonKLB: yes, in 2.2, we will have another feature that will allow you to do the opposite [13:05] SimonKLB: basically, the subnet is unmanaged by MAAS, but you can create ranges MAAS can use [13:05] SimonKLB: so you would have both modes [13:05] roaksoax: cool thanks! [13:34] roaksoax: can i get logging from a node that is starting up somehow? [13:43] i can see that the dhcp request is being ack'd by the dhcp server, but the webgui says "IP Address (Unconfigured)" [13:48] SimonKLB: what are you doing ? commissioning ? [13:48] SimonKLB: you can get logging in two places, for two different purposes [13:48] roaksoax: just trying to deploy a node [13:48] SimonKLB: 1. the Mchine Event log, which you can find uner the machine details page [13:49] SimonKLB: it will tell you if it is PXE booting, and what things it is doing [13:49] SimonKLB: rsyslog /var/log/maas/rsyslog///* [13:50] roaksoax: the events are kind of non-verbose, i can see that things art powered on and off, but not much else [13:50] the rsyslog looks promising though! [13:51] SimonKLB: you can see more events actually. The ones that are shown in the main page of the machine are non-verbose [13:51] SimonKLB: but yes, those are basically more high level events [13:51] SimonKLB: in the events detail you will see what cloud-init is doing for example [13:51] ah neat [13:53] roaksoax: so the current issue im facing is that i cant ssh to the machine [13:54] SimonKLB: right, while the machine is 'deploying' ? [13:54] yes [13:54] it looks stuck [13:55] roaksoax: do i have to do anything else other than uploading my pubkey to the maas user? [13:56] SimonKLB: nope, so cloud-init should import your ssh key into the installation environment [13:58] roaksoax: no cloudinit events in the event log [13:58] PXE request - installation, TFTP Request boot-kernel and boot-initrd and then just Power state query [14:00] everything looks otherwise correct, the DHCP packets are going out, its responding to ping and ssh [14:00] just not setting it up with cloudinit i suppose [14:48] roaksoax: i think i found the issue http://paste.ubuntu.com/23770633/ [14:48] any ideas? [14:49] or anyone else for that matter [14:51] SimonKLB: that is strange.... [14:51] SimonKLB: what's your rackd.conf show in /etc/maas/rackd.conf [14:52] roaksoax: cluster_uuid: b2bec0e6-2b15-4d4b-aece-352d632b2652 [14:52] maas_url: http://localhost:5240/MAAS [14:54] SimonKLB: try chaching maas_url: http://:5240/MAAS [14:54] SimonKLB: also, what version of MAAS you running ? [14:56] roaksoax: 2.1.2+bzr5555-0ubuntu1~16.04.1 [14:57] roaksoax: do i have to restart anything after changing rackd.conf ? [14:57] Bug #1655048 opened: MAAS upgrade rewrites maas-http.conf [15:03] roaksoax: changing the url seem to have done the trick! thanks a lot for all the help today :) [15:09] Bug #1655048 changed: MAAS upgrade rewrites maas-http.conf [15:15] Bug #1655048 opened: MAAS upgrade rewrites maas-http.conf [15:16] Bug #1655049 opened: List index out of range on main page and nodes page [15:19] Bug #1655049 changed: List index out of range on main page and nodes page [15:28] Bug #1655049 opened: List index out of range on main page and nodes page [15:57] Bug #1655048 changed: MAAS upgrade rewrites maas-http.conf === mup_ is now known as mup [17:31] How do I modify the network bonding parameters without having to delete and recreate a bond? The MAAS GUI does not seem to provide a way to update the parameters. [17:32] Even the MAAS CLI does not seem to provide a way. For instance, all I need to do is changing the bonding mode from round robin to active backup [17:58] Bug #1655049 opened: [2.1] netaddr raises IndexError when looking up some OUI registrations [17:58] Bug #1655096 opened: MAAS CLI and GUI must provide a way to modify the bonding paramters [19:26] Hey guys. I am trying to deploy a node with MAAS, but the /var/lib/cloud/instance/scripts/user_data.sh script I run is reporting "request to http://10.20.21.245:5240/MAAS/metadata//2012-03-01/ failed. sleeping 32.: HTTP Error 401: OK [19:26] " errors. [19:26] Has anybody ever seen this? [19:27] This is happening during commissioning, not deploying. [19:29] The clock skew is getting adjusted by 0 and -1 so the times seem close enough === mup_ is now known as mup [21:16] Kildurin: Check out the command "maas my-profile interface update -h" You can update some bond parameters there [21:18] Kildurin: Note that the keywords for bond parameters should be with underscores (see https://bugs.launchpad.net/maas/+bug/1645319) [22:00] I am having issues with "MAAS Version 2.1.2+bzr5555-0ubuntu1 (16.04.1)" deploying CentOS 7 on Dell R710s. I have upgraded to the latest bios/firmware and it keeps Failing deployment. Error on the console is "Failed to start Execute cloud user/final scripts." Any idea on how to go about troubleshooting this issue? [22:01] Ubuntu installs without issues. [22:43] Bug #1655164 opened: no feedback when something's missing on manual enlistment [22:43] Bug #1655165 opened: manual node create dialog should disappear when the Save button is clicked [23:34] Bug #1655176 opened: [2.1.2] Power state could not be queried: Could not connect to BMC. Check BMC configuration and try again.