Issue #2342
closed
Vagrant setup does not allow to checkout the code in anywhere except $HOME/devel
Status:
CLOSED - CURRENTRELEASE
I think this is by design. You really should use ~/devel.
semyers wrote:
I think this is by design. You really should use ~/devel.
I misinterpreted this as referring to ~/devel in the vagrant guest machine, but in talking about it the code needed to be in ~/devel on the host. That is not okay.
- Triaged changed from No to Yes
I haven't been able to reproduce this, but it might be fixed for 3.0. I definitely had this in mind when converting all the 3.0 vagrant stuff to ansible, and tested installing from code in locations other than ~/devel on both the host and the vagrant box while developing the playbook.
Here is some more info on what we observed. When bizhang and I experienced the issue I believe the checkouts were located on the host system at ~/pulp/ or ~/devel/pulp/pulp/ (one extra 'pulp' dir). This was with a Pulp 2.y setup. IIRC, the Vagrant completed and Pulp was installed, but most of the pulp bits that you expected to be from your checkouts actually came from rpms. This led to a strange "my changes are not taking effect" problem.
The description claims that permission errors are the problem, but I've observed the issue without permission errors occurring. This is from memory but roughly:
1. Check out platform to ~/notdevel/pulp/
and pulp_rpm to ~/notdevel/pulp_rpm/
2. vagrant up
3. SSH to the vagrant env and cd /tmp
4. Create a python shell and run:
>>> from pulp import server
>>>
>>> server
<module 'pulp.server' from '/home/vagrant/devel/pulp/server/pulp/server/__init__.pyc'>
The above is a healthy environment. A broken environment would show pulp.server being provided from /usr/lib/python2.7/site-packages/pulp/
- Status changed from NEW to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF