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

[cdh-prodigy] Update Failing with Unmet Dependencies Error #5665

Closed
kayiwa opened this issue Dec 24, 2024 · 1 comment
Closed

[cdh-prodigy] Update Failing with Unmet Dependencies Error #5665

kayiwa opened this issue Dec 24, 2024 · 1 comment
Assignees
Labels
Operations pulls issues into the Operations ZenHub board

Comments

@kayiwa
Copy link
Member

kayiwa commented Dec 24, 2024

We are encountering the following error while running our periodic update on cdh-prodigy1.princeton.edu and cdh-prodigy2.princeton.edu:

fatal: [cdh-prodigy1.princeton.edu]: FAILED! => {"changed": false, "msg": "'/usr/bin/apt-get dist-upgrade ' failed: E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).\n", "rc": 100, "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nYou might want to run 'apt --fix-broken install' to correct these.\nThe following packages have unmet dependencies:\n python3.12-venv : Depends: python3.12 (= 3.12.8-1+jammy1) but 3.12.7-1+jammy1 is installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "You might want to run 'apt --fix-broken install' to correct these.", "The following packages have unmet dependencies:", " python3.12-venv : Depends: python3.12 (= 3.12.8-1+jammy1) but 3.12.7-1+jammy1 is installed"]}

fatal: [cdh-prodigy2.princeton.edu]: FAILED! => {"changed": false, "msg": "'/usr/bin/apt-get dist-upgrade ' failed: E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).\n", "rc": 100, "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nYou might want to run 'apt --fix-broken install' to correct these.\nThe following packages have unmet dependencies:\n python3.12-venv : Depends: python3.12 (= 3.12.8-1+jammy1) but 3.12.7-1+jammy1 is installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "You might want to run 'apt --fix-broken install' to correct these.", "The following packages have unmet dependencies:", " python3.12-venv : Depends: python3.12 (= 3.12.8-1+jammy1) but 3.12.7-1+jammy1 is installed"]}

It appears that the python3.12-venv package requires python3.12 version 3.12.8-1+jammy1, but version 3.12.7-1+jammy1 is currently installed. This is causing a dependency conflict and preventing the dist-upgrade from completing successfully.

Steps to Investigate and Resolve:

  1. Manual Investigation:
  • SSH into cdh-prodigy1.princeton.edu and cdh-prodigy2.princeton.edu.
  • Run apt --fix-broken install as suggested by the error message. This command will attempt to automatically resolve the dependency issues.
  • If the issue persists, try manually installing the required version of python3.12:
sudo apt-get install python3.12=3.12.8-1+jammy1
  • Check for any other potential dependency conflicts or errors.
  1. Update Script Review:

Re-run the os_updates.yml playbook to ensure it is correctly handling dependencies and package upgrades.

@dphillips-39 dphillips-39 added the Operations pulls issues into the Operations ZenHub board label Jan 22, 2025
@dphillips-39
Copy link
Contributor

dphillips-39 commented Jan 22, 2025

Actions Taken:
SSH'd into cdh-prodigy1.princeton.edu and cdh-prodigy2.princeton.edu.
Installed the required Python 3.12 version (confirmed installation of the required version).
Used sudo apt --fix-broken install to resolve the dependency issue and ensure the system was using the correct Python version (3.12.8-1+jammy1
Re-ran the playbook to apply necessary updates:
ansible-playbook playbooks/os_updates.yml -e runtime_env=cdh-prodigy1.princeton.edu.
Monitored the playbook run for errors and confirmed successful execution with no errors.

Post-Actions:
Verified system and package status after playbook execution to check that all updates applied successfully.
Ran final checks using sudo apt list --upgradable and sudo apt --fix-broken install to confirm there were no remaining issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Operations pulls issues into the Operations ZenHub board
Projects
None yet
Development

No branches or pull requests

2 participants