jaytaylor / shipbuilder

The Open-source self-hosted Platform-as-a-Service written in Go

Home Page:https://shipbuilder.gigawatt.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Creating new node cannot create zpool

brockhaywood opened this issue · comments

When attempting to create a new node like so:

./install/node.sh -H sb-node7a -d /dev/xvdb -s /dev/xvdc install

I get the following error:

info: installLxc() succeeded
info: attempting to unmount /mnt and /dev/xvdb to be safe
info: existing fs type on /dev/xvdb is ext4
info: formatting /dev/xvdb with zfs
invalid vdev specification
use '-f' to override the following errors:
/dev/xvdb is part of potentially active pool 'tank'
error: command 'sudo zpool create -o ashift=12 tank /dev/xvdb' exited with non-zero status 1
error: remote prepareNode() invocation exited with non-zero status 1

If I don't specify the swap device, i get a different error:

./install/node.sh -H sb-node7a -d /dev/xvdb install
info: auto-detected shipbuilder host: ubuntu@sb
info: auto-detected lxc filesystem: zfs
info: auto-detected zfs pool: tank
info: verifying ssh and sudo access for 2 hosts
info: testing host ubuntu@sb .. succeeded
info: testing host sb-node7a .. succeeded
....
sent 80 bytes received 20 bytes 28.57 bytes/sec
total size is 31289 speedup is 312.89
error: prepareNode() missing required zfs parameter: $zfsPool
error: remote prepareNode() invocation exited with non-zero status 1

The relevant env nodes are:

$ cat env/LXC_FS
zfs
brock ~/dev/sendhub/shipbuilder [master*]
$ cat env/ZFS_POOL
tank

Any ideas?

When you created the node on EC2, how many ephemeral devices did you
allocate and to what /dev/xvd* device are they mapped to?

On Thu, Dec 5, 2013 at 4:52 PM, brockhaywood notifications@github.comwrote:

When attempting to create a new node like so:

./install/node.sh -H sb-node7a -d /dev/xvdb -s /dev/xvdc install

I get the following error:

info: installLxc() succeeded
info: attempting to unmount /mnt and /dev/xvdb to be safe
info: existing fs type on /dev/xvdb is ext4
info: formatting /dev/xvdb with zfs
invalid vdev specification
use '-f' to override the following errors:
/dev/xvdb is part of potentially active pool 'tank'
error: command 'sudo zpool create -o ashift=12 tank /dev/xvdb' exited with
non-zero status 1
error: remote prepareNode() invocation exited with non-zero status 1

If I don't specify the swap device, i get a different error:

./install/node.sh -H sb-node7a -d /dev/xvdb install
info: auto-detected shipbuilder host: ubuntu@sb
info: auto-detected lxc filesystem: zfs
info: auto-detected zfs pool: tank
info: verifying ssh and sudo access for 2 hosts
info: testing host ubuntu@sb .. succeeded
info: testing host sb-node7a .. succeeded
....
sent 80 bytes received 20 bytes 28.57 bytes/sec
total size is 31289 speedup is 312.89
error: prepareNode() missing required zfs parameter: $zfsPool
error: remote prepareNode() invocation exited with non-zero status 1

The relevant env nodes are:

$ cat env/LXC_FS
zfs
brock ~/dev/sendhub/shipbuilder [master*]
$ cat env/ZFS_POOL
tank

Any ideas?


Reply to this email directly or view it on GitHubhttps://github.com//issues/7
.

The node actually was unresponsive so it was restarted.

Root device
/dev/sda1
Lifecycle normal
Block devices
/dev/sda1
/dev/sdb

After a node restart you don't need to reinstall anything. All that is
rquired is to re-mount the ZFS volume.

IIRC, the command is something along the lines of:

sudo zpool import tank

On Thu, Dec 5, 2013 at 5:04 PM, brockhaywood notifications@github.comwrote:

The node actually was unresponsive so it was restarted.

Root device
/dev/sda1
Lifecycle normal
Block devices
/dev/sda1
/dev/sdb


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-29955007
.

That's it! Thank you!