You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There is an issue with upgrading RabbitMQ component on Ubuntu. It looks like a problem with erlang dependencies.
Recently there was a fix for RabbitMQ installation, but it didn't affect the upgrade process.
As for me, the upgrade role requires some refactoring, so that during the upgrade it uses the installation tasks from the
RabbitMQ role (as it is for Grafana).
How to reproduce
Steps to reproduce the behavior:
Deploy a 0.6/0.7/0.8 cluster with RabbitMQ component enabled
Upgrade the cluster to 0.9/develop
Expected behavior
The cluster has been upgraded successfully.
Environment
Cloud provider: [AWS | Azure | Any]
OS: [Ubuntu]
Log:
2021-01-13T16:23:26.9096088Z[38;21m16:23:26 INFO cli.engine.ansible.AnsibleCommand - TASK [upgrade : RabbitMQ | Upgrade packages] ***********************************[0m
2021-01-13T16:23:27.8953809Z[31;21m16:23:27 ERROR cli.engine.ansible.AnsibleCommand - fatal: [ci-07to09azubflannel-rabbitmq-vm-0]: FAILED! => {"cache_update_time": 1610555007, "cache_updated": true, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\" install 'erlang-eldap=1:23.1.*' 'erlang-inets=1:23.1.*' 'erlang-os-mon=1:23.1.*' 'erlang-public-key=1:23.1.*' 'erlang-ssl=1:23.1.*' 'rabbitmq-server=3.8.9*'' 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 erlang-eldap : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or\n erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-asn1 (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n erlang-inets : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or\n erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-ftp (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-mnesia (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n Depends: erlang-runtime-tools (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n Depends: erlang-tftp (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n erlang-os-mon : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or\n erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-mnesia (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n Depends: erlang-snmp (= 1:23.1.4-1) but it is not going to be installed\n erlang-public-key : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or\n erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-asn1 (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n Depends: erlang-crypto (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n erlang-ssl : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or\n erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed\n Depends: erlang-crypto (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed\n Depends: erlang-runtime-tools (= 1:23.1.4-1) but 1:21.3.8.18-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:", " erlang-eldap : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or", " erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-asn1 (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " erlang-inets : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or", " erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-ftp (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-mnesia (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " Depends: erlang-runtime-tools (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " Depends: erlang-tftp (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " erlang-os-mon : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or", " erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-mnesia (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " Depends: erlang-snmp (= 1:23.1.4-1) but it is not going to be installed", " erlang-public-key : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or", " erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-asn1 (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " Depends: erlang-crypto (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " erlang-ssl : Depends: erlang-base (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed or", " erlang-base-hipe (= 1:23.1.4-1) but it is not going to be installed", " Depends: erlang-crypto (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed", " Depends: erlang-runtime-tools (= 1:23.1.4-1) but 1:21.3.8.18-1 is to be installed"]}
The text was updated successfully, but these errors were encountered:
Describe the bug
There is an issue with upgrading RabbitMQ component on Ubuntu. It looks like a problem with erlang dependencies.
Recently there was a fix for RabbitMQ installation, but it didn't affect the upgrade process.
As for me, the upgrade role requires some refactoring, so that during the upgrade it uses the installation tasks from the
RabbitMQ role (as it is for Grafana).
How to reproduce
Steps to reproduce the behavior:
Expected behavior
The cluster has been upgraded successfully.
Environment
Log:
The text was updated successfully, but these errors were encountered: