New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scylla_setup: Cannot get driver information: No such device #3658

Closed
tzach opened this Issue Aug 5, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@tzach
Contributor

tzach commented Aug 5, 2018

Installation details
Scylla version (or git commit hash): 2.2
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): CentOS on AWS, i3.4xlarge

scylla_setup prompt for Amazon EC2 configuration check and return with a Cannot get driver information: No such device error

$ sudo scylla_setup
Skip any of the following steps by answering 'no'
Do you want to run Amazon EC2 configuration check?
Answer yes to have this script verify that current instance configuration is optimized for running Scylla; answer no to skip this check.
[YES/no]
Cannot get driver information: No such device
cat: /sys/class/net/eth0/address: No such file or directory
VPC is not enabled!
To enable enhanced networking, please enable VPC.
@syuu1228

This comment has been minimized.

Contributor

syuu1228 commented Aug 6, 2018

Seems like duplicated with #3584, but it only fixed on master & branch-2.3 (python version), not backported branch-2.2 (bash version). So will send a fix for branch-2.2

avikivity added a commit that referenced this issue Aug 8, 2018

dist/common/scripts/scylla_ec2_check: support custom NIC ifname on EC2
This is bash version of commit 88fe3c2.

Since some AMIs using consistent network device naming, primary NIC
ifname is not 'eth0'.
But we hardcoded NIC name as 'eth0' on scylla_ec2_check, we need to add
--nic option to specify custom NIC ifname.

Fixes #3658

Signed-off-by: Takuya ASADA <syuu@scylladb.com>
Message-Id: <20180807231650.13697-1-syuu@scylladb.com>

@tzach tzach added this to the 2.3 milestone Aug 9, 2018

@tzach

This comment has been minimized.

Contributor

tzach commented Aug 9, 2018

@syuu1228 can we close this issue?

@syuu1228

This comment has been minimized.

Contributor

syuu1228 commented Aug 10, 2018

@tzach Yes, 6fca92a should fix the issue.

@tzach tzach closed this Aug 12, 2018

@powellchristoph

This comment has been minimized.

powellchristoph commented Aug 30, 2018

I ran into this today with version 2.2.0-0.20180705.240b9f122-0ubuntu1~xenial.

It says this was fixed and backported into 2.2. Has a new build been released?

@tzach

This comment has been minimized.

Contributor

tzach commented Sep 2, 2018

@powellchristoph it will be part of the next 2.2.x release, 2.2.1
Hopefully in a few weeks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment