Skip to content
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 fails on Oracle Linux Artifact: OS variant not recognized #6761

Closed
ShlomiBalalis opened this issue Jul 5, 2020 · 3 comments
Closed

Comments

@ShlomiBalalis
Copy link

Installation details
Scylla version (or git commit hash): 666.development-0.20200704.8e3ecc30a9d
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): ami-0d6a24fe35fdf5dc4
Instance Type: i3.large

The oel-76 artifact test fails when executing the scylla_setup script:

Command: 'sudo /usr/lib/scylla/scylla_setup --nic eth0 --disks /dev/nvme0n1 '

Exit code: 1

Stdout:

ESC[1;32mThis EC2 instance is optimized for Scylla.ESC[0m
This is a supported kernel version.
OS variant not recognized
scylla-jmx package is not installed.

Stderr:

WARN  2020-07-04 23:55:38,790 [shard 0] iotune - Available space on filesystem at /var/tmp/mnt: 124 MB: is less than recommended: 10 GB
INFO  2020-07-04 23:55:38,790 [shard 0] iotune - /var/tmp/mnt passed sanity checks

Logs:

+------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                          Log links for testrun with test id 5a4c273d-ca70-4a06-aa8e-ab036c9c0cba                                           |
+-----------------+------------+-----------------------------------------------------------------------------------------------------------------------------+
| Date            | Log type   | Link                                                                                                                        |
+-----------------+------------+-----------------------------------------------------------------------------------------------------------------------------+
| 20200704_225549 | db-cluster | https://cloudius-jenkins-test.s3.amazonaws.com/5a4c273d-ca70-4a06-aa8e-ab036c9c0cba/20200704_225549/db-cluster-5a4c273d.zip |
| 20200704_225549 | sct-runner | https://cloudius-jenkins-test.s3.amazonaws.com/5a4c273d-ca70-4a06-aa8e-ab036c9c0cba/20200704_225549/sct-runner-5a4c273d.zip |
+-----------------+------------+-----------------------------------------------------------------------------------------------------------------------------+
@syuu1228
Copy link
Contributor

syuu1228 commented Jul 6, 2020

Okay I found why it fails, I was misunderstood how distro package works, it seems distro.id() is NOT always same output as ID in /etc/os-release.
On /etc/os-release, OEL is ID="ol", but distro.id() returns oracle:

[vagrant@localhost ~]$ /opt/scylladb/python3/bin/python3
Python 3.8.3 (default, May 15 2020, 00:00:00) 
[GCC 10.1.1 20200507 (Red Hat 10.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import distro
>>> distro.id()
'oracle'

syuu1228 added a commit to syuu1228/scylla that referenced this issue Jul 6, 2020
It seems distro.id() is NOT always same output as ID in /etc/os-release.
We need to replace "ol" to "oracle", "amzn" to "amazon".

Fixes scylladb#6761
@avikivity
Copy link
Member

No vulnerable release.

@avikivity
Copy link
Member

@penberg why is the promoter re-adding the backport candidate label?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants