/srv/irclogs.ubuntu.com/2015/01/14/#maas.txt

piyushHello friends11:25
piyushi am installing maas but when i run as localhost/maas and login then there is no "load image" option in images tab .11:26
piyushhow can i deal with this error or load image manually11:27
piyushhello11:57
=== jfarschman is now known as MilesDenver
=== roadmr is now known as roadmr_afk
=== jfarschman is now known as MilesDenver
=== alexpilotti_ is now known as alexpilotti
=== roadmr_afk is now known as roadmr
TrXukhi @blake_r Re-installed 10.14 from scratch as a new MaaS following the install documentation here: https://maas.ubuntu.com/docs1.7/install.html Same issue persists. Can see that the node to enlist does sucessfully connect to iSCSI tgtd on the MaaS server19:01
TrXuk@blake_r tcp        0      0 0.0.0.0:3260            0.0.0.0:*               LISTEN      1322/tgtd        tcp        0   4144 10.0.52.5:3260          10.0.52.200:54088       ESTABLISHED 1322/tgtd19:01
TrXuk@blake_r however, still seeing exactly the same issue19:02
TrXuk@blake_r screenshot of dropping to initrd: https://www.dropbox.com/s/jezjjdhqplij5q9/Screenshot%202015-01-14%2019.00.14.JPG?dl=019:03
TrXuk@blake_r still looks very much like the bug @ https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1391354 . Just don't know why I'm the only one running into it from the default install19:03
ubot5Launchpad bug 1391354 in maas-images "Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more" [Undecided,Confirmed]19:03
blake_rTrXuk: what does this show "sudo tgtadm --lld iscsi --mode target --op show"19:04
TrXuk@blake_r awesome, solaris command naming creeping into linux :P http://pastebin.com/AKXrKRav19:06
blake_rTrXuk: do you have a firewall between the node and the cluster?19:07
TrXukNope, physical Layer 219:08
TrXuk@blake_r MaaS IP: 10.0.52.5/24, DHCP given to node direct from MaaS: 10.0.52.200/2419:08
TrXuk tcp        0   4144 10.0.52.5:3260          10.0.52.200:54088       ESTABLISHED 1322/tgtd19:08
TrXukroot@maas1:~# ping 10.0.52.200 PING 10.0.52.200 (10.0.52.200) 56(84) bytes of data. 64 bytes from 10.0.52.200: icmp_seq=1 ttl=64 time=0.134 ms 64 bytes from 10.0.52.200: icmp_seq=2 ttl=64 time=0.161 ms 64 bytes from 10.0.52.200: icmp_seq=3 ttl=64 time=0.146 ms ^C --- 10.0.52.200 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.134/0.147/0.161/0.011 ms root@maas1:~#  arp -a ? (10.019:10
blake_rTrXuk: its wierd that the node is not able to connect to that iscsi target19:11
TrXuk@blake_r19:11
TrXuk@blake_r i'm still not 100% sure it's unable to connect... The bug report still seems to match excatly... Ie, if i look right now in the (initramfs) shell, ls /dev/disk/by-path has no ip-* entries19:12
blake_rTrXuk: no actually its alittle differnet19:13
blake_rTrXuk: its a network issue with the node not able to connect to the iscsi target running on the cluster, not a missing permission or file issue in the image19:13
TrXukBut MaaS shows an established TCP session from the Node's IP to TGTD19:14
TrXukand the TGT output you recommended shows connection 0 and the source IP of the PXEbooted node in question:  I_T nexus: 1             Initiator: maas-enlist alias: maas-enlist             Connection: 0                 IP Address: 10.0.52.20019:15
TrXuk@blake_r is there anything in the initrd shell in terms of binaries that could help me debug further? like manually trying the iscsi initiator again?19:15
TrXuk@blake_r or anything else you can suggest? from a TCP standpoint as above, it looks like it sucessfully contacted tgtd19:16
blake_rTrXuk: yeah there, cant remember of the top my head19:17
blake_rTrXuk: list the contents of /scripts in the initramfs19:17
TrXuklocal, functions, nfs19:26
TrXukthen dir's init-top, local-bottom, panic, local-premount, init-bottom, init-premount and local-top19:26
blake_rTrXuk: contents of local-top19:36
TrXuk@blake_r sorry for the delay. cryptopensc, ORDER, crypto, iscsi20:02
blake_rTrXuk: try /scripts/local-top/iscsi20:02
TrXuk./iscsi ... Logging in, 10.0.52.5:3620... initiator reported error 15 - session exists20:03
TrXukTries twice20:03
TrXuk@blake_r got d/c23:34
bmorrisoWhen I try and do an apt-get update, it uses the MAAS IP as a mirror, but in /etc/apt/sources.list it has archive.ubuntu.com -- after the box was provisioned, it no longer has access to MAAS, so how do I stop it from trying to use the MAAS box as an apt mirror?23:41
blake_rbmorriso: /etc/apt/apt.conf you will see a reference to the maas server23:52
blake_ras http proxy23:52
blake_rTrXuk: not in front of PC at moment to provide support, I can look more into tomorrow23:53
bmorrisoI have /etc/apt.conf.d/90-curtin-aptproxy but no /etc/apt/apt.conf it has Acquire::HTTP::Proxy "http://ip.of.maas:8000/";23:53
blake_rah there you go23:53
blake_rjust delete that file23:53
bmorrisobeautiful23:54
bmorrisoThank you very much!23:54
TrXuk@blake_r works for me, thanks for your help on this one. Learning more about MaaS than I really wanted to ;)... but i guess thats never a bad thing!23:55

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