[11:25] <piyush> Hello friends
[11:26] <piyush> i am installing maas but when i run as localhost/maas and login then there is no "load image" option in images tab .
[11:27] <piyush> how can i deal with this error or load image manually
[11:57] <piyush> hello
[19:01] <TrXuk> hi @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 server
[19: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/tgtd
[19:02] <TrXuk> @blake_r however, still seeing exactly the same issue
[19:03] <TrXuk> @blake_r screenshot of dropping to initrd: https://www.dropbox.com/s/jezjjdhqplij5q9/Screenshot%202015-01-14%2019.00.14.JPG?dl=0
[19: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 install
[19:04] <blake_r> TrXuk: what does this show "sudo tgtadm --lld iscsi --mode target --op show"
[19:06] <TrXuk> @blake_r awesome, solaris command naming creeping into linux :P http://pastebin.com/AKXrKRav
[19:07] <blake_r> TrXuk: do you have a firewall between the node and the cluster?
[19:08] <TrXuk> Nope, physical Layer 2
[19:08] <TrXuk> @blake_r MaaS IP: 10.0.52.5/24, DHCP given to node direct from MaaS: 10.0.52.200/24
[19:08] <TrXuk>  tcp        0   4144 10.0.52.5:3260          10.0.52.200:54088       ESTABLISHED 1322/tgtd
[19:10] <TrXuk> root@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.0
[19:11] <blake_r> TrXuk: its wierd that the node is not able to connect to that iscsi target
[19:11] <TrXuk> @blake_r
[19:12] <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-* entries
[19:13] <blake_r> TrXuk: no actually its alittle differnet
[19:13] <blake_r> TrXuk: 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 image
[19:14] <TrXuk> But MaaS shows an established TCP session from the Node's IP to TGTD
[19:15] <TrXuk> and 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.200
[19: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:16] <TrXuk> @blake_r or anything else you can suggest? from a TCP standpoint as above, it looks like it sucessfully contacted tgtd
[19:17] <blake_r> TrXuk: yeah there, cant remember of the top my head
[19:17] <blake_r> TrXuk: list the contents of /scripts in the initramfs
[19:26] <TrXuk> local, functions, nfs
[19:26] <TrXuk> then dir's init-top, local-bottom, panic, local-premount, init-bottom, init-premount and local-top
[19:36] <blake_r> TrXuk: contents of local-top
[20:02] <TrXuk> @blake_r sorry for the delay. cryptopensc, ORDER, crypto, iscsi
[20:02] <blake_r> TrXuk: try /scripts/local-top/iscsi
[20:03] <TrXuk> ./iscsi ... Logging in, 10.0.52.5:3620... initiator reported error 15 - session exists
[20:03] <TrXuk> Tries twice
[23:34] <TrXuk> @blake_r got d/c
[23:41] <bmorriso> When 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:52] <blake_r> bmorriso: /etc/apt/apt.conf you will see a reference to the maas server
[23:52] <blake_r> as http proxy
[23:53] <blake_r> TrXuk: not in front of PC at moment to provide support, I can look more into tomorrow
[23:53] <bmorriso> I 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_r> ah there you go
[23:53] <blake_r> just delete that file
[23:54] <bmorriso> beautiful
[23:54] <bmorriso> Thank you very much!
[23:55] <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!