search

conjure-up / spells

conjure-up spells registry
79 stars 37 forks source link

spells with spark fail with lxd/localhost provider #130

Closed chrisheckler closed 6 years ago

chrisheckler commented 6 years ago

Per https://github.com/juju-solutions/bigtop/issues/52, any spells that deploy spark fail when deployed using the lxd provider.

adam-stokes commented 6 years ago

Ah this needs an updated lxd profile like what we do with kubernetes and openstack-novlaxd spells

adam-stokes commented 6 years ago

I'll see if I can look at it tonight

chrisheckler commented 6 years ago

fyi, after more testing, looks like it may be zookeeper and spark that throw the error

adam-stokes commented 6 years ago

Thanks for the additional information, I'll see what I can find

chrisheckler commented 6 years ago

@battlemidget @kwmonroe following further investigation I found this in the log https://paste.ubuntu.com/26388694/

Possibly my modem is handing out domains that aren't resolvable.

Here is some insight from inside one of the failing juju deployed containers

ubuntu@juju-65cf08-1:~$ cat /etc/hostname
juju-65cf08-1
ubuntu@juju-65cf08-1:~$ cat /etc/hosts
127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
ubuntu@juju-65cf08-1:~$ hostname
juju-65cf08-1
ubuntu@juju-65cf08-1:~$ hostname -f
hostname: Name or service not known

ubuntu@juju-65cf08-1:~$ host juju-65cf08-4.hsd1.or.comcast.net
Host juju-65cf08-4.hsd1.or.comcast.net not found: 3(NXDOMAIN)
ubuntu@juju-65cf08-1:~$ host juju-65cf08-4.hsd1.or.comcast.net 10.0.0.1
Using domain server:
Name: 10.0.0.1
Address: 10.0.0.1#53
Aliases: 

juju-65cf08-4.hsd1.or.comcast.net has address 10.0.0.55

Going to see if modifying dns server to that of 10.0.0.1 fixes, I have a feeling it will.

Update: looks as if the comcast modem doesn't support modifying dns for the local subnet ... oh well, its time for some network upgrades anyway.

Thanks for your help/insight, you can close this issue if you like!

jamesbeedy commented 6 years ago

this is https://github.com/juju-solutions/jujubigdata/issues/62

kwmonroe commented 6 years ago

Yeah @battlemidget, you can close this out. It's being tracked in jujubigdata since the underlying problem is with dns in big data clusters.