| mup | Bug #1686244 opened: [web UI] Storage modification message is confusing <docteam> <MAAS:New> <https://launchpad.net/bugs/1686244> | 00:18 |
|---|---|---|
| mup | Bug #1686246 opened: [CLI help] set-storage-layout says Allocated when it should say Ready <docteam> <MAAS:New> <https://launchpad.net/bugs/1686246> | 00:18 |
| mup | Bug #1686248 opened: Node configuration user collisions are possible <docteam> <MAAS:New> <https://launchpad.net/bugs/1686248> | 00:49 |
| === haasn is now known as hanna | ||
| mup | Bug #1686412 opened: Add ability to change PXE boot behavior of a device <MAAS:Triaged> <https://launchpad.net/bugs/1686412> | 14:02 |
| vasey | mpontillo: i installed python3-pyvmomi, and i'm getting this message when i try to connect : "Error:__init__() takes 1 positional argument but 2 were given" | 14:37 |
| vasey | as well as a "power error" message when i try to check the power state | 14:37 |
| vasey | mpontillo: and now i'm seeing that certificate error in my events log for that node: https://pastebin.com/eYzdxecn | 15:03 |
| xygnal | mpontillo: I see a code merge for our problem. is that still being tested? its quite small so tempted to apply it to ours and see if we can verify the results | 15:37 |
| roaksoax | xygnal: i just uploaded to a ppa, if you wanna test from there ? | 15:54 |
| roaksoax | xygnal: but if you give us some time to test that'd be good | 15:57 |
| xygnal | roaksoax what kind of time are you looking for to incorporate this into RC3 and release it? We have about 3 weeks time before we need to be ready for prod deployments and we want to be sure this is wrapped up. | 16:08 |
| roaksoax | xygnal: it is already in RC3 milestone | 16:11 |
| roaksoax | just need to test it first | 16:11 |
| roaksoax | before I can say there's no regressions | 16:11 |
| xygnal | roaksoax what is the *goal* date for RC3 release? | 16:11 |
| xygnal | what are you aiming for | 16:11 |
| roaksoax | xygnal: we are targetting a release for the end of the week. It may be final or it may be rc3 | 16:12 |
| xygnal | roaksoax thanks much. | 16:12 |
| mup | Bug #1623851 changed: Tables not responsive for mobile <ui> <MAAS:Fix Released> <https://launchpad.net/bugs/1623851> | 17:44 |
| mup | Bug #1686464 opened: [2.2, API] set-storage-layout fails silently when invoked by a non-admin <api> <api-ux> <docteam> <MAAS:Triaged> <https://launchpad.net/bugs/1686464> | 17:44 |
| mpontillo | xygnal: I think patching your setup with the diff from that merge proposal would be a low-risk thing to do. please do give it a try. | 17:52 |
| xygnal | mpontillo: thanks, will test it out this week. | 17:52 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1686485 opened: cc_ntp fails to work when deploying ubuntu-core <cloud-init:New> <MAAS:Triaged> <https://launchpad.net/bugs/1686485> | 18:59 |
| mary_ | hello I have a problem with maas, for some reason, the rack controller fails | 20:26 |
| mary_ | theyre both on the same machine | 20:26 |
| mary_ | can anyone help me | 20:29 |
| catbus1 | mary_: first post the error message please | 20:29 |
| mary_ | there's no error message just a red cross on the gui in front of the rack controller | 20:30 |
| roaksoax | mary_: go to the rack controller, and see the status of it | 20:30 |
| roaksoax | does it show why it is red ? | 20:30 |
| mary_ | on the images status it says region importing and on the boot images status tab it says out of sync | 20:31 |
| mary_ | I dont get it, I did configure the url | 20:34 |
| mary_ | and I did the same steps I did before but last time, it worked | 20:35 |
| mup | Bug #1686516 opened: [2.2, trunk] Pod remote storage listing shows blank for pods with out remote storage <MAAS:In Progress by blake-rouse> <https://launchpad.net/bugs/1686516> | 21:05 |
| xygnal | mpontillo: that works, final address is correct | 21:34 |
| xygnal | mpontillo new problem. observed address does not go away, so system keeps booting old temporary address, | 21:34 |
| xygnal | will that fix itself when temporary lease expires? | 21:34 |
| xygnal | hm... | 21:35 |
| mup | Bug #1646847 changed: Multi interface issue while charm deployed on centos image <cloud-images:New> <juju:Invalid> <MAAS:Won't Fix> <https://launchpad.net/bugs/1646847> | 21:35 |
| mup | Bug #1658718 changed: MAAS 2.1.3 Centos 7 image deployment fails <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1658718> | 21:35 |
| roaksoax | xygnal: is the machine set as 'dynamic' or is it set as 'auto assign' ? | 21:35 |
| roaksoax | xygnal: and what do you mean by keeps booting ? | 21:36 |
| xygnal | ah, sorry bad phrasing. DHCP-aquires the old dynamic range address | 21:36 |
| xygnal | if you look in that subnets view, you can see that same node has an observed address and automatic address | 21:36 |
| xygnal | observed is the dynamic | 21:37 |
| roaksoax | xygnal: that will clear itself automatically | 21:37 |
| xygnal | yes but wasnt that 2 hours? | 21:37 |
| xygnal | for the default expire | 21:37 |
| roaksoax | xygnal: the dynamic range expires 10 minutes | 21:37 |
| xygnal | oh wow ok, understood | 21:38 |
| roaksoax | xygnal: what may be failing is dhcp tells maas about a lease expiring | 21:38 |
| roaksoax | and maas removes that from tracking | 21:38 |
| roaksoax | xygnal: but has the deployed machine been successfully configuired ? | 21:38 |
| xygnal | roaksoax maas has correct config, but node boots up with build IP instead of its assigned IP. | 21:45 |
| xygnal | shutting them down for 10 minutes, power off | 21:45 |
| xygnal | to verify that clears | 21:45 |
| roaksoax | xygnal: if e/n/i is configured w/ static IP address, how will it boot from an address it gets from dhcp ? | 21:45 |
| xygnal | I suspect the pre-existing lease is not given a chance to expire | 21:45 |
| xygnal | auto-assign | 21:46 |
| xygnal | your auto-assign is static dhcp, if I recall correctly | 21:46 |
| roaksoax | xygnal: auto-assign will configure /etc/network/interfaces with 'iface X inet static' | 21:46 |
| roaksoax | dhcp will configure /e/n/i w/ 'iface X inet dhcp' | 21:46 |
| xygnal | then its NOT compatibe with a custom image, which I could have sworn mpontillo steered me the other way pon | 21:46 |
| roaksoax | xygnal: is this an Ubuntu custom image? | 21:47 |
| xygnal | CentOS only for us | 21:47 |
| xygnal | cloud-init enabled image | 21:47 |
| roaksoax | ah right | 21:47 |
| roaksoax | so MAAS doesn't yet support network config for centos images | 21:47 |
| roaksoax | but it will do soon | 21:48 |
| xygnal | alright I thought that before, but somehow got a mixed message | 21:48 |
| roaksoax | that said | 21:48 |
| roaksoax | MAAS adds a hostmap | 21:48 |
| xygnal | then we go back to my plan before that | 21:48 |
| xygnal | which was using DHCP but changing the IP after deploy (Via post-script) to a reserved range address | 21:49 |
| roaksoax | xygnal: so if eth0 - auto-assign, MAAS will add a hostmap for eth0's MAC + IP assigned by MAAS | 21:49 |
| roaksoax | xygnal: but, unless isc-dhcp is ignoring the hostmap | 21:49 |
| xygnal | hm... what will this hostmap result in? | 21:49 |
| roaksoax | xygnal: the hostmap should result in the machine obtaining the IP as per 'auto-assign' and not form dynamic range | 21:50 |
| roaksoax | xygnal: if you do dhclient on your system for eth0... does it get the right IP ? | 21:50 |
| xygnal | roaksoax: no, it gets the dynamic/observed ip | 21:50 |
| xygnal | roaksoax but in the UI it has an auto-assigned address in the proper range for auto-assign | 21:51 |
| xygnal | roaksoax: if that is not supported, why does it pick an auto assign? | 21:51 |
| wasosa | Hi all. I'm looking for some help deploying a node with maas (just upgraded to 2.1.5+bzr5596-0ubuntu1~16). Though the web UI tells me the node is 'Ready', it also warns me: No storage information. Commissioning this node will gather the storage information. | 21:51 |
| xygnal | I would expect to be told NO | 21:51 |
| roaksoax | xygnal: check your isc-dhcp config | 21:51 |
| roaksoax | xygnal: you should see the hostmap there | 21:52 |
| roaksoax | xygnal: /var/lib/maas/dhcpd.conf | 21:52 |
| roaksoax | xygnal: my guess is that isc dhcp is preferring the address from the dynamic range rather than tha hostmap address | 21:52 |
| roaksoax | xygnal: what if you clean your leases file ? | 21:52 |
| roaksoax | xygnal: try cleaning the leases file, then force the interface to re-obtain an IP from isc-dhcp and see if it gets the right address ? | 21:53 |
| xygnal | roaksoax yes | 21:53 |
| xygnal | there is a host map | 21:53 |
| xygnal | I powered the nodes down in the hope that the 10 minute lease woud expire | 21:53 |
| xygnal | if a lease is already alive, a new hostmap wont matter will it? or should the old lease be overridden? | 21:54 |
| xygnal | confirmed observed lease is gone | 21:55 |
| xygnal | powered back up | 21:55 |
| wasosa | Hi all. I'm looking for some help deploying a node with maas (just upgraded to 2.1.5+bzr5596-0ubuntu1~16). The web UI tells me the node is 'Ready', but warns me: No storage information. Commissioning this node will gather the storage information. As best as I can tell, the block-device output is good. The only hits I found with similar problems had to do with vms rather than real hardware (I'm attempting to deploy an Intel SkullCanyon | 22:03 |
| wasosa | I'd appreciate any help anyone can provide. Thanks! | 22:03 |
| roaksoax | xygnal: did it get new IP ? | 22:05 |
| roaksoax | wasosa: that means that no storage was discovered during commissioning | 22:05 |
| roaksoax | wasosa: do you have any specific storage in this machine? | 22:06 |
| xygnal | roaksoax I seem to be a little confused, i was testing two boxes. Back just one now. I dont seem to have a hostmap in dhcpd despite deploying as auto-assign | 22:06 |
| xygnal | there is a hostmap in there for another build that *I* did not build, i am checking to see if that one was different somehow | 22:06 |
| wasosa | roaksoax: Yes, the machine has one nvme drive, and it looks like that's showing up properly in the 00-maas-07-block-devices.out listed under 'Machine output' | 22:08 |
| wasosa | roaksoax: (thanks for jumping in, btw) | 22:08 |
| roaksoax | wasosa: are you commissioning with Xenial? go to the settings page, to the commissioning section, and select xenial for commissioning | 22:09 |
| wasosa | roaksoax: yes I am, that secion reads: Default Ubuntu release used for commissioning: Ubuntu 16.04 LTS "Xenial Xersus" (and I can't change it). | 22:11 |
| wasosa | roaksoax: the output of the block devices caputred during commissioning looks sane to me, but I haven't been able to find the problem yet. I can share that output here if you'd like. | 22:15 |
| xygnal | roaksoax: think i found the problem. its pxe booting them. not sure why its responding to taht, as they are 'deployed' status. | 22:17 |
| mpontillo | xygnal: currently MAAS will always respond to a PXE boot, but if the machine is deployed the PXE boot payload will instruct the node to boot from its local disk | 22:23 |
| xygnal | mpontillo: I will verify that behavior, ty | 22:24 |
| mpontillo | xygnal: when the node PXE boots it should receive the IP address assigned via the static lease installed by auto-assignment | 22:24 |
| xygnal | mpontillo: that it does not, bit the implied host map in dhcpd.conf is not there either | 22:25 |
| xygnal | despite that, its in deployed status | 22:25 |
| xygnal | and has an Assigned up | 22:25 |
| xygnal | IP* | 22:25 |
| xygnal | yes i just booted local HD | 22:25 |
| xygnal | same result | 22:25 |
| xygnal | there is no hostmap so there is no static entry | 22:25 |
| xygnal | i do see one that was build yesterday pre-fix that now suddenly has correct addrwess | 22:26 |
| xygnal | and is working | 22:26 |
| xygnal | we are slowing down for the day so, we'll do some more exhaustive testing on this and report back tomorrow. thanks for the help. | 22:26 |
| mpontillo | xygnal: thanks; I'd investigate if the DHCP configuration is not being properly updated when the IP address is assigned, then. thanks for your testing! | 22:27 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!