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 node role: Ubuntu 20, if I select 2021.1.8 and in repo the latest is 2021.1.9 I can't get 2021.1.8 installed #102

Closed
tarzanek opened this issue Mar 1, 2022 · 4 comments · Fixed by #125 or #130

Comments

@tarzanek
Copy link
Collaborator

tarzanek commented Mar 1, 2022

Error seen:

10:12:36 fatal: [scylla-stage-us-central1-c-1]: FAILED! => {"cache_update_time": 1646125910, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\"       install 'scylla-enterprise=2021.1.8*'' failed: E: Unable to correct problems, you have held broken packages.\n", "rc": 100, "stderr": "E: Unable to correct problems, you have held broken packages.\n", "stderr_lines": ["E: Unable to correct problems, you have held broken packages."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n scylla-enterprise : Depends: scylla-enterprise-server (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed\n                     Depends: scylla-enterprise-jmx (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed\n                     Depends: scylla-enterprise-tools (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed\n                     Depends: scylla-enterprise-tools-core (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed\n                     Depends: scylla-enterprise-kernel-conf (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " scylla-enterprise : Depends: scylla-enterprise-server (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed", "                     Depends: scylla-enterprise-jmx (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed", "                     Depends: scylla-enterprise-tools (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed", "                     Depends: scylla-enterprise-tools-core (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed", "                     Depends: scylla-enterprise-kernel-conf (= 2021.1.8-0.20220106.fcdf103fd-1) but 2021.1.9-0.20220208.86e3ea4df-1 is to be installed"]}
@tarzanek
Copy link
Collaborator Author

tarzanek commented Apr 7, 2022

see https://github.com/scylladb/scylla-enterprise/issues/2176
and use pinning workaround from it for specified version

@tarzanek
Copy link
Collaborator Author

alt. way besides pinning:

using dpkg get dependencies of meta package scylla-server
and then install all listed packages with explicit versions

@vladzcloudius
Copy link
Collaborator

Another option is to use aptitude. We already install a few additional packages we need so maybe installing aptitude would be so much of an issue if it would save us the hacking you need to do today.

Or use dpkg directly - someone said that it may be resolving dependencies better than apt.

@tarzanek
Copy link
Collaborator Author

tarzanek added a commit to tarzanek/scylla-ansible-roles that referenced this issue Jun 23, 2022
tarzanek added a commit to tarzanek/scylla-ansible-roles that referenced this issue Jun 23, 2022
vladzcloudius pushed a commit that referenced this issue Jun 24, 2022
* Debian: get versioning of scylla package working with role

fixes #102
@vladzcloudius vladzcloudius reopened this Jun 25, 2022
vladzcloudius added a commit to vladzcloudius/scylla-ansible-roles that referenced this issue Jun 28, 2022
Fixes scylladb#102

Signed-off-by: Vlad Zolotarov <vladz@scylladb.com>
vladzcloudius added a commit to vladzcloudius/scylla-ansible-roles that referenced this issue Jun 28, 2022
Fixes scylladb#102

Signed-off-by: Vlad Zolotarov <vladz@scylladb.com>
vladzcloudius added a commit to vladzcloudius/scylla-ansible-roles that referenced this issue Jun 28, 2022
Fixes scylladb#102

Signed-off-by: Vlad Zolotarov <vladz@scylladb.com>
vladzcloudius added a commit to vladzcloudius/scylla-ansible-roles that referenced this issue Jun 29, 2022
This patch fixes for the 'installation' and the 'upgrade' paths.
The corresponding code is moved into a separate tasks file:
Debian_install.yml; and used from both locations.

Fixes scylladb#102

Signed-off-by: Vlad Zolotarov <vladz@scylladb.com>
vladzcloudius added a commit that referenced this issue Jun 29, 2022
This patch fixes for the 'installation' and the 'upgrade' paths.
The corresponding code is moved into a separate tasks file:
Debian_install.yml; and used from both locations.

Fixes #102

Signed-off-by: Vlad Zolotarov <vladz@scylladb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment