| g3 | Also if I commission and allow ssh access, the drives are there.... | 00:03 |
|---|---|---|
| roaksoax | g3: cool, I'll track it | 00:10 |
| roaksoax | g3: thanks | 00:10 |
| roaksoax | g3: what server is this? HP Gen9 ? | 00:15 |
| g3 | supermicro | 00:18 |
| mup | Bug #1660498 opened: ipv6 address in power parameters should not require [] <maas-ipv6> <MAAS:New> <https://launchpad.net/bugs/1660498> | 00:18 |
| g3 | The unfortunately side effect is, it was working up until the weekend | 00:18 |
| g3 | I had deployed the servers many times while sorting out the subnet. | 00:19 |
| jwitko | hey all, I'm trying to setup firewall rules for my MAAS server via IPTables and I'm wondering how MAAS is using iscsi? | 00:40 |
| jwitko | do I need to open iscsi ports ? | 00:40 |
| jwitko | using MAAS 2.1 btw | 00:40 |
| babbageclunk | ping mpontillo? | 02:35 |
| mpontillo | babbageclunk: hi there | 02:35 |
| babbageclunk | mpontillo: Hi! I'm trying to bootstrap juju to a kvm maas I have, but I needed to bump up the ram in the node I'm using as the controller. | 02:38 |
| babbageclunk | mpontillo: How can I get maas to see the new ram amount? | 02:39 |
| babbageclunk | mpontillo: Do I need to remove and recommission the machine? Or is there some easier way? | 02:41 |
| mpontillo | babbageclunk: recommissioning (without deleting it) /should/ work, but you can also use the API/CLI, such as "maas <profile> machine update <system_id> memory=4096" | 02:45 |
| babbageclunk | mpontillo: great, thanks! | 02:46 |
| mpontillo | np | 02:46 |
| junaidali | Hi guys, is the commissioning time out configurable? | 07:24 |
| junaidali | I'm emulating arm on x64, so vm is taking time while commissioning resulting into 'failed commissioning'. Any help will be much appreciated | 07:37 |
| === frankban|afk is now known as frankban | ||
| jlec__ | good morning | 08:42 |
| jlec__ | Is it possible to start a live CD or in live mode via Maas? | 08:42 |
| jlec__ | I'd to not alter the content on the disk for inspection and debugging? | 08:43 |
| brendand | jlec__, you can boot in 'rescue mode' which loads an ephemeral image (that is similar to a live cd) | 08:53 |
| jlec__ | brendand: true :) I tried that before | 08:54 |
| jlec__ | thanks | 08:54 |
| hachi | Hello | 09:22 |
| hachi | How i can connect a network interface to a fabric using CLI ? | 09:23 |
| brendand | hachi, you can link it to a subnet - that subnet will be associated with a fabric | 09:35 |
| hachi | brendand thank you for your answer, do you mean using the cmd: | 09:53 |
| hachi | maas $maas_profile interface link-subnet $system_id........ | 09:53 |
| hachi | ? | 09:53 |
| brendand | hachi, you also need to specify the interface id and the parameters. but yeah | 09:56 |
| hachi | brendand thank you, i will update my script to include your recommendations and see how it goes | 10:00 |
| netmonk | roaksoax: ok :) | 10:31 |
| netmonk | but something else ? | 10:31 |
| mup | Bug #1660589 opened: [Machine details page] In the interfaces list add parenthesis to the value Unconfigured for unconfigured Subnets <MAAS:New> <https://launchpad.net/bugs/1660589> | 11:30 |
| mup | Bug #1660592 opened: [Machine details page] In the machine summary change the term Unassigned to (Unassigned) for when the owner has not been assigned <MAAS:New> <https://launchpad.net/bugs/1660592> | 11:30 |
| mup | Bug #1660593 opened: [web UI] 2.2 DHCP Relay - Action 'disable dhcp' should be 'disable dhcp relay' <docteam> <MAAS:New> <https://launchpad.net/bugs/1660593> | 11:30 |
| jlec__ | I am trapped in "Failed to exit rescue mode". What Can I do there? | 11:39 |
| jlec__ | solved | 12:07 |
| mup | Bug #1660617 opened: unexpected string of length 1 <MAAS:New> <https://launchpad.net/bugs/1660617> | 13:15 |
| mup | Bug #1660617 changed: unexpected string of length 1 <MAAS:New> <https://launchpad.net/bugs/1660617> | 13:24 |
| mup | Bug #1660617 opened: unexpected string of length 1 <MAAS:New> <https://launchpad.net/bugs/1660617> | 13:27 |
| thiagolib | HI sameone already this error | 13:49 |
| thiagolib | Node commissioning failure - 'cloudinit' running config-ntp with frequency once-per-instance, in commissioning. I'm utilizing ubuntu 16.04 with MAAS Version 2.1.3 | 13:49 |
| roaksoax | thiagolib: smaybe your machi cannot access the archives to download ntp related stuff and configure it. | 14:01 |
| roaksoax | thiagolib: also see the actual log /var/log/maas/rsyslog/<mache-name>/<date>/messages -> that should give you more detail of what failed | 14:01 |
| mup | Bug #1660617 changed: unexpected string of length 1 <MAAS:Invalid> <https://launchpad.net/bugs/1660617> | 14:09 |
| mup | Bug #1660617 opened: unexpected string of length 1 <MAAS:Incomplete> <https://launchpad.net/bugs/1660617> | 15:09 |
| === zz_CyberJacob is now known as CyberJacob | ||
| mup | Bug #1660649 opened: [UX] Improve bulk actions - Break the Take action list with separator lines to improve the readability and discoverability of actions <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1660649> | 15:39 |
| thiagolib | roaksoax: Searching for the error in the messages file I found an excerpt saying that the file cc_ntp.py failed. | 17:29 |
| thiagolib | https://pastebin.ubuntu.com/23900491/ | 17:29 |
| roaksoax | thiagolib: #012Command: ['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold', '--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--quiet', 'update']#012Exit code: 100#012Reason: -#012Stdout: ''#012Stderr: '' | 18:29 |
| roaksoax | Jan 31 14:49:55 BOOTSTRAP [CLOUDINIT] stages.py[DEBUG]: Running module timezone (<module 'cloudinit.config.cc_timezone' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py'>) with frequency once-per-instance | 18:29 |
| roaksoax | thiagolib: that is leading me to believe that it was an issue with the apt-get command | 18:30 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1660743 opened: [2.1.3] Incorrect warning message in WebUI that MAAS is not providing DHCP even though DHCP enabled <oil> <MAAS:New> <https://launchpad.net/bugs/1660743> | 19:12 |
| capncrunch4me | Fresh maas install, running into connection error 111 | 19:18 |
| capncrunch4me | MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) | 19:18 |
| capncrunch4me | connection refused from any node trying to be provisioned up. Its a vanilla MAAS install | 19:19 |
| mup | Bug #1660754 opened: Connection Error 111 <MAAS:New> <https://launchpad.net/bugs/1660754> | 19:27 |
| capncrunch4me | so newest versions of maas dont listen on 5240 on IPV4 | 19:30 |
| roaksoax | capncrunch4me: maas always listens on 5240 | 19:33 |
| capncrunch4me | roaksoax: strangely I see it on netstat as tcp6, not on tcp | 19:34 |
| blake_r | capncrunch4me: can you do an "ip addr show | pastebinit" | 19:35 |
| blake_r | capncrunch4me: and a "cat /etc/maas/regiond.conf | pastebinit" | 19:36 |
| capncrunch4me | http://paste.ubuntu.com/23901090/ | 19:36 |
| mup | Bug #1660754 changed: Connection Error 111 <MAAS:Incomplete> <https://launchpad.net/bugs/1660754> | 19:36 |
| capncrunch4me | http://paste.ubuntu.com/23901092/ | 19:37 |
| blake_r | capncrunch4me: hmm got an ipv4 address, very strange | 19:37 |
| blake_r | capncrunch4me: and the maas_url is ipv4 based | 19:37 |
| blake_r | capncrunch4me: try "sudo systemctl restart maas-regiond maas-rackd" then do a netstat to see if listening on ipv4 | 19:37 |
| blake_r | lamont: ^ any thoughts? | 19:37 |
| capncrunch4me | hrmm | 19:38 |
| capncrunch4me | I dont want maas listening on public IP | 19:38 |
| capncrunch4me | I want it listening on all | 19:38 |
| capncrunch4me | nupe, tcp6 only | 19:39 |
| capncrunch4me | tcp6 0 0 :::5240 :::* LISTEN 7029/python3 | 19:39 |
| roaksoax | i think that's twisted's way of implementing things | 19:40 |
| blake_r | capncrunch4me: lamont is our ipv6 expert so I will have to defer to him on why its choosing not to open a socket on tcp4 socket | 19:40 |
| capncrunch4me | on latest maas, how do I reconfigure IP without having to modify each config by hand? | 19:41 |
| capncrunch4me | I would prefer that it communicate over my private IP, versus public | 19:41 |
| mup | Bug #1660754 opened: Connection Error 111 <MAAS:Incomplete> <https://launchpad.net/bugs/1660754> | 19:42 |
| roaksoax | capncrunch4me: sudo maas-rack config --help | 19:47 |
| roaksoax | sudo maas-region local_config_* | 19:47 |
| capncrunch4me | yeah, not sure what the local_config is | 19:52 |
| capncrunch4me | yeah, as is suspected there are waaaay too many bugs to use MAAS in production | 19:59 |
| capncrunch4me | we tried this with 1.8, 1.9 and now 2.1 | 19:59 |
| capncrunch4me | for instance, once you overcome one issue…like the IP address issue, then MAAS decides in commissioning to improperly report the impi address | 20:00 |
| capncrunch4me | is 2.0 more stable? | 20:01 |
| roaksoax | capncrunch4me: commissioning looks into the BMC and reports the IP address the BMC reports | 20:07 |
| capncrunch4me | well, it will pull IP | 20:10 |
| capncrunch4me | then it will release it | 20:10 |
| capncrunch4me | so I see BMC pull IP, I can ping that ip | 20:10 |
| capncrunch4me | then it stops responding | 20:10 |
| capncrunch4me | this isnt non-standard hardware | 20:10 |
| capncrunch4me | all HP general gear | 20:10 |
| capncrunch4me | DL380s | 20:10 |
| lamont | note that tcp6 means that it will accept connections from both ipv4 and ipv6 | 20:34 |
| g3 | hey roaksoax can I use the cli to erase a node? | 21:01 |
| g3 | a node that is in the ready state that is | 21:02 |
| g3 | Still addressing that no writable disks issue | 21:02 |
| roaksoax | g3: yes you can. You can do everything on the CLI | 21:10 |
| mup | Bug #1657285 changed: [UI] When editing a commissioned interface, you need to do it twice for the changes to take effect. <MAAS:Triaged> <https://launchpad.net/bugs/1657285> | 21:16 |
| g3 | roaksoax how do I do that? | 21:35 |
| g3 | maas erase NODE | 21:35 |
| mup | Bug # changed: 1185164, 1304857, 1355813, 1462514 | 21:40 |
| mup | Bug #1660810 opened: Clicking on username doesn't take me to the user page until I complete or skip the first use page <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1660810> | 21:40 |
| mup | Bug #1660812 opened: Admins should be able to manage keys for other users <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1660812> | 21:40 |
| === Vax is now known as Guest31505 | ||
| roaksoax | g3: maas <user> machine delete <system_id> | 21:49 |
| mup | Bug # changed: 1394367, 1446916, 1449033, 1459889, 1459890 | 21:52 |
| mup | Bug #1660819 opened: [2.1.3] webUI slows down to a crawl during windows image create <oil> <MAAS:New> <https://launchpad.net/bugs/1660819> | 21:52 |
| g3 | I'm thinking of erasing the disks on the node | 21:56 |
| g3 | So after poking through the code a bit. I think I tracked it down to line 122 in maasserver/storage_layout.py | 21:57 |
| g3 | As it thinkgs that there are no block_devices.. | 21:58 |
| g3 | That or line 175 in maasserver/storage_layout.py where it asserts that the boot_partition_table.table_type is a GPT partiton table. | 22:03 |
| g3 | As when I use an ubuntu live cd it things that the partition table is MS_DOS? | 22:03 |
| g3 | So I'll go in under rescue mode to poke around some more | 22:04 |
| roaksoax | ack | 22:07 |
| g3 | my thoughts exactly | 22:07 |
| g3 | Hmm yeah all of the partitions have a msdos Partition Table. Interesting | 22:11 |
| g3 | updatd the ticket | 22:15 |
| g3 | hmp | 23:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!