/srv/irclogs.ubuntu.com/2017/05/11/#maas.txt

mupBug #1688354 opened: Race Condition in umount_partition() When Cleaning Up Loop Device <MAAS:New> <MAAS Image Builder:New> <https://launchpad.net/bugs/1688354>00:36
mupBug #1688354 changed: Race Condition in umount_partition() When Cleaning Up Loop Device <MAAS:New> <MAAS Image Builder:New> <https://launchpad.net/bugs/1688354>00:39
mupBug #1688354 opened: Race Condition in umount_partition() When Cleaning Up Loop Device <MAAS:New> <MAAS Image Builder:New> <https://launchpad.net/bugs/1688354>00:42
mupBug #1688354 changed: Race Condition in umount_partition() When Cleaning Up Loop Device <MAAS:New> <MAAS Image Builder:New> <https://launchpad.net/bugs/1688354>00:45
mupBug #1688354 opened: Race Condition in umount_partition() When Cleaning Up Loop Device <MAAS:New> <MAAS Image Builder:New> <https://launchpad.net/bugs/1688354>00:48
=== frankban|afk is now known as frankban
martijn1234hey there! I've got a question... I've looked at the MAAS 2.1 API docs and accessed the API itself but I can't figure out what format its returning... the /api/2.0/version/ endpoint returns json, but the rest seems to be returning some sort of binary format?12:00
martijn1234Or is this a stupid question? :p12:02
martijn1234apparently its python pickle format12:40
=== mup_ is now known as mup
=== frankban is now known as frankban|afk
sanjayhi13:10
sanjayi need help regarding deployment of nodes via maas13:12
mupBug #1690144 opened: Failed talking to pod: int() argument must be a string, a bytes-like object or a number, not 'NoneType' <MAAS:New> <https://launchpad.net/bugs/1690144>13:13
mupBug #1689603 changed: virsh pod creation fails with pre-existing machines <MAAS:New> <https://launchpad.net/bugs/1689603>13:43
sanjayhi14:00
roaksoaxsanjay: please ask your question and someone who can help will reply14:15
mupBug #1690154 opened: block-curtin-poweroff doesn't work <MAAS:Incomplete> <https://launchpad.net/bugs/1690154>14:16
sanjayyes14:21
sanjayafter curtin installation its gets stucked14:21
vasey_mpontillo: i'm past that issue now, though when I try to deploy ubuntu 17.04 i boot to a gnu grub bootloader with a "Local" option that doesn't have anything present14:29
vasey_a manual installation of ubuntu works fine, but maas' deployment doesn't work14:30
roaksoaxsanjay: can you be a bit mroe specific ? the machine finishes curtin install, reboots, but then iut doesn't boot into the OS ?14:31
roaksoaxvasey_: that could be a grub issue, but if I follow, you deploy, the machine is marked as deployed but it doesn't boot ?14:32
roaksoaxvasey_: or it doesn't boot after restart ?14:32
vasey_the status will remain "Deploying", it'll restart but won't boot into ubuntu post-installation, which appears to work14:33
roaksoaxvasey_: that seems like a efi related issue14:33
vasey_it does. i've seen a message regarding "shimx64.efi" not being found, which looks like is related to secure boot, though that's disabled on my servers14:34
roaksoaxvasey_: do you have the latest firmware ? I do recall someone a couple weeks ago mentioning that upgrading their frimware fixed that for them14:35
roaksoaxvasey_: that said, I also have 1 machine which i have not yet looked at fuilly that I changed from legacy to EFI that doesn't boot, experiencing exactly the same as you are14:36
roaksoaxvasey_: but the other amchines (which are exactly the same type_ do work fine14:36
roaksoaxvasey_: but I was messing with the bios config14:36
roaksoaxso i think it must be bios/firmware14:36
* roaksoax tries to deploy 7.0414:37
vasey_roaksoax: thanks, i'll look into that now14:40
sanjaythe machine finishes curtin install, reboots, but then iut doesn't boot into the OS ? yes15:16
sanjayI have already delpoyed one node with same environment, but others are not getting deployed15:16
sanjayInstallation complete - Node disabled netbootThu, 11 May. 2017 15:13:09 PXE Request - installationThu, 11 May. 2017 14:45:5819:16
sanjayafter this failed to deployed19:16
roaksoaxsanjay: that means that the install process continued fine, but the machine rebooted and didn't contact MAAS to say "i'm actually deploed"19:25
roaksoaxsanjay: do you have a console log19:25
roaksoaxor any logs we can see to determine what may be wrong ?19:25
roaksoaxvasey_: let me know if that makes any difference19:25
roaksoaxvasey_: fwiw, i successfully deployed 17.04 on EFI with secure boot disabeld19:26
sanjayno logs are also coming19:28
sanjayjust it shows failed deployment19:28
roaksoaxsanjay: do you have console logs ?19:30
roaksoaxsanjay: what about the full node event log ?19:30
sanjayi have full node event log19:33
sanjayMay 11 19:13:11 vtnode-04 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="2001" x-info="http://www.rsyslog.com"] exiting on signal 15.19:33
sanjaythis is last line..after that nothing...19:33
shewlessHi. I've been using maas 2 for awhile now and I'm a big fan.  I have the need to add some new nodes and I want them to pxe off of a different interface then normal.  If I add maas to the appropriate fabric and "enable" dhcp on that vlan associated with that fabric will everything work like magic?19:34
shewlessCan I have 2 interfaces responding to DHCP/PXE or only 1?19:35
shewlessI think the "maas_url" in regiond and rackd is going to hose me.. because it's an IP that the new nodes won't have access to19:36
shewlesscan I make the maas_url a dns name instead of an ip?19:36
shewlessor can I add multiple entries?19:36
sanjayQueried node's BMC - Power state queried: onThu, 11 May. 2017 15:38:53 Node changed status - From 'Deploying' to 'Failed deployment'Thu, 11 May. 2017 15:38:32 Marking node failed - Machine operation 'Deploying' timed out after 60 minutes.19:41
roaksoaxsanjay: the node failed to boot19:46
roaksoaxsanjay: after initial disk installation was completed19:46
roaksoaxsanjay: for that, can you get console logs ?19:46
roaksoaxshewless: yes you can make it a dns name19:46
roaksoaxshewless: you can have the rack provide dhcp on multiple vlans for sure too, but again, the region needs to be accessible for the machines19:47
roaksoaxshewless: because the machines access directly to the region to gather metadata19:47
shewlessroaksoax: thanks. is there anyway to make the region listen on multiple IPs?19:48
roaksoaxshewless: the region can listen on multiple IP's, but maas_url on rackd.conf is the IP your machines will be told to access19:48
roaksoaxshewless: so you can either use a dns name, or you can use a VIP that is reacheable for all the machines19:48
shewlessroaksoax: hmm. yeah the dns name thing probably won't work because I would have to make it two different IPs depending on the server that's booting19:49
shewlessmaybe I could do a VIP.. kind of a weird scenario though19:50
=== frankban|afk is now known as frankban
shewlessso I could install HA proxy on my maas server19:53
shewlessthen it could listen on both IPs and forward to localhost19:54
shewlessor rather.. forward to the maas_url?19:54
roaksoaxshewless: yes you could also do that19:54
shewlesseither way my nodes are going to try and directly hit maas_url though.. for the metadata right?19:55
roaksoaxyes19:56
roaksoaxshewless: they will all hit maas_url if they are under the same rack19:56
shewlessroaksoax: Another option I have is to remove the "old" IP and just add the new one since all of my nodes will have an IP and fabric on the new one19:56
shewlessif I change the maas_url to a new IP.. will I break my existing nodes?19:57
shewlessfor example will they stay "deployed" .. and if I reboot will they successfully boot from the hard drive?19:57
roaksoaxshewless: yes the machines will stay deployed20:03
roaksoaxshewless: i dont see why it should create other issues20:03
roaksoaxit is only really used for the deployment process20:03
roaksoax(and commissioning, etc)20:03
shewlessroaksoax: thanks for the info.20:03
shewlessmaas is awesome!20:04
roaksoax:) thank you!20:04
sanjayany suggestions21:06
sanjayi have removed and reinstalled maas to but still facing same issue21:06
mupBug #1443519 changed: when bind reloading is locking, regiond complete blocks. <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1443519>21:10
mupBug #1688359 changed: Unable to power on machine on commissioning. <MAAS:Incomplete> <https://launchpad.net/bugs/1688359>21:10
roaksoaxsanjay: check /etc/rackd.conf , does it have under maas_url an IP address that the machine you are deploying can contact ?21:12
roaksoaxsanjay: apart from that, without a console log, there's not much I can do to see what may be wrong21:12
mupBug #1690231 opened: MAAS auto-assigned gateway IP, while not allowing to reserve IP's in subnets. <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1690231>21:43
sanjayHi Roaksoax,  i have checked /etc/rackd.conf , there is http://MASSIP:5240/MAAS21:55
sanjayyes they can ping maas server, get dhcp ip21:56
sanjayQueried node's BMC - Power state queried: onThu, 11 May. 2017 17:39:38 TFTP Request - libutil.c32Thu, 11 May. 2017 17:39:30 TFTP Request - libcom32.c32Thu, 11 May. 2017 17:39:29 TFTP Request - chain.c32Thu, 11 May. 2017 17:39:29 PXE Request - local bootThu, 11 May. 2017 17:39:2921:56
sanjayafter this is will do Queried node's BMC - Power state queried:21:57
sanjayand then get failed deployment21:57
=== frankban is now known as frankban|afk
mupBug #1690256 opened: [2.1.5] Commissioning fails using 14.04 due to invalid lsblk option <MAAS:New> <https://launchpad.net/bugs/1690256>23:05

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!