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

Need Help with setting up all the modules on a single server and issues with pacemaker cluster manager system pcs #2

Open
engineerprincipal opened this issue May 25, 2017 · 0 comments

Comments

@engineerprincipal
Copy link

May I request your help with setting up all the modules on a single server with 64 cores.

  1. I am running the setup as local 127.0.0.1 for all hosts. Then I started as
    ~/mechaphish/setup $ ansible-playbook -i inventory/mechaphish/hosts setup.yml -b -vvv --connection=local --extra-vars "ansible_sudo_pass=Password1!"
    After the ansible-playbook CMD, it setup kubernetes nodes and it run OK for 165 steps and got failed while setting up the virtual IPs in setup.yml. I keep getting issues with the PCS pacemaker cluster manager system setup. Please see the error snippet.

  2. If I would like to run the whole module on a single large server, how will I do it?

Your help is very much appreciated.
Regards,
Aron

TASK [virtual-ip : Install packages] ***************************************************************************************************
task path: /home/user1/mechaphish/setup/roles/virtual-ip/tasks/main.yml:2
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/packaging/os/apt.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: user1
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=qteynaqimumzdopdqolalbepszcxwkcw] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-qteynaqimumzdopdqolalbepszcxwkcw; /usr/bin/python'"'"' && sleep 0'
failed: [127.0.0.1] (item=pcs) => {
"cache_update_time": 1495664661,
"cache_updated": false,
"failed": true,
"invocation": {
"module_args": {
"allow_unauthenticated": false,
"autoremove": null,
"cache_valid_time": 0,
"deb": null,
"default_release": null,
"dpkg_options": "force-confdef,force-confold",
"force": false,
"install_recommends": null,
"name": "pcs",
"only_upgrade": false,
"package": [
"pcs"
],
"purge": false,
"state": "latest",
"update_cache": null,
"upgrade": null
}
},
"item": "pcs",
"msg": "'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" install 'pcs'' failed: E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n",
"stderr": "E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n",
"stderr_lines": [
"E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution)."
],
"stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\npcs is already the newest version.\nYou might want to run 'apt-get -f install' to correct these:\nThe following packages have unmet dependencies:\n libruby2.3 : Depends: rake (>= 10.4.2) but it is not going to be installed\n Depends: ruby-did-you-mean (>= 1.0) but it is not installable\n Depends: ruby-minitest (>= 5.4) but 5.2.1-1 is to be installed\n Depends: ruby-net-telnet (>= 0.1.1) but it is not installable\n Depends: ruby-test-unit (>= 3.0.8~) but it is not going to be installed\n Depends: libncurses5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed\n Depends: libreadline7 (>= 6.0) but it is not installable\n Depends: libssl1.0.2 (>= 1.0.2d) but it is not installable\n Depends: libtinfo5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed\n pcs : Depends: python2.7 (>= 2.7.9) but 2.7.6-8ubuntu0.3 is to be installed\n Recommends: pacemaker (>= 1.1.12) but it is not going to be installed\n ruby-rpam-ruby19 : Depends: ruby (>= 1:2.30)\n",
"stdout_lines": [
"Reading package lists...",
"Building dependency tree...",
"Reading state information...",
"pcs is already the newest version.",
"You might want to run 'apt-get -f install' to correct these:",
"The following packages have unmet dependencies:",
" libruby2.3 : Depends: rake (>= 10.4.2) but it is not going to be installed",
" Depends: ruby-did-you-mean (>= 1.0) but it is not installable",
" Depends: ruby-minitest (>= 5.4) but 5.2.1-1 is to be installed",
" Depends: ruby-net-telnet (>= 0.1.1) but it is not installable",
" Depends: ruby-test-unit (>= 3.0.8
) but it is not going to be installed",
" Depends: libncurses5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed",
" Depends: libreadline7 (>= 6.0) but it is not installable",
" Depends: libssl1.0.2 (>= 1.0.2d) but it is not installable",
" Depends: libtinfo5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed",
" pcs : Depends: python2.7 (>= 2.7.9) but 2.7.6-8ubuntu0.3 is to be installed",
" Recommends: pacemaker (>= 1.1.12) but it is not going to be installed",
" ruby-rpam-ruby19 : Depends: ruby (>= 1:2.3~0)"
]
}
Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/packaging/os/apt.py
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=jimsijnupllbhytltkagdrdgvxavyuai] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-jimsijnupllbhytltkagdrdgvxavyuai; /usr/bin/python'"'"' && sleep 0'
ok: [127.0.0.1] => (item=fence-agents) => {
"cache_update_time": 1495664661,
"cache_updated": false,
"changed": false,
"invocation": {
"module_args": {
"allow_unauthenticated": false,
"autoremove": null,
"cache_valid_time": 0,
"deb": null,
"default_release": null,
"dpkg_options": "force-confdef,force-confold",
"force": false,
"install_recommends": null,
"name": "fence-agents",
"only_upgrade": false,
"package": [
"fence-agents"
],
"purge": false,
"state": "latest",
"update_cache": null,
"upgrade": null
}
},
"item": "fence-agents"
}
to retry, use: --limit @/var/home/hyasin/mechaphish/setup/setup.retry

PLAY RECAP *****************************************************************************************************************************
127.0.0.1 : ok=165 changed=12 unreachable=0 failed=1

Myts2 added a commit to Myts2/setup that referenced this issue May 15, 2018
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

1 participant