| somedude | echo | 02:18 |
|---|---|---|
| === Guest44232 is now known as zz_Guest44232 | ||
| mup | Bug #1498851 opened: [1.9.0 - alpha 1] Can't save power config <MAAS:Triaged> <https://launchpad.net/bugs/1498851> | 11:01 |
| mup | Bug #1498854 opened: [1.9.0 - alpha 1] cannot select power details on node details <MAAS:Triaged> <https://launchpad.net/bugs/1498854> | 11:01 |
| mup | Bug #1498899 opened: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 12:40 |
| mup | Bug #1498899 changed: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:16 |
| mup | Bug #1498899 opened: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:22 |
| mup | Bug #1498899 changed: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:28 |
| mup | Bug #1498899 opened: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:31 |
| mup | Bug #1498899 changed: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:34 |
| mup | Bug #1498899 opened: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:37 |
| mup | Bug #1498899 changed: [1.9.0 - alpha1] Can't delete node <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1498899> | 13:40 |
| === jfarschman is now known as MilesDenver | ||
| === jfarschman is now known as MilesDenver | ||
| === Sagar is now known as Guest45894 | ||
| Guest45894 | hi ... I have a MAAS cluster running 1.8.0 version, want to install OS on a physical server having a bunch of hard drives. I want control to install OS on a specific HDD | 14:24 |
| Guest45894 | currently, MAAS installs OS randomly | 14:24 |
| Guest45894 | any suggestions? | 14:25 |
| Guest45894 | #join | 14:26 |
| Guest45894 | I don't see anyone active on the list | 14:41 |
| bdx | hows it going everyone? | 17:56 |
| bdx | I have a concern about our production storage infrastructure that is deployed via maas/juju .... | 17:57 |
| bdx | I cannot seem to wrap my head around the process for replacing failed disks in a storage node deployed via MAAS...... is there anyone here who might have an idea on a best practice for disk failure/recovery without having to re-commission a node? | 17:59 |
| roaksoax | bdx: at the moment we don't support that without re-commissioning, but we are discussing such feature | 18:02 |
| roaksoax | bdx: although, you could always update the serial and such directly through the api | 18:10 |
| bdx | roaksoax: Is that what you do on large scale production deployments when a disk fails? | 18:28 |
| bdx | updating the serial directly only fixes 1/3 of the issue | 18:29 |
| bdx | good call on that....but it is no solution...just a heads up | 18:30 |
| roaksoax | bdx: as I said, It is just a work around not a solution | 18:31 |
| roaksoax | bdx: as we don't support that without re-commissioning | 18:31 |
| bdx | roaksoax: gotcha, thanks | 18:34 |
| mup | Bug #1499044 opened: [1.9.0 alpha2] Ready node has OS <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499044> | 18:56 |
| mup | Bug #1499047 opened: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:11 |
| mup | Bug #1499047 changed: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:14 |
| JZTech101 | Hi, so I have a MaaS controller in a VM. I am trying to get it to work with the other 2 VMs I have setup and prepared for Nodes. But PXE boot shows "No boot filename recieved". It should be noted. I have a host-only network specifically for the 2 nodes and the controller. There is a secondary host-only network for internet though that is also connected to all three VMs. | 19:19 |
| JZTech101 | Help? | 19:19 |
| JZTech101 | (the hypervisor is vmware fyi) | 19:22 |
| mup | Bug #1499047 opened: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:23 |
| mup | Bug #1499047 changed: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:29 |
| mup | Bug #1499050 opened: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499050> | 19:29 |
| mup | Bug #1499050 changed: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499050> | 19:32 |
| mup | Bug #1499047 opened: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:32 |
| mup | Bug #1499047 changed: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:35 |
| mup | Bug #1499050 opened: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499050> | 19:35 |
| mup | Bug #1499050 changed: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499050> | 19:38 |
| mup | Bug #1499047 opened: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:38 |
| mup | Bug #1499047 changed: [1.9.0 alpha2] Node stuck in deployment <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499047> | 19:41 |
| mup | Bug #1499050 opened: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1499050> | 19:41 |
| mwenning | JZTech101, did you run thru https://maas.ubuntu.com/docs/install.html | 19:57 |
| JZTech101 | yes | 19:59 |
| JZTech101 | I did | 19:59 |
| JZTech101 | I installed it using the Multi-Server Option on the CD | 19:59 |
| JZTech101 | The eth1 (Main host-only network is setup http://vgy.me/iHK8gK). I removed eth0 (the host-only internet network) from the cluster controller, but that has made no difference. | 20:00 |
| JZTech101 | pserv.log shows : | 20:00 |
| JZTech101 | 2015-09-23 15:31:03-0400 [Uninitialized] Event-loop ondria:pid=2000 (127.0.0.1:48076): Connection was refused by other side: 111: Connection refused. | 20:00 |
| JZTech101 | 2015-09-23 15:31:03-0400 [Uninitialized] Event-loop ondria:pid=2000 (1.1.1.39:48076): Connection was refused by other side: 111: Connection refused. | 20:00 |
| JZTech101 | and MaaS.log shows : | 20:00 |
| JZTech101 | Sep 23 15:28:08 ondria maas.lease_upload_service: [INFO] Uploading 0 DHCP leases to region controller. | 20:00 |
| JZTech101 | Sep 23 15:28:08 ondria maas.bootsources: [INFO] Updated boot sources cache. | 20:00 |
| JZTech101 | Sep 23 15:28:08 ondria maas.import-images: [INFO] Started importing boot images. | 20:00 |
| JZTech101 | Sep 23 15:28:08 ondria maas.bootresources: [INFO] Importing images from source: http://maas.ubuntu.com/images/ephemeral-v2/releases/ | 20:00 |
| JZTech101 | Sep 23 15:28:08 ondria maas.boot_image_download_service: [ERROR] Failed to download images: Unable to open http://1.1.1.39/images-stream/streams/v1/index.json. mirrors=[] | 20:01 |
| JZTech101 | Sep 23 15:28:09 ondria maas.bootresources: [INFO] Finished importing of boot images from 1 source(s). | 20:01 |
| JZTech101 | Sep 23 15:28:09 ondria maas.import-images: [INFO] Started importing boot images. | 20:01 |
| JZTech101 | Sep 23 15:28:09 ondria maas.import-images: [INFO] Finished importing boot images, the region does not have any new images. | 20:01 |
| JZTech101 | Sep 23 15:30:47 ondria maas.calls: [INFO] Starting task 'write_full_dns_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSForwardZoneConfig object at 0x7fc2bbc0b7d0>, <provisioningserver.dns.zoneconfig.DNSReverseZoneConfig object at 0x7fc2bbc0b910>], 'callback': provisioningserver.tasks.rndc_command([u'reload'], False), 'upstream_dns': [u'1.1.1.1'], 'trusted_networks': u'1.1.1.0/24; 1.1.2.0/24;'} | 20:01 |
| JZTech101 | Sep 23 15:30:47 ondria maas.calls: [INFO] Starting task 'rndc_command' with args: ([u'reload'], False) {} | 20:01 |
| JZTech101 | Sep 23 15:30:47 ondria maas.calls: [INFO] Finished task 'rndc_command' with args: ([u'reload'], False) {} | 20:01 |
| JZTech101 | Sep 23 15:30:47 ondria maas.calls: [INFO] Finished task 'write_full_dns_config' with args: () {'zones': [<provisioningserver.dns.zoneconfig.DNSForwardZoneConfig object at 0x7fc2bbc0b7d0>, <provisioningserver.dns.zoneconfig.DNSReverseZoneConfig object at 0x7fc2bbc0b910>], 'callback': provisioningserver.tasks.rndc_command([u'reload'], False), 'upstream_dns': [u'1.1.1.1'], 'trusted_networks': u'1.1.1.0/24; 1.1.2.0/24;'} | 20:01 |
| JZTech101 | Sep 23 15:30:48 ondria maas: [WARNING] Failed to create Network when adding/editing cluster interface maas-eth1 with error [{'ip': [u'Network with this Ip already exists.'], 'name': [u'Network with this Name already exists.']}]. This is OK if it already exists. | 20:01 |
| mup | Bug #1499062 opened: Internal Server Error if 'Sync URL' Setting has a preseeding whitespace <MAAS:Confirmed> <MAAS 1.8:New> <https://launchpad.net/bugs/1499062> | 20:14 |
| mwenning | JZTech101, click on clusters tab in maas gui, mine is called cluster master | 20:24 |
| JZTech101 | mwenning, yes. Mine is called cluster master as well | 20:25 |
| mwenning | I've got 2 interfaces, under the manage column, one says dhcp and dns | 20:25 |
| mwenning | the other one is unmanaged | 20:25 |
| JZTech101 | I only have one managed dhcp and dns. The other one that is managed by my router, I removed | 20:26 |
| JZTech101 | Should I uh add it back? | 20:26 |
| JZTech101 | removing it nor adding it has made a difference | 20:26 |
| mwenning | not yet ;-) | 20:26 |
| JZTech101 | ok | 20:27 |
| mwenning | interface is eth0? | 20:27 |
| JZTech101 | no eth1 | 20:27 |
| JZTech101 | eth0 is the one managed by router | 20:27 |
| mwenning | ok. what is eth1 set up as in virt-manager | 20:27 |
| JZTech101 | uh | 20:28 |
| JZTech101 | what | 20:28 |
| mwenning | Not using virt-manager? | 20:28 |
| JZTech101 | oh. I use vmware. Its a host-only network with no DHCP | 20:28 |
| mwenning | oh ok. | 20:29 |
| JZTech101 | oh and I should mention, the controller is a VM on its own as well its Nodes. But that shouldn't make a difference afaik | 20:29 |
| JZTech101 | (Controller + Nodes are side-by-side VMs) | 20:30 |
| mwenning | JZTech101, that's what I've got here using kvm/virt-manager | 20:30 |
| JZTech101 | ok | 20:30 |
| mwenning | Maas-server is set up as a static address, 172.16.0.1/22 | 20:32 |
| mwenning | Nodes should be set up to pxe boot from the same network of course | 20:32 |
| mwenning | maas-server should access the outside world on the other network | 20:33 |
| JZTech101 | uh. Static IP Address? I just uh thought that MaaS controller would handle configuring this new network adapter | 20:33 |
| JZTech101 | :| | 20:33 |
| mwenning | what's the network addr for eth1 on Interfaces | 20:34 |
| mwenning | Interfaces section of Cluster Controller | 20:35 |
| JZTech101 | 1.1.2.0/24 | 20:35 |
| JZTech101 | http://vgy.me/iHK8gK That's a screenshot of the interface config | 20:35 |
| mwenning | And you are accessing the maas server gui from 1.1.2.0 ? | 20:39 |
| JZTech101 | uh | 20:40 |
| JZTech101 | no actually | 20:40 |
| JZTech101 | I'm accessing it through eth0 | 20:40 |
| JZTech101 | mwenning, I have not gotten an IP from MaaS so I can't access that particular subnet. Actually the VM itself has no IP for that subnet | 20:42 |
| JZTech101 | o.O | 20:42 |
| JZTech101 | how to make MaaS properly assign IPs? | 20:42 |
| mwenning | ok, what I did was edit /etc/network/interfaces and add a static address for the internal maas network | 20:43 |
| mwenning | in youre case eth0 | 20:43 |
| mwenning | oops eth1 | 20:43 |
| JZTech101 | mwenning, can you give me an example config so I don't mess it up? | 20:44 |
| mwenning | sure stby | 20:44 |
| mup | Bug #1499050 changed: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1499050> | 20:45 |
| JZTech101 | Also, I changed the static IP field to 1.1.2.1 | 20:45 |
| JZTech101 | And left the router field the same (1.1.2.1) | 20:45 |
| mwenning | auto eth0 | 20:47 |
| mwenning | iface eth0 inet static | 20:47 |
| mwenning | address 172.16.0.1 | 20:47 |
| mwenning | broadcast 172.16.3.255 | 20:47 |
| mwenning | netmask 255.255.252.0 | 20:47 |
| mwenning | JZTech101, yeah that's the way mine's set up | 20:47 |
| JZTech101 | ok | 20:47 |
| mwenning | Try that. did you find the maas doc on setting the nodes to poweronoff using virsh? | 20:49 |
| JZTech101 | o.o | 20:49 |
| JZTech101 | why is the netmask 252.0? | 20:49 |
| JZTech101 | I always set it 255.0 | 20:49 |
| mwenning | maas 1.8 uses 2 sets of dhcp ranges, one for dynamic and another for static | 20:51 |
| mwenning | mine setup assigns 255 to each range | 20:51 |
| JZTech101 | uh | 20:52 |
| JZTech101 | wat? o.O | 20:52 |
| * JZTech101 is confused | 20:52 | |
| * mwenning tries to take a screenshot of his maas server | 20:55 | |
| JZTech101 | mwenning, ok. So eth1 now has an IP on the VM. But the DHCP Server is still not functioning as my host has yet to have an IP from MaaS | 20:55 |
| mup | Bug #1499050 opened: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1499050> | 20:57 |
| mwenning | JZTech101, try that http://vgy.me/DrEMup | 20:57 |
| mup | Bug #1499050 changed: [1.9.0 alpha2] can't access networks tab <ui> <ux> <MAAS:Won't Fix> <https://launchpad.net/bugs/1499050> | 21:00 |
| JZTech101 | uh mwenning I see your main IP is 0.1. Well.. the thing is, the router hands out IPs in the 1.1.1.x range. So would using 252.0 conflict? | 21:01 |
| mwenning | JZTech101, in your case probably. It's not important, this setup is for controlling big mass clusters, where we have 100's of nodes | 21:04 |
| mwenning | If you bring up another node on the internal maas network, can you ping the maas server? | 21:04 |
| === zz_Guest44232 is now known as CyberJacob | ||
| JZTech101 | mwenning, well its not a node. Its just another device. And no. it is not getting an IP from the MaaS server :( | 21:07 |
| JZTech101 | so it cannot ping the MaaS server | 21:07 |
| JZTech101 | Imma brb for dinner | 21:08 |
| mwenning | JZTech101, ok | 21:08 |
| mwenning | JZTech101, I'm gonna have to bail soon too. Try this doc: http://certification-static.canonical.com/docs/MAAS_Advanced_NUC_Installation_And_Configuration.pdf | 21:12 |
| mwenning | That's the way I set up mine. It assumes real hw but it worked fine from the MAAS_server VM | 21:13 |
| mwenning | When you get that working you will have to set the nodes up to boot from virsh, see https://maas.ubuntu.com/docs/nodes.html | 21:16 |
| JZTech101 | mwenning, still around? | 21:54 |
| mwenning | JZTech101, yup, can you reach that document? | 21:55 |
| JZTech101 | mwenning, I can indeed. And the setup script, I'm not entirely sure how to get it seeing as I did a MAAS install direct from the Server CD | 21:56 |
| JZTech101 | rather than on an existing install | 21:56 |
| JZTech101 | but that might be what is lacking with the DHCP Server not working? | 21:57 |
| JZTech101 | :O | 21:58 |
| JZTech101 | mwenning, hmm. Ok, so its just the host being stupid. I can't blame it. But Netboot seems to be working now | 21:58 |
| JZTech101 | :D | 21:58 |
| JZTech101 | hm | 21:58 |
| JZTech101 | mass-enlisting node eh? | 21:58 |
| JZTech101 | :o | 21:58 |
| mwenning | it's working now? | 21:59 |
| mwenning | rephrasing, it's pxebooting now? | 21:59 |
| JZTech101 | it is pxebooting now :D | 22:00 |
| mwenning | |\o/ | 22:00 |
| mwenning | Nodes go thru 3 phases, enlisting, commissioning, and deploying | 22:01 |
| mwenning | enlist they pxeboot and make themselves known to MAAS | 22:01 |
| mwenning | commission they will pxe boot again and collect system info | 22:01 |
| mwenning | deploy they will pxeboot, load an image on the disk, and reboot to the disk. | 22:02 |
| JZTech101 | hm | 22:03 |
| JZTech101 | how do I tell it to deploy the image? | 22:03 |
| mwenning | after enlist you will have to set up the virsh thing above, since maas assumes that it can control power to the node for commission and deploy | 22:03 |
| JZTech101 | I only have one Ubuntu LTS | 22:03 |
| JZTech101 | lol | 22:03 |
| mwenning | on the node page on the maas gui, the enlisting node should show up as "New" | 22:04 |
| JZTech101 | uh | 22:04 |
| mwenning | then you click in there and edit the power settings | 22:04 |
| JZTech101 | how do I setup virsh if the controller itself is a VM alongside the other VMs? | 22:04 |
| JZTech101 | and how do I do that in VMWare | 22:05 |
| mwenning | hmm. I googled 'maas virsh vmware' and 'maas vmware power type' and got some hits :-O | 22:10 |
| mwenning | Also you can be the power controller - hit commission and then manually turn on the vm | 22:11 |
| JZTech101 | Yeah I know | 22:11 |
| JZTech101 | thats actually what I'm doing right now | 22:11 |
| JZTech101 | lol | 22:11 |
| mwenning | ok well that will work its just a PITA | 22:11 |
| * JZTech101 shrugs | 22:12 | |
| JZTech101 | the problem is, afaik vmware workstation does not support Wake-On-Lan | 22:13 |
| JZTech101 | and none of the others will work because it is a VM alongside VMs | 22:13 |
| JZTech101 | The host is not the controller | 22:13 |
| JZTech101 | this is fun | 22:13 |
| JZTech101 | it is deploying | 22:13 |
| JZTech101 | :D | 22:13 |
| JZTech101 | Thanks for your help mwenning :D | 22:14 |
| mwenning | JZTech101, np. thanks for your patience :-) | 22:14 |
| JZTech101 | hm | 22:26 |
| JZTech101 | mwenning, is there anything special I need to do to get the ssh-keys working? Basically I added the wrong key After deploying the node. So I have redeploy the node or something? | 22:27 |
| JZTech101 | (I've already changed it to the correct SSH Key | 22:27 |
| mwenning | This is for power control? | 22:29 |
| JZTech101 | uh no. | 22:29 |
| JZTech101 | I'm just trying ot access this new node | 22:30 |
| JZTech101 | lol | 22:30 |
| * mwenning is still thinking virsh | 22:30 | |
| catbus1 | you will have to re-deploy so the new key gets set up on the deployed node after the install. | 22:31 |
| mwenning | I would expect so. I think the key is passed during deployment so you can ssh into the node without a password | 22:31 |
| mwenning | what catbus1 said ;-) | 22:31 |
| JZTech101 | :( | 22:31 |
| JZTech101 | ok | 22:31 |
| JZTech101 | was hoping it would automatically update | 22:31 |
| mwenning | that's the cool thing about vm's it doesn't take 20 minutes like real hw | 22:32 |
| JZTech101 | Also | 22:33 |
| JZTech101 | Why am I getting 14.04.1? | 22:33 |
| JZTech101 | 14.04.3 has long been out | 22:34 |
| JZTech101 | :< | 22:34 |
| mwenning | enlist or commission? | 22:34 |
| JZTech101 | commission? | 22:34 |
| mwenning | the pxeboot images are still 14.04.1, once you get to the real image on the hd (in deploy), you should see 14.04.3 | 22:35 |
| JZTech101 | ah | 22:35 |
| JZTech101 | o.O | 22:40 |
| JZTech101 | hey mwenning what am I doing wrong? I put the public SSH Key in there. (the .pub file). And I still can't connect. I'm using owner as the username. Should I use something else? | 22:41 |
| JZTech101 | hm. Apparently I should | 22:42 |
| mwenning | ssh ubuntu@mynode | 22:42 |
| JZTech101 | the user is ubuntu | 22:42 |
| JZTech101 | well its deployed and it says "Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64) | 22:44 |
| JZTech101 | " | 22:44 |
| === CyberJacob is now known as zz_CyberJacob | ||
| catbus1 | I had a fresh maas install and configuration on Monday, and the imported image is 14.04.3 on my maas. | 22:46 |
| catbus1 | JZTech101: what your maas version? | 22:46 |
| catbus1 | not that I think it's related, but would be good to know. | 22:46 |
| JZTech101 | uh | 22:47 |
| JZTech101 | where do I get the version? | 22:47 |
| catbus1 | apt-cache policy maas | 22:47 |
| catbus1 | if you are using maas 1.8, you should see maas version on the bottom left of the maas webpage | 22:47 |
| JZTech101 | Installed: 1.7.6+bzr3376-0ubuntu2~14.04.1 | 22:48 |
| JZTech101 | o.O | 22:48 |
| JZTech101 | I installed from a Server CD I downloaded today | 22:49 |
| JZTech101 | ;_; | 22:49 |
| catbus1 | 1.7.6 is good | 22:50 |
| catbus1 | wait, 14.04.1 but with newer kernel 3.13, your node is using 14.04.1 user space and 3.13 kernel, the same kernel version as in 14.04.3. | 22:51 |
| catbus1 | JZTech101: I used MAAS to deploy a node and it comes up the same as you are seeing. | 22:56 |
| catbus1 | JZTech101: the other node 14.04.3 I have, I used juju to deploy, so I guess after the install, it might do apt-get dist-upgrade. | 22:56 |
| catbus1 | sorry, I was wrong about the kernel version in 14.04.3, it is 3.19. It is 3.13 in 14.04.1. | 23:01 |
| catbus1 | JZTech101: so I did apt-get dist-upgrade on the MAAS deployed node, and now it comes up 14.04.3 with 3.13.0-35 kernel. | 23:01 |
| JZTech101 | ah ok | 23:17 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!