Project

General

Profile

Bug #10745

Vagrant up failing for devmode

Added by Abhishek Lekshmanan about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

I'm not sure if this is because of a misconfiguration somewhere.. but doing a vagrant up --provider=kvm throws the following error for me. The full logs are available at http://git.io/bcsF

Complete.  Now run:
 1. `CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize`
 2. supervisord -c dev/supervisord.conf -n
[INFO    ] {'pid': 11091, 'retcode': 0, 'stderr': '', 'stdout': 'Calamari repo is at: /home/vagrant/calamari, user is vagrant, venv /home/vagrant/calamari/env\nWriting /home/vagrant/calamari/dev/etc/salt/master\nWriting /home/vagrant/calamari/dev/calamari.conf\nWriting /home/vagrant/calamari/dev/alembic.ini\nWriting /home/vagrant/calamari/tests/test.conf\nComplete.  Now run:\n 1. `CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize`\n 2. supervisord -c dev/supervisord.conf -n'}
[INFO    ] Completed state [source /home/vagrant/calamari/env/bin/activate && dev/configure.py] at time 12:08:22.862266
[INFO    ] Running state [source /home/vagrant/calamari/env/bin/activate && CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize --admin-username admin --admin-password admin --admin-email admin@admin.com] at time 12:08:22.862609
[INFO    ] Executing state cmd.run for source /home/vagrant/calamari/env/bin/activate && CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize --admin-username admin --admin-password admin --admin-email admin@admin.com
[INFO    ] Executing command 'source /home/vagrant/calamari/env/bin/activate && CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize --admin-username admin --admin-password admin --admin-email admin@admin.com' as user 'vagrant' in directory '/home/vagrant/calamari'
[ERROR   ] Command 'source /home/vagrant/calamari/env/bin/activate && CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize --admin-username admin --admin-password admin --admin-email admin@admin.com' failed with return code: 127
[ERROR   ] stderr: /bin/bash: calamari-ctl: command not found
[ERROR   ] retcode: 127
[ERROR   ] {'pid': 11099, 'retcode': 127, 'stderr': '/bin/bash: calamari-ctl: command not found', 'stdout': ''}
[INFO    ] Completed state [source /home/vagrant/calamari/env/bin/activate && CALAMARI_CONFIG=dev/calamari.conf calamari-ctl --devmode initialize --admin-username admin --admin-password admin --admin-email admin@admin.com] at time 12:08:22.892712
[DEBUG   ] LazyLoaded .returner

A full log is available here

History

#1 Updated by Dan Mick about 9 years ago

I don't immediately see the problem. I have had issues with Linux and shebang scripts, of which calamari-ctl is one....if the #! line ends up longer than 127 characters, Linux silently truncates it, which of course causes the execution to fail, and things to die. Certainly I'd look at calamari-ctl, and try running it by hand as the state was, as a first diagnosis.

#2 Updated by Abhishek Lekshmanan about 9 years ago

Dan Mick wrote:

I don't immediately see the problem. I have had issues with Linux and shebang scripts, of which calamari-ctl is one....if the #! line ends up longer than 127 characters, Linux silently truncates it, which of course causes the execution to fail, and things to die. Certainly I'd look at calamari-ctl, and try running it by hand as the state was, as a first diagnosis.

I looked at the complete logs (http://git.io/bcsF) and it seems at starting point installation of pyzmq is failing with Permission denied.. and the reason for this seems to be the permission denied for the download-cache to write to /vagrant/pip-cache. I'm not sure why though

#3 Updated by Dan Mick about 9 years ago

does it work with virtualbox? Could it be provider issues with writability of shared filesystems? I've had similar issues with one of the other vagrant providers: https://github.com/pradels/vagrant-libvirt/issues/274

#4 Updated by Abhishek Lekshmanan about 9 years ago

Dan Mick wrote:

does it work with virtualbox? Could it be provider issues with writability of shared filesystems? I've had similar issues with one of the other vagrant providers: https://github.com/pradels/vagrant-libvirt/issues/274

Could be possible.. because running the pip command without download-cache or with a different folder seems to work without error.. so looks like it might be related to the use of kvm provider after all

#5 Updated by Abhishek Lekshmanan about 9 years ago

I'll try out using virtualbox provider itself then ...

#6 Updated by Dan Mick about 9 years ago

  • Status changed from New to Need More Info

#7 Updated by Christina Meno about 9 years ago

Abhishek,

Has this issue been resolved for you? If it has I would like to close this ticket.

thank you.

#8 Updated by Christina Meno about 9 years ago

  • Status changed from Need More Info to Closed

closing this. If you have this issue again please bring it to the mailing list http://lists.ceph.com/listinfo.cgi/ceph-calamari-ceph.com

Also available in: Atom PDF