Re: [openstack-dev] olso.config error on running Devstack
On Wed, Feb 5, 2014 at 3:01 PM, Doug Hellmann wrote: > > > > On Wed, Feb 5, 2014 at 1:25 PM, Ben Nemec wrote: > >> On 2014-02-05 10:58, Doug Hellmann wrote: >> >> >> >> >> On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: >> >>> On 2014-02-05 09:05, Doug Hellmann wrote: >>> >>> >>> On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: >>> On 2014-01-08 12:14, Doug Hellmann wrote: On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > On 2014-01-08 11:16, Sean Dague wrote: > >> On 01/08/2014 12:06 PM, Doug Hellmann wrote: >> >> >>> Yeah, that's what made me start thinking oslo.sphinx should be called >>> something else. >>> >>> Sean, how strongly do you feel about not installing oslo.sphinx in >>> devstack? I see your point, I'm just looking for alternatives to the >>> hassle of renaming oslo.sphinx. >> >> >> Doing the git thing is definitely not the right thing. But I guess I >> got >> lost somewhere along the way about what the actual problem is. Can >> someone write that up concisely? With all the things that have been >> tried/failed, why certain things fail, etc. > > The problem seems to be when we pip install -e oslo.config on the > system, then pip install oslo.sphinx in a venv. oslo.config is > unavailable > in the venv, apparently because the namespace package for o.s causes the > egg-link for o.c to be ignored. Pretty much every other combination I've > tried (regular pip install of both, or pip install -e of both, regardless > of where they are) works fine, but there seem to be other issues with all > of the other options we've explored so far. > > We can't remove the pip install -e of oslo.config because it has to be > used for gating, and we can't pip install -e oslo.sphinx because it's not > a > runtime dep so it doesn't belong in the gate. Changing the toplevel > package for oslo.sphinx was also mentioned, but has obvious drawbacks too. > > I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 Doug This just bit me again trying to run unit tests against a fresh Nova tree.I don't think it's just me either - Matt Riedemann said he has been disabling site-packages in tox.ini for local tox runs. We really need to do _something_ about this, even if it's just disabling site-packages by default in tox.ini for the affected projects. A different option would be nice, but based on our previous discussion I'm not sure we're going to find one. Thoughts? >>> Is the problem isolated to oslo.sphinx? That is, do we end up with any >>> configurations where we have 2 oslo libraries installed in different modes >>> (development and "regular") where one of those 2 libraries is not >>> oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename >>> that to move it out of the namespace package. >>> >>>oslo.sphinx is the only one that has triggered this for me so far. >>> I think it's less likely to happen with the others because they tend to be >>> runtime dependencies so they get installed in devstack, whereas oslo.sphinx >>> doesn't because it's a build dep (AIUI anyway). >>> >> >> That's pretty much what I expected. >> >> Can we get a volunteer to work on renaming oslo.sphinx? >> >> >> I'm winding down on the parallel testing work so I could look at this >> next. I don't know exactly what is going to be involved in the rename >> though. >> >> We also need to decide what we're going to call it. I haven't come up >> with any suggestions that I'm particularly in love with so far. :-/ >> > > Yeah, I haven't come up with anything good, either. > > oslosphinx? > > openstacksphinx? > > We will need to: > > - rename the git repository -- we have some other renames planned for this > Friday, so we could possibly take care of that one this week > - make sure the metadata file for packaging the new library is correct in > the new repo > - prepare a release under the new name so it ends up on PyPI > - update the sphinx conf.py in all consuming projects to use the new name, > and change their test-requirements.txt to refer to the new name (or finally > add a doc-requirements.txt for doc jobs) > - remove oslo.sphinx from pypi so no one uses it accidentally > > Doug > This work has started: https://review.openstack.org/#/q/I7788a9d6b5984fdfcc4678f2182104d2eb8a2be0,n,z Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Wed, Feb 5, 2014 at 1:25 PM, Ben Nemec wrote: > On 2014-02-05 10:58, Doug Hellmann wrote: > > > > > On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: > >> On 2014-02-05 09:05, Doug Hellmann wrote: >> >> >> On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: >> >>> On 2014-01-08 12:14, Doug Hellmann wrote: >>> >>> >>> >>> On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: >>> On 2014-01-08 11:16, Sean Dague wrote: > On 01/08/2014 12:06 PM, Doug Hellmann wrote: > > >> Yeah, that's what made me start thinking oslo.sphinx should be called >> something else. >> >> Sean, how strongly do you feel about not installing oslo.sphinx in >> devstack? I see your point, I'm just looking for alternatives to the >> hassle of renaming oslo.sphinx. > > > Doing the git thing is definitely not the right thing. But I guess I > got > lost somewhere along the way about what the actual problem is. Can > someone write that up concisely? With all the things that have been > tried/failed, why certain things fail, etc. The problem seems to be when we pip install -e oslo.config on the system, then pip install oslo.sphinx in a venv. oslo.config is unavailable in the venv, apparently because the namespace package for o.s causes the egg-link for o.c to be ignored. Pretty much every other combination I've tried (regular pip install of both, or pip install -e of both, regardless of where they are) works fine, but there seem to be other issues with all of the other options we've explored so far. We can't remove the pip install -e of oslo.config because it has to be used for gating, and we can't pip install -e oslo.sphinx because it's not a runtime dep so it doesn't belong in the gate. Changing the toplevel package for oslo.sphinx was also mentioned, but has obvious drawbacks too. I think that about covers what I know so far. >>> >>> Here's a link dstufft provided to the pip bug tracking this problem: >>> https://github.com/pypa/pip/issues/3 >>> Doug >>> >>> This just bit me again trying to run unit tests against a fresh Nova >>> tree.I don't think it's just me either - Matt Riedemann said he has >>> been disabling site-packages in tox.ini for local tox runs. We really need >>> to do _something_ about this, even if it's just disabling site-packages by >>> default in tox.ini for the affected projects. A different option would be >>> nice, but based on our previous discussion I'm not sure we're going to find >>> one. >>> Thoughts? >>> >> Is the problem isolated to oslo.sphinx? That is, do we end up with any >> configurations where we have 2 oslo libraries installed in different modes >> (development and "regular") where one of those 2 libraries is not >> oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename >> that to move it out of the namespace package. >> >>oslo.sphinx is the only one that has triggered this for me so far. I >> think it's less likely to happen with the others because they tend to be >> runtime dependencies so they get installed in devstack, whereas oslo.sphinx >> doesn't because it's a build dep (AIUI anyway). >> > > That's pretty much what I expected. > > Can we get a volunteer to work on renaming oslo.sphinx? > > > I'm winding down on the parallel testing work so I could look at this > next. I don't know exactly what is going to be involved in the rename > though. > > We also need to decide what we're going to call it. I haven't come up > with any suggestions that I'm particularly in love with so far. :-/ > Yeah, I haven't come up with anything good, either. oslosphinx? openstacksphinx? We will need to: - rename the git repository -- we have some other renames planned for this Friday, so we could possibly take care of that one this week - make sure the metadata file for packaging the new library is correct in the new repo - prepare a release under the new name so it ends up on PyPI - update the sphinx conf.py in all consuming projects to use the new name, and change their test-requirements.txt to refer to the new name (or finally add a doc-requirements.txt for doc jobs) - remove oslo.sphinx from pypi so no one uses it accidentally Doug > > -Ben > > > Doug > >> >> >> Doug >> >>> -Ben >>> >> > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-02-05 10:58, Doug Hellmann wrote: > On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: > > On 2014-02-05 09:05, Doug Hellmann wrote: > > On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > > On 2014-01-08 12:14, Doug Hellmann wrote: > > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > > On 2014-01-08 11:16, Sean Dague wrote: > On 01/08/2014 12:06 PM, Doug Hellmann wrote: > > Yeah, that's what made me start thinking oslo.sphinx should be called > something else. > > Sean, how strongly do you feel about not installing oslo.sphinx in > devstack? I see your point, I'm just looking for alternatives to the > hassle of renaming oslo.sphinx. > Doing the git thing is definitely not the right thing. But I guess I got > lost somewhere along the way about what the actual problem is. Can > someone write that up concisely? With all the things that have been > tried/failed, why certain things fail, etc. The problem seems to be when we pip install -e oslo.config on the system, then pip install oslo.sphinx in a venv. oslo.config is unavailable in the venv, apparently because the namespace package for o.s causes the egg-link for o.c to be ignored. Pretty much every other combination I've tried (regular pip install of both, or pip install -e of both, regardless of where they are) works fine, but there seem to be other issues with all of the other options we've explored so far. We can't remove the pip install -e of oslo.config because it has to be used for gating, and we can't pip install -e oslo.sphinx because it's not a runtime dep so it doesn't belong in the gate. Changing the toplevel package for oslo.sphinx was also mentioned, but has obvious drawbacks too. I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 [1] Doug This just bit me again trying to run unit tests against a fresh Nova tree. I don't think it's just me either - Matt Riedemann said he has been disabling site-packages in tox.ini for local tox runs. We really need to do _something_ about this, even if it's just disabling site-packages by default in tox.ini for the affected projects. A different option would be nice, but based on our previous discussion I'm not sure we're going to find one. Thoughts? Is the problem isolated to oslo.sphinx? That is, do we end up with any configurations where we have 2 oslo libraries installed in different modes (development and "regular") where one of those 2 libraries is not oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename that to move it out of the namespace package. oslo.sphinx is the only one that has triggered this for me so far. I think it's less likely to happen with the others because they tend to be runtime dependencies so they get installed in devstack, whereas oslo.sphinx doesn't because it's a build dep (AIUI anyway). That's pretty much what I expected. Can we get a volunteer to work on renaming oslo.sphinx? I'm winding down on the parallel testing work so I could look at this next. I don't know exactly what is going to be involved in the rename though. We also need to decide what we're going to call it. I haven't come up with any suggestions that I'm particularly in love with so far. :-/ -Ben > Doug > > Doug > > -Ben Links: -- [1] https://github.com/pypa/pip/issues/3 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
Avoiding namespace packages is a good idea in general. At least until Python 3.whatever is baseline. > On Feb 5, 2014, at 10:58 AM, Doug Hellmann > wrote: > > > > >> On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: >>> On 2014-02-05 09:05, Doug Hellmann wrote: >>> >>> On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: On 2014-01-08 12:14, Doug Hellmann wrote: > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: >> On 2014-01-08 11:16, Sean Dague wrote: >> On 01/08/2014 12:06 PM, Doug Hellmann wrote: >> >>> Yeah, that's what made me start thinking oslo.sphinx should be called >>> something else. >>> >>> Sean, how strongly do you feel about not installing oslo.sphinx in >>> devstack? I see your point, I'm just looking for alternatives to the >>> hassle of renaming oslo.sphinx. >> >> Doing the git thing is definitely not the right thing. But I guess I got >> lost somewhere along the way about what the actual problem is. Can >> someone write that up concisely? With all the things that have been >> tried/failed, why certain things fail, etc. > The problem seems to be when we pip install -e oslo.config on the system, > then pip install oslo.sphinx in a venv. oslo.config is unavailable in > the venv, apparently because the namespace package for o.s causes the > egg-link for o.c to be ignored. Pretty much every other combination I've > tried (regular pip install of both, or pip install -e of both, regardless > of where they are) works fine, but there seem to be other issues with all > of the other options we've explored so far. > > We can't remove the pip install -e of oslo.config because it has to be > used for gating, and we can't pip install -e oslo.sphinx because it's not > a runtime dep so it doesn't belong in the gate. Changing the toplevel > package for oslo.sphinx was also mentioned, but has obvious drawbacks too. > > I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 Doug This just bit me again trying to run unit tests against a fresh Nova tree. I don't think it's just me either - Matt Riedemann said he has been disabling site-packages in tox.ini for local tox runs. We really need to do _something_ about this, even if it's just disabling site-packages by default in tox.ini for the affected projects. A different option would be nice, but based on our previous discussion I'm not sure we're going to find one. Thoughts? >>> >>> Is the problem isolated to oslo.sphinx? That is, do we end up with any >>> configurations where we have 2 oslo libraries installed in different modes >>> (development and "regular") where one of those 2 libraries is not >>> oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename >>> that to move it out of the namespace package. >> >> oslo.sphinx is the only one that has triggered this for me so far. I think >> it's less likely to happen with the others because they tend to be runtime >> dependencies so they get installed in devstack, whereas oslo.sphinx doesn't >> because it's a build dep (AIUI anyway). > > That's pretty much what I expected. > > Can we get a volunteer to work on renaming oslo.sphinx? > > Doug > >>> >>> Doug -Ben > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Wed, Feb 5, 2014 at 11:44 AM, Ben Nemec wrote: > On 2014-02-05 09:05, Doug Hellmann wrote: > > > On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > >> On 2014-01-08 12:14, Doug Hellmann wrote: >> >> >> >> On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: >> >>> On 2014-01-08 11:16, Sean Dague wrote: >>> On 01/08/2014 12:06 PM, Doug Hellmann wrote: > Yeah, that's what made me start thinking oslo.sphinx should be called > something else. > > Sean, how strongly do you feel about not installing oslo.sphinx in > devstack? I see your point, I'm just looking for alternatives to the > hassle of renaming oslo.sphinx. Doing the git thing is definitely not the right thing. But I guess I got lost somewhere along the way about what the actual problem is. Can someone write that up concisely? With all the things that have been tried/failed, why certain things fail, etc. >>> >>> The problem seems to be when we pip install -e oslo.config on the >>> system, then pip install oslo.sphinx in a venv. oslo.config is unavailable >>> in the venv, apparently because the namespace package for o.s causes the >>> egg-link for o.c to be ignored. Pretty much every other combination I've >>> tried (regular pip install of both, or pip install -e of both, regardless >>> of where they are) works fine, but there seem to be other issues with all >>> of the other options we've explored so far. >>> >>> We can't remove the pip install -e of oslo.config because it has to be >>> used for gating, and we can't pip install -e oslo.sphinx because it's not a >>> runtime dep so it doesn't belong in the gate. Changing the toplevel >>> package for oslo.sphinx was also mentioned, but has obvious drawbacks too. >>> >>> I think that about covers what I know so far. >> >> Here's a link dstufft provided to the pip bug tracking this problem: >> https://github.com/pypa/pip/issues/3 >> Doug >> >> This just bit me again trying to run unit tests against a fresh Nova >> tree.I don't think it's just me either - Matt Riedemann said he has >> been disabling site-packages in tox.ini for local tox runs. We really need >> to do _something_ about this, even if it's just disabling site-packages by >> default in tox.ini for the affected projects. A different option would be >> nice, but based on our previous discussion I'm not sure we're going to find >> one. >> Thoughts? >> > > Is the problem isolated to oslo.sphinx? That is, do we end up with any > configurations where we have 2 oslo libraries installed in different modes > (development and "regular") where one of those 2 libraries is not > oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename > that to move it out of the namespace package. > > > oslo.sphinx is the only one that has triggered this for me so far. I > think it's less likely to happen with the others because they tend to be > runtime dependencies so they get installed in devstack, whereas oslo.sphinx > doesn't because it's a build dep (AIUI anyway). > That's pretty much what I expected. Can we get a volunteer to work on renaming oslo.sphinx? Doug > > Doug > >> -Ben >> > > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-02-05 09:05, Doug Hellmann wrote: > On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > > On 2014-01-08 12:14, Doug Hellmann wrote: > > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > > On 2014-01-08 11:16, Sean Dague wrote: > On 01/08/2014 12:06 PM, Doug Hellmann wrote: > > Yeah, that's what made me start thinking oslo.sphinx should be called > something else. > > Sean, how strongly do you feel about not installing oslo.sphinx in > devstack? I see your point, I'm just looking for alternatives to the > hassle of renaming oslo.sphinx. > Doing the git thing is definitely not the right thing. But I guess I got > lost somewhere along the way about what the actual problem is. Can > someone write that up concisely? With all the things that have been > tried/failed, why certain things fail, etc. The problem seems to be when we pip install -e oslo.config on the system, then pip install oslo.sphinx in a venv. oslo.config is unavailable in the venv, apparently because the namespace package for o.s causes the egg-link for o.c to be ignored. Pretty much every other combination I've tried (regular pip install of both, or pip install -e of both, regardless of where they are) works fine, but there seem to be other issues with all of the other options we've explored so far. We can't remove the pip install -e of oslo.config because it has to be used for gating, and we can't pip install -e oslo.sphinx because it's not a runtime dep so it doesn't belong in the gate. Changing the toplevel package for oslo.sphinx was also mentioned, but has obvious drawbacks too. I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 [1] Doug This just bit me again trying to run unit tests against a fresh Nova tree. I don't think it's just me either - Matt Riedemann said he has been disabling site-packages in tox.ini for local tox runs. We really need to do _something_ about this, even if it's just disabling site-packages by default in tox.ini for the affected projects. A different option would be nice, but based on our previous discussion I'm not sure we're going to find one. Thoughts? Is the problem isolated to oslo.sphinx? That is, do we end up with any configurations where we have 2 oslo libraries installed in different modes (development and "regular") where one of those 2 libraries is not oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename that to move it out of the namespace package. oslo.sphinx is the only one that has triggered this for me so far. I think it's less likely to happen with the others because they tend to be runtime dependencies so they get installed in devstack, whereas oslo.sphinx doesn't because it's a build dep (AIUI anyway). > Doug > >> -Ben Links: -- [1] https://github.com/pypa/pip/issues/3 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Tue, Feb 4, 2014 at 5:14 PM, Ben Nemec wrote: > On 2014-01-08 12:14, Doug Hellmann wrote: > > > > > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > >> On 2014-01-08 11:16, Sean Dague wrote: >> >>> On 01/08/2014 12:06 PM, Doug Hellmann wrote: >>> >>> Yeah, that's what made me start thinking oslo.sphinx should be called something else. Sean, how strongly do you feel about not installing oslo.sphinx in devstack? I see your point, I'm just looking for alternatives to the hassle of renaming oslo.sphinx. >>> >>> >>> Doing the git thing is definitely not the right thing. But I guess I got >>> lost somewhere along the way about what the actual problem is. Can >>> someone write that up concisely? With all the things that have been >>> tried/failed, why certain things fail, etc. >> >> The problem seems to be when we pip install -e oslo.config on the >> system, then pip install oslo.sphinx in a venv. oslo.config is unavailable >> in the venv, apparently because the namespace package for o.s causes the >> egg-link for o.c to be ignored. Pretty much every other combination I've >> tried (regular pip install of both, or pip install -e of both, regardless >> of where they are) works fine, but there seem to be other issues with all >> of the other options we've explored so far. >> >> We can't remove the pip install -e of oslo.config because it has to be >> used for gating, and we can't pip install -e oslo.sphinx because it's not a >> runtime dep so it doesn't belong in the gate. Changing the toplevel >> package for oslo.sphinx was also mentioned, but has obvious drawbacks too. >> >> I think that about covers what I know so far. > > > Here's a link dstufft provided to the pip bug tracking this problem: > https://github.com/pypa/pip/issues/3 > > Doug > > This just bit me again trying to run unit tests against a fresh Nova > tree.I don't think it's just me either - Matt Riedemann said he has > been disabling site-packages in tox.ini for local tox runs. We really need > to do _something_ about this, even if it's just disabling site-packages by > default in tox.ini for the affected projects. A different option would be > nice, but based on our previous discussion I'm not sure we're going to find > one. > > Thoughts? > Is the problem isolated to oslo.sphinx? That is, do we end up with any configurations where we have 2 oslo libraries installed in different modes (development and "regular") where one of those 2 libraries is not oslo.sphinx? Because if the issue is really just oslo.sphinx, we can rename that to move it out of the namespace package. Doug > > -Ben > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-08 12:14, Doug Hellmann wrote: > On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > > On 2014-01-08 11:16, Sean Dague wrote: > On 01/08/2014 12:06 PM, Doug Hellmann wrote: > > Yeah, that's what made me start thinking oslo.sphinx should be called > something else. > > Sean, how strongly do you feel about not installing oslo.sphinx in > devstack? I see your point, I'm just looking for alternatives to the > hassle of renaming oslo.sphinx. > Doing the git thing is definitely not the right thing. But I guess I got > lost somewhere along the way about what the actual problem is. Can > someone write that up concisely? With all the things that have been > tried/failed, why certain things fail, etc. The problem seems to be when we pip install -e oslo.config on the system, then pip install oslo.sphinx in a venv. oslo.config is unavailable in the venv, apparently because the namespace package for o.s causes the egg-link for o.c to be ignored. Pretty much every other combination I've tried (regular pip install of both, or pip install -e of both, regardless of where they are) works fine, but there seem to be other issues with all of the other options we've explored so far. We can't remove the pip install -e of oslo.config because it has to be used for gating, and we can't pip install -e oslo.sphinx because it's not a runtime dep so it doesn't belong in the gate. Changing the toplevel package for oslo.sphinx was also mentioned, but has obvious drawbacks too. I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 [1] Doug This just bit me again trying to run unit tests against a fresh Nova tree. I don't think it's just me either - Matt Riedemann said he has been disabling site-packages in tox.ini for local tox runs. We really need to do _something_ about this, even if it's just disabling site-packages by default in tox.ini for the affected projects. A different option would be nice, but based on our previous discussion I'm not sure we're going to find one. Thoughts? -Ben Links: -- [1] https://github.com/pypa/pip/issues/3 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Wed, Jan 8, 2014 at 12:37 PM, Ben Nemec wrote: > On 2014-01-08 11:16, Sean Dague wrote: > >> On 01/08/2014 12:06 PM, Doug Hellmann wrote: >> >> >>> Yeah, that's what made me start thinking oslo.sphinx should be called >>> something else. >>> >>> Sean, how strongly do you feel about not installing oslo.sphinx in >>> devstack? I see your point, I'm just looking for alternatives to the >>> hassle of renaming oslo.sphinx. >>> >> >> Doing the git thing is definitely not the right thing. But I guess I got >> lost somewhere along the way about what the actual problem is. Can >> someone write that up concisely? With all the things that have been >> tried/failed, why certain things fail, etc. >> > > The problem seems to be when we pip install -e oslo.config on the system, > then pip install oslo.sphinx in a venv. oslo.config is unavailable in the > venv, apparently because the namespace package for o.s causes the egg-link > for o.c to be ignored. Pretty much every other combination I've tried > (regular pip install of both, or pip install -e of both, regardless of > where they are) works fine, but there seem to be other issues with all of > the other options we've explored so far. > > We can't remove the pip install -e of oslo.config because it has to be > used for gating, and we can't pip install -e oslo.sphinx because it's not a > runtime dep so it doesn't belong in the gate. Changing the toplevel > package for oslo.sphinx was also mentioned, but has obvious drawbacks too. > > I think that about covers what I know so far. Here's a link dstufft provided to the pip bug tracking this problem: https://github.com/pypa/pip/issues/3 Doug > > > -Ben > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-08 11:16, Sean Dague wrote: On 01/08/2014 12:06 PM, Doug Hellmann wrote: Yeah, that's what made me start thinking oslo.sphinx should be called something else. Sean, how strongly do you feel about not installing oslo.sphinx in devstack? I see your point, I'm just looking for alternatives to the hassle of renaming oslo.sphinx. Doing the git thing is definitely not the right thing. But I guess I got lost somewhere along the way about what the actual problem is. Can someone write that up concisely? With all the things that have been tried/failed, why certain things fail, etc. The problem seems to be when we pip install -e oslo.config on the system, then pip install oslo.sphinx in a venv. oslo.config is unavailable in the venv, apparently because the namespace package for o.s causes the egg-link for o.c to be ignored. Pretty much every other combination I've tried (regular pip install of both, or pip install -e of both, regardless of where they are) works fine, but there seem to be other issues with all of the other options we've explored so far. We can't remove the pip install -e of oslo.config because it has to be used for gating, and we can't pip install -e oslo.sphinx because it's not a runtime dep so it doesn't belong in the gate. Changing the toplevel package for oslo.sphinx was also mentioned, but has obvious drawbacks too. I think that about covers what I know so far. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 01/08/2014 12:06 PM, Doug Hellmann wrote: > Yeah, that's what made me start thinking oslo.sphinx should be called > something else. > > Sean, how strongly do you feel about not installing oslo.sphinx in > devstack? I see your point, I'm just looking for alternatives to the > hassle of renaming oslo.sphinx. Doing the git thing is definitely not the right thing. But I guess I got lost somewhere along the way about what the actual problem is. Can someone write that up concisely? With all the things that have been tried/failed, why certain things fail, etc. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Wed, Jan 8, 2014 at 11:53 AM, Ben Nemec wrote: > On 2014-01-08 10:50, Doug Hellmann wrote: > > > > > On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote: > >> On 2014-01-08 08:24, Doug Hellmann wrote: >> >> >> >> >> On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote: >> >>> On 2014-01-07 07:16, Doug Hellmann wrote: >>> >>> >>> >>> >>> On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: >>> I have been seeing this problem also. My problem is actually with oslo.sphinx. I ran sudo pip install -r test-requirements.txt in cinder so that I could run the tests there, which installed oslo.sphinx. Strange thing is that the oslo.sphinx installed a directory called oslo in /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this package installed like so I get the same error you get with oslo.config. >>> >>> The oslo libraries use python namespace packages, which manifest >>> themselves as a directory in site-packages (or dist-packages) with >>> sub-packages but no __init__.py(c). That way oslo.sphinx and oslo.config >>> can be packaged separately, but still installed under the "oslo" directory >>> and imported as oslo.sphinx and oslo.config. >>> >>> My guess is that installing oslo.sphinx globally (with sudo), set up 2 >>> copies of the namespace package (one in the global dist-packages and >>> presumably one in the virtualenv being used for the tests). >>> >>>Actually I think it may be the opposite problem, at least where I'm >>> currently running into this. oslo.sphinx is only installed in the venv and >>> it creates a namespace package there. Then if you try to load oslo.config >>> in the venv it looks in the namespace package, doesn't find it, and bails >>> with a missing module error. >>> >>> I'm personally running into this in tempest - I can't even run pep8 out >>> of the box because the sample config check fails due to missing >>> oslo.config. Here's what I'm seeing: >>> >>> In the tox venv: >>> (pep8)[fedora@devstack site-packages]$ ls oslo* >>> oslo.sphinx-1.1-py2.7-nspkg.pth >>> >>> oslo: >>> sphinx >>> >>> oslo.sphinx-1.1-py2.7.egg-info: >>> dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt >>> installed-files.txt not-zip-safeSOURCES.txt >>> >>> >>> And in the system site-packages: >>> [fedora@devstack site-packages]$ ls oslo* >>> oslo.config.egg-link oslo.messaging.egg-link >>> >>> >>> Since I don't actually care about oslo.sphinx in this case, I also found >>> that deleting it from the venv fixes the problem, but obviously that's just >>> a hacky workaround. My initial thought is to install oslo.sphinx in >>> devstack the same way as oslo.config and oslo.messaging, but I assume >>> there's a reason we didn't do it that way in the first place so I'm not >>> sure if that will work. >>> >>> So I don't know what the proper fix is, but I thought I'd share what >>> I've found so far. Also, I'm not sure if this even relates to the >>> ceilometer issue since I wouldn't expect that to be running in a venv, but >>> it may have a similar issue. >>> >> >> I wonder if the issue is actually that we're using "pip install -e" for >> oslo.config and oslo.messaging (as evidenced by the .egg-link files). Do >> things work properly if those packages are installed to the global >> site-packages from PyPI instead? We don't want to change the way devstack >> installs them, but it would give us another data point. >> >> Another solution is to have a list of dependencies needed for building >> documentation, separate from the tests, since oslo.sphinx isn't needed for >> the tests. >> >> >> >> It does work if I remove the pip install -e version of oslo.config and >> reinstall from the pypi package, so this appears to be an issue with the >> egg-links. >> > > You had already tested installing oslo.sphinx with pip install -e, > right? That's probably the least-wrong answer. Either that or move > oslo.sphinx to a different top level package to avoid conflicting with > runtime code. > > > Right. This https://review.openstack.org/#/c/65336/ also fixed the > problem for me, but according to Sean that's not something we should be > doing in devstack either. > Yeah, that's what made me start thinking oslo.sphinx should be called something else. Sean, how strongly do you feel about not installing oslo.sphinx in devstack? I see your point, I'm just looking for alternatives to the hassle of renaming oslo.sphinx. Doug > -Ben > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-08 10:50, Doug Hellmann wrote: > On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote: > > On 2014-01-08 08:24, Doug Hellmann wrote: > > On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote: > > On 2014-01-07 07:16, Doug Hellmann wrote: > > On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: > > I have been seeing this problem also. > > My problem is actually with oslo.sphinx. I ran sudo pip install -r > test-requirements.txt in cinder so that I could run the tests there, which > installed oslo.sphinx. > > Strange thing is that the oslo.sphinx installed a directory called oslo in > /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this > package installed like so I get the same error you get with oslo.config. > > The oslo libraries use python namespace packages, which manifest themselves > as a directory in site-packages (or dist-packages) with sub-packages but no > __init__.py(c). That way oslo.sphinx and oslo.config can be packaged > separately, but still installed under the "oslo" directory and imported as > oslo.sphinx and oslo.config. > > My guess is that installing oslo.sphinx globally (with sudo), set up 2 copies > of the namespace package (one in the global dist-packages and presumably one > in the virtualenv being used for the tests). Actually I think it may be the opposite problem, at least where I'm currently running into this. oslo.sphinx is only installed in the venv and it creates a namespace package there. Then if you try to load oslo.config in the venv it looks in the namespace package, doesn't find it, and bails with a missing module error. I'm personally running into this in tempest - I can't even run pep8 out of the box because the sample config check fails due to missing oslo.config. Here's what I'm seeing: In the tox venv: (pep8)[fedora@devstack site-packages]$ ls oslo* oslo.sphinx-1.1-py2.7-nspkg.pth oslo: sphinx oslo.sphinx-1.1-py2.7.egg-info: dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt installed-files.txt not-zip-safe SOURCES.txt And in the system site-packages: [fedora@devstack site-packages]$ ls oslo* oslo.config.egg-link oslo.messaging.egg-link Since I don't actually care about oslo.sphinx in this case, I also found that deleting it from the venv fixes the problem, but obviously that's just a hacky workaround. My initial thought is to install oslo.sphinx in devstack the same way as oslo.config and oslo.messaging, but I assume there's a reason we didn't do it that way in the first place so I'm not sure if that will work. So I don't know what the proper fix is, but I thought I'd share what I've found so far. Also, I'm not sure if this even relates to the ceilometer issue since I wouldn't expect that to be running in a venv, but it may have a similar issue. I wonder if the issue is actually that we're using "pip install -e" for oslo.config and oslo.messaging (as evidenced by the .egg-link files). Do things work properly if those packages are installed to the global site-packages from PyPI instead? We don't want to change the way devstack installs them, but it would give us another data point. Another solution is to have a list of dependencies needed for building documentation, separate from the tests, since oslo.sphinx isn't needed for the tests. It does work if I remove the pip install -e version of oslo.config and reinstall from the pypi package, so this appears to be an issue with the egg-links. You had already tested installing oslo.sphinx with pip install -e, right? That's probably the least-wrong answer. Either that or move oslo.sphinx to a different top level package to avoid conflicting with runtime code. Right. This https://review.openstack.org/#/c/65336/ also fixed the problem for me, but according to Sean that's not something we should be doing in devstack either. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Wed, Jan 8, 2014 at 11:31 AM, Ben Nemec wrote: > On 2014-01-08 08:24, Doug Hellmann wrote: > > > > > On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote: > >> On 2014-01-07 07:16, Doug Hellmann wrote: >> >> >> >> >> On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: >> >>> I have been seeing this problem also. >>> >>> My problem is actually with oslo.sphinx. I ran sudo pip install -r >>> test-requirements.txt in cinder so that I could run the tests there, which >>> installed oslo.sphinx. >>> >>> Strange thing is that the oslo.sphinx installed a directory called oslo >>> in /usr/local/lib/python2.7/dist-packages with no __init__.py file. With >>> this package installed like so I get the same error you get with >>> oslo.config. >>> >> >> The oslo libraries use python namespace packages, which manifest >> themselves as a directory in site-packages (or dist-packages) with >> sub-packages but no __init__.py(c). That way oslo.sphinx and oslo.config >> can be packaged separately, but still installed under the "oslo" directory >> and imported as oslo.sphinx and oslo.config. >> >> My guess is that installing oslo.sphinx globally (with sudo), set up 2 >> copies of the namespace package (one in the global dist-packages and >> presumably one in the virtualenv being used for the tests). >> >>Actually I think it may be the opposite problem, at least where I'm >> currently running into this. oslo.sphinx is only installed in the venv and >> it creates a namespace package there. Then if you try to load oslo.config >> in the venv it looks in the namespace package, doesn't find it, and bails >> with a missing module error. >> >> I'm personally running into this in tempest - I can't even run pep8 out >> of the box because the sample config check fails due to missing >> oslo.config. Here's what I'm seeing: >> >> In the tox venv: >> (pep8)[fedora@devstack site-packages]$ ls oslo* >> oslo.sphinx-1.1-py2.7-nspkg.pth >> >> oslo: >> sphinx >> >> oslo.sphinx-1.1-py2.7.egg-info: >> dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt >> installed-files.txt not-zip-safeSOURCES.txt >> >> >> And in the system site-packages: >> [fedora@devstack site-packages]$ ls oslo* >> oslo.config.egg-link oslo.messaging.egg-link >> >> >> Since I don't actually care about oslo.sphinx in this case, I also found >> that deleting it from the venv fixes the problem, but obviously that's just >> a hacky workaround. My initial thought is to install oslo.sphinx in >> devstack the same way as oslo.config and oslo.messaging, but I assume >> there's a reason we didn't do it that way in the first place so I'm not >> sure if that will work. >> >> So I don't know what the proper fix is, but I thought I'd share what I've >> found so far. Also, I'm not sure if this even relates to the ceilometer >> issue since I wouldn't expect that to be running in a venv, but it may have >> a similar issue. >> > > I wonder if the issue is actually that we're using "pip install -e" for > oslo.config and oslo.messaging (as evidenced by the .egg-link files). Do > things work properly if those packages are installed to the global > site-packages from PyPI instead? We don't want to change the way devstack > installs them, but it would give us another data point. > > Another solution is to have a list of dependencies needed for building > documentation, separate from the tests, since oslo.sphinx isn't needed for > the tests. > > > > It does work if I remove the pip install -e version of oslo.config and > reinstall from the pypi package, so this appears to be an issue with the > egg-links. > You had already tested installing oslo.sphinx with pip install -e, right? That's probably the least-wrong answer. Either that or move oslo.sphinx to a different top level package to avoid conflicting with runtime code. Doug > -Ben > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-08 08:24, Doug Hellmann wrote: > On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote: > > On 2014-01-07 07:16, Doug Hellmann wrote: > > On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: > > I have been seeing this problem also. > > My problem is actually with oslo.sphinx. I ran sudo pip install -r > test-requirements.txt in cinder so that I could run the tests there, which > installed oslo.sphinx. > > Strange thing is that the oslo.sphinx installed a directory called oslo in > /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this > package installed like so I get the same error you get with oslo.config. > > The oslo libraries use python namespace packages, which manifest themselves > as a directory in site-packages (or dist-packages) with sub-packages but no > __init__.py(c). That way oslo.sphinx and oslo.config can be packaged > separately, but still installed under the "oslo" directory and imported as > oslo.sphinx and oslo.config. > > My guess is that installing oslo.sphinx globally (with sudo), set up 2 copies > of the namespace package (one in the global dist-packages and presumably one > in the virtualenv being used for the tests). Actually I think it may be the opposite problem, at least where I'm currently running into this. oslo.sphinx is only installed in the venv and it creates a namespace package there. Then if you try to load oslo.config in the venv it looks in the namespace package, doesn't find it, and bails with a missing module error. I'm personally running into this in tempest - I can't even run pep8 out of the box because the sample config check fails due to missing oslo.config. Here's what I'm seeing: In the tox venv: (pep8)[fedora@devstack site-packages]$ ls oslo* oslo.sphinx-1.1-py2.7-nspkg.pth oslo: sphinx oslo.sphinx-1.1-py2.7.egg-info: dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt installed-files.txt not-zip-safe SOURCES.txt And in the system site-packages: [fedora@devstack site-packages]$ ls oslo* oslo.config.egg-link oslo.messaging.egg-link Since I don't actually care about oslo.sphinx in this case, I also found that deleting it from the venv fixes the problem, but obviously that's just a hacky workaround. My initial thought is to install oslo.sphinx in devstack the same way as oslo.config and oslo.messaging, but I assume there's a reason we didn't do it that way in the first place so I'm not sure if that will work. So I don't know what the proper fix is, but I thought I'd share what I've found so far. Also, I'm not sure if this even relates to the ceilometer issue since I wouldn't expect that to be running in a venv, but it may have a similar issue. I wonder if the issue is actually that we're using "pip install -e" for oslo.config and oslo.messaging (as evidenced by the .egg-link files). Do things work properly if those packages are installed to the global site-packages from PyPI instead? We don't want to change the way devstack installs them, but it would give us another data point. Another solution is to have a list of dependencies needed for building documentation, separate from the tests, since oslo.sphinx isn't needed for the tests. It does work if I remove the pip install -e version of oslo.config and reinstall from the pypi package, so this appears to be an issue with the egg-links. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Tue, Jan 7, 2014 at 12:32 PM, Ben Nemec wrote: > On 2014-01-07 07:16, Doug Hellmann wrote: > > > > > On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: > >> I have been seeing this problem also. >> >> My problem is actually with oslo.sphinx. I ran sudo pip install -r >> test-requirements.txt in cinder so that I could run the tests there, which >> installed oslo.sphinx. >> >> Strange thing is that the oslo.sphinx installed a directory called oslo >> in /usr/local/lib/python2.7/dist-packages with no __init__.py file. With >> this package installed like so I get the same error you get with >> oslo.config. >> > > The oslo libraries use python namespace packages, which manifest > themselves as a directory in site-packages (or dist-packages) with > sub-packages but no __init__.py(c). That way oslo.sphinx and oslo.config > can be packaged separately, but still installed under the "oslo" directory > and imported as oslo.sphinx and oslo.config. > > My guess is that installing oslo.sphinx globally (with sudo), set up 2 > copies of the namespace package (one in the global dist-packages and > presumably one in the virtualenv being used for the tests). > > Actually I think it may be the opposite problem, at least where I'm > currently running into this. oslo.sphinx is only installed in the venv and > it creates a namespace package there. Then if you try to load oslo.config > in the venv it looks in the namespace package, doesn't find it, and bails > with a missing module error. > > I'm personally running into this in tempest - I can't even run pep8 out of > the box because the sample config check fails due to missing oslo.config. > Here's what I'm seeing: > > In the tox venv: > (pep8)[fedora@devstack site-packages]$ ls oslo* > oslo.sphinx-1.1-py2.7-nspkg.pth > > oslo: > sphinx > > oslo.sphinx-1.1-py2.7.egg-info: > dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt > installed-files.txt not-zip-safeSOURCES.txt > > > And in the system site-packages: > [fedora@devstack site-packages]$ ls oslo* > oslo.config.egg-link oslo.messaging.egg-link > > > Since I don't actually care about oslo.sphinx in this case, I also found > that deleting it from the venv fixes the problem, but obviously that's just > a hacky workaround. My initial thought is to install oslo.sphinx in > devstack the same way as oslo.config and oslo.messaging, but I assume > there's a reason we didn't do it that way in the first place so I'm not > sure if that will work. > > So I don't know what the proper fix is, but I thought I'd share what I've > found so far. Also, I'm not sure if this even relates to the ceilometer > issue since I wouldn't expect that to be running in a venv, but it may have > a similar issue. > I wonder if the issue is actually that we're using "pip install -e" for oslo.config and oslo.messaging (as evidenced by the .egg-link files). Do things work properly if those packages are installed to the global site-packages from PyPI instead? We don't want to change the way devstack installs them, but it would give us another data point. Another solution is to have a list of dependencies needed for building documentation, separate from the tests, since oslo.sphinx isn't needed for the tests. Doug > > -Ben > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 01/07/2014 01:44 PM, Ben Nemec wrote: > On 2014-01-07 12:11, Noorul Islam Kamal Malmiyoda wrote: >> On Tue, Jan 7, 2014 at 4:54 PM, Michael Kerrin >> wrote: >>> I have been seeing this problem also. >>> >>> >>> >>> My problem is actually with oslo.sphinx. I ran sudo pip install -r >>> test-requirements.txt in cinder so that I could run the tests there, >>> which >>> installed oslo.sphinx. >>> >>> >>> >>> Strange thing is that the oslo.sphinx installed a directory called >>> oslo in >>> /usr/local/lib/python2.7/dist-packages with no __init__.py file. With >>> this >>> package installed like so I get the same error you get with oslo.config. >>> >>> >>> >>> I don't need oslo.sphinx so I just went and manually deleted the oslo >>> directory and the oslo.sphinx* files in >>> /usr/local/lib/python2.7/dist-packages. Everything worked fine after >>> that. >>> >>> >>> >>> Not sure what to do about this, but that is my story >>> >>> >>> >> >> In solum, we are trying to use devstack job for functional testing. We >> are installing test packages [1] from test-requirements.txt, hence we >> are also facing similar issue. See [2] and [3] >> >> Regards, >> Noorul >> >> [1] >> http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_20_26_838 >> >> [2] >> http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_11_500 >> >> [3] >> http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_15_996 >> > > I went ahead and proposed a change to install oslo.sphinx from git in > devstack: https://review.openstack.org/#/c/65336 That fixes my problems > in tempest anyway. > > If anyone knows of a reason we shouldn't do that, speak now or forever > hold your peace. :-) Yes, we shouldn't do that. That's there for installing things that need to be self gating with the rest of openstack. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-07 12:11, Noorul Islam Kamal Malmiyoda wrote: On Tue, Jan 7, 2014 at 4:54 PM, Michael Kerrin wrote: I have been seeing this problem also. My problem is actually with oslo.sphinx. I ran sudo pip install -r test-requirements.txt in cinder so that I could run the tests there, which installed oslo.sphinx. Strange thing is that the oslo.sphinx installed a directory called oslo in /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this package installed like so I get the same error you get with oslo.config. I don't need oslo.sphinx so I just went and manually deleted the oslo directory and the oslo.sphinx* files in /usr/local/lib/python2.7/dist-packages. Everything worked fine after that. Not sure what to do about this, but that is my story In solum, we are trying to use devstack job for functional testing. We are installing test packages [1] from test-requirements.txt, hence we are also facing similar issue. See [2] and [3] Regards, Noorul [1] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_20_26_838 [2] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_11_500 [3] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_15_996 I went ahead and proposed a change to install oslo.sphinx from git in devstack: https://review.openstack.org/#/c/65336 That fixes my problems in tempest anyway. If anyone knows of a reason we shouldn't do that, speak now or forever hold your peace. :-) -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Tue, Jan 7, 2014 at 4:54 PM, Michael Kerrin wrote: > I have been seeing this problem also. > > > > My problem is actually with oslo.sphinx. I ran sudo pip install -r > test-requirements.txt in cinder so that I could run the tests there, which > installed oslo.sphinx. > > > > Strange thing is that the oslo.sphinx installed a directory called oslo in > /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this > package installed like so I get the same error you get with oslo.config. > > > > I don't need oslo.sphinx so I just went and manually deleted the oslo > directory and the oslo.sphinx* files in > /usr/local/lib/python2.7/dist-packages. Everything worked fine after that. > > > > Not sure what to do about this, but that is my story > > > In solum, we are trying to use devstack job for functional testing. We are installing test packages [1] from test-requirements.txt, hence we are also facing similar issue. See [2] and [3] Regards, Noorul [1] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_20_26_838 [2] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_11_500 [3] http://logs.openstack.org/59/64059/8/check/gate-solum-devstack-dsvm/a7522b8/console.html#_2014-01-07_05_26_15_996 > Michael > > > > > > > > On Mon 23 Dec 2013 14:18:11 Sean Dague wrote: > >> On 12/23/2013 11:52 AM, Ben Nemec wrote: > >> > On 2013-12-18 09:26, Sayali Lunkad wrote: > >> >> Hello, > >> >> > >> >> I get the following error when I run stack.sh on Devstack > >> >> > >> >> Traceback (most recent call last): > >> >> File "/usr/local/bin/ceilometer-dbsync", line 6, in > >> >> > >> >> from ceilometer.storage import dbsync > >> >> > >> >> File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line > >> >> > >> >> 23, in > >> >> > >> >> from oslo.config import cfg > >> >> > >> >> ImportError: No module named config > >> >> ++ failed > >> >> ++ local r=1 > >> >> +++ jobs -p > >> >> ++ kill > >> >> ++ set +o xtrace > >> >> > >> >> Search gives me olso.config is installed. Please let me know of any > >> >> solution. > >> > > >> > Devstack pulls oslo.config from git, so if you have it installed on the > >> > system through pip or something it could cause problems. If you can > >> > verify that it's only in /opt/stack/oslo.config, you might try deleting > >> > that directory and rerunning devstack to pull down a fresh copy. I > >> > don't know for sure what the problem is, but those are a couple of > >> > things to try. > >> > >> We actually try to resolve that here: > >> > >> https://github.com/openstack-dev/devstack/blob/master/lib/oslo#L43 > >> > >> However, have I said how terrible python packaging is recently? > >> Basically you can very easily get yourself in a situation where *just > >> enough* of the distro package is left behind that pip thinks its there, > >> so won't install it, but the python loader doesn't, so won't work. > >> > >> Then much sadness. > >> > >> If anyone has a more fool proof way to fix this, suggestions appreciated. > >> > >> -Sean > > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2014-01-07 07:16, Doug Hellmann wrote: > On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: > >> I have been seeing this problem also. >> >> My problem is actually with oslo.sphinx. I ran sudo pip install -r >> test-requirements.txt in cinder so that I could run the tests there, which >> installed oslo.sphinx. >> >> Strange thing is that the oslo.sphinx installed a directory called oslo in >> /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this >> package installed like so I get the same error you get with oslo.config. > > The oslo libraries use python namespace packages, which manifest themselves > as a directory in site-packages (or dist-packages) with sub-packages but no > __init__.py(c). That way oslo.sphinx and oslo.config can be packaged > separately, but still installed under the "oslo" directory and imported as > oslo.sphinx and oslo.config. > > My guess is that installing oslo.sphinx globally (with sudo), set up 2 copies > of the namespace package (one in the global dist-packages and presumably one > in the virtualenv being used for the tests). Actually I think it may be the opposite problem, at least where I'm currently running into this. oslo.sphinx is only installed in the venv and it creates a namespace package there. Then if you try to load oslo.config in the venv it looks in the namespace package, doesn't find it, and bails with a missing module error. I'm personally running into this in tempest - I can't even run pep8 out of the box because the sample config check fails due to missing oslo.config. Here's what I'm seeing: In the tox venv: (pep8)[fedora@devstack site-packages]$ ls oslo* oslo.sphinx-1.1-py2.7-nspkg.pth oslo: sphinx oslo.sphinx-1.1-py2.7.egg-info: dependency_links.txt namespace_packages.txt PKG-INFO top_level.txt installed-files.txt not-zip-safe SOURCES.txt And in the system site-packages: [fedora@devstack site-packages]$ ls oslo* oslo.config.egg-link oslo.messaging.egg-link Since I don't actually care about oslo.sphinx in this case, I also found that deleting it from the venv fixes the problem, but obviously that's just a hacky workaround. My initial thought is to install oslo.sphinx in devstack the same way as oslo.config and oslo.messaging, but I assume there's a reason we didn't do it that way in the first place so I'm not sure if that will work. So I don't know what the proper fix is, but I thought I'd share what I've found so far. Also, I'm not sure if this even relates to the ceilometer issue since I wouldn't expect that to be running in a venv, but it may have a similar issue. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On Tue, Jan 7, 2014 at 6:24 AM, Michael Kerrin wrote: > I have been seeing this problem also. > > > > My problem is actually with oslo.sphinx. I ran sudo pip install -r > test-requirements.txt in cinder so that I could run the tests there, which > installed oslo.sphinx. > > > > Strange thing is that the oslo.sphinx installed a directory called oslo in > /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this > package installed like so I get the same error you get with oslo.config. > The oslo libraries use python namespace packages, which manifest themselves as a directory in site-packages (or dist-packages) with sub-packages but no __init__.py(c). That way oslo.sphinx and oslo.config can be packaged separately, but still installed under the "oslo" directory and imported as oslo.sphinx and oslo.config. My guess is that installing oslo.sphinx globally (with sudo), set up 2 copies of the namespace package (one in the global dist-packages and presumably one in the virtualenv being used for the tests). Doug > > > I don't need oslo.sphinx so I just went and manually deleted the oslo > directory and the oslo.sphinx* files in > /usr/local/lib/python2.7/dist-packages. Everything worked fine after that. > > > > Not sure what to do about this, but that is my story > > > > Michael > > > > > > > > On Mon 23 Dec 2013 14:18:11 Sean Dague wrote: > > > On 12/23/2013 11:52 AM, Ben Nemec wrote: > > > > On 2013-12-18 09:26, Sayali Lunkad wrote: > > > >> Hello, > > > >> > > > >> I get the following error when I run stack.sh on Devstack > > > >> > > > >> Traceback (most recent call last): > > > >> File "/usr/local/bin/ceilometer-dbsync", line 6, in > > > >> > > > >> from ceilometer.storage import dbsync > > > >> > > > >> File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line > > > >> > > > >> 23, in > > > >> > > > >> from oslo.config import cfg > > > >> > > > >> ImportError: No module named config > > > >> ++ failed > > > >> ++ local r=1 > > > >> +++ jobs -p > > > >> ++ kill > > > >> ++ set +o xtrace > > > >> > > > >> Search gives me olso.config is installed. Please let me know of any > > > >> solution. > > > > > > > > Devstack pulls oslo.config from git, so if you have it installed on the > > > > system through pip or something it could cause problems. If you can > > > > verify that it's only in /opt/stack/oslo.config, you might try deleting > > > > that directory and rerunning devstack to pull down a fresh copy. I > > > > don't know for sure what the problem is, but those are a couple of > > > > things to try. > > > > > > We actually try to resolve that here: > > > > > > https://github.com/openstack-dev/devstack/blob/master/lib/oslo#L43 > > > > > > However, have I said how terrible python packaging is recently? > > > Basically you can very easily get yourself in a situation where *just > > > enough* of the distro package is left behind that pip thinks its there, > > > so won't install it, but the python loader doesn't, so won't work. > > > > > > Then much sadness. > > > > > > If anyone has a more fool proof way to fix this, suggestions appreciated. > > > > > > -Sean > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
I have been seeing this problem also. My problem is actually with oslo.sphinx. I ran sudo pip install -r test-requirements.txt in cinder so that I could run the tests there, which installed oslo.sphinx. Strange thing is that the oslo.sphinx installed a directory called oslo in /usr/local/lib/python2.7/dist-packages with no __init__.py file. With this package installed like so I get the same error you get with oslo.config. I don't need oslo.sphinx so I just went and manually deleted the oslo directory and the oslo.sphinx* files in /usr/local/lib/python2.7/dist-packages. Everything worked fine after that. Not sure what to do about this, but that is my story Michael On Mon 23 Dec 2013 14:18:11 Sean Dague wrote: > On 12/23/2013 11:52 AM, Ben Nemec wrote: > > On 2013-12-18 09:26, Sayali Lunkad wrote: > >> Hello, > >> > >> I get the following error when I run stack.sh on Devstack > >> > >> Traceback (most recent call last): > >> File "/usr/local/bin/ceilometer-dbsync", line 6, in > >> > >> from ceilometer.storage import dbsync > >> > >> File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line > >> > >> 23, in > >> > >> from oslo.config import cfg > >> > >> ImportError: No module named config > >> ++ failed > >> ++ local r=1 > >> +++ jobs -p > >> ++ kill > >> ++ set +o xtrace > >> > >> Search gives me olso.config is installed. Please let me know of any > >> solution. > > > > Devstack pulls oslo.config from git, so if you have it installed on the > > system through pip or something it could cause problems. If you can > > verify that it's only in /opt/stack/oslo.config, you might try deleting > > that directory and rerunning devstack to pull down a fresh copy. I > > don't know for sure what the problem is, but those are a couple of > > things to try. > > We actually try to resolve that here: > > https://github.com/openstack-dev/devstack/blob/master/lib/oslo#L43 > > However, have I said how terrible python packaging is recently? > Basically you can very easily get yourself in a situation where *just > enough* of the distro package is left behind that pip thinks its there, > so won't install it, but the python loader doesn't, so won't work. > > Then much sadness. > > If anyone has a more fool proof way to fix this, suggestions appreciated. > > -Sean ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2013-12-23 13:18, Sean Dague wrote: On 12/23/2013 11:52 AM, Ben Nemec wrote: On 2013-12-18 09:26, Sayali Lunkad wrote: Hello, I get the following error when I run stack.sh on Devstack Traceback (most recent call last): File "/usr/local/bin/ceilometer-dbsync", line 6, in from ceilometer.storage import dbsync File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in from oslo.config import cfg ImportError: No module named config ++ failed ++ local r=1 +++ jobs -p ++ kill ++ set +o xtrace Search gives me olso.config is installed. Please let me know of any solution. Devstack pulls oslo.config from git, so if you have it installed on the system through pip or something it could cause problems. If you can verify that it's only in /opt/stack/oslo.config, you might try deleting that directory and rerunning devstack to pull down a fresh copy. I don't know for sure what the problem is, but those are a couple of things to try. We actually try to resolve that here: https://github.com/openstack-dev/devstack/blob/master/lib/oslo#L43 However, have I said how terrible python packaging is recently? Basically you can very easily get yourself in a situation where *just enough* of the distro package is left behind that pip thinks its there, so won't install it, but the python loader doesn't, so won't work. Then much sadness. If anyone has a more fool proof way to fix this, suggestions appreciated. -Sean Ah, good to know. I haven't actually run into this problem recently, so this was kind of a shot in the dark. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 12/23/2013 11:52 AM, Ben Nemec wrote: > On 2013-12-18 09:26, Sayali Lunkad wrote: > >> Hello, >> >> I get the following error when I run stack.sh on Devstack >> >> Traceback (most recent call last): >> File "/usr/local/bin/ceilometer-dbsync", line 6, in >> from ceilometer.storage import dbsync >> File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line >> 23, in >> from oslo.config import cfg >> ImportError: No module named config >> ++ failed >> ++ local r=1 >> +++ jobs -p >> ++ kill >> ++ set +o xtrace >> >> Search gives me olso.config is installed. Please let me know of any >> solution. > > > Devstack pulls oslo.config from git, so if you have it installed on the > system through pip or something it could cause problems. If you can > verify that it's only in /opt/stack/oslo.config, you might try deleting > that directory and rerunning devstack to pull down a fresh copy. I > don't know for sure what the problem is, but those are a couple of > things to try. We actually try to resolve that here: https://github.com/openstack-dev/devstack/blob/master/lib/oslo#L43 However, have I said how terrible python packaging is recently? Basically you can very easily get yourself in a situation where *just enough* of the distro package is left behind that pip thinks its there, so won't install it, but the python loader doesn't, so won't work. Then much sadness. If anyone has a more fool proof way to fix this, suggestions appreciated. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
On 2013-12-18 09:26, Sayali Lunkad wrote: > Hello, > > I get the following error when I run stack.sh on Devstack > > Traceback (most recent call last): > File "/usr/local/bin/ceilometer-dbsync", line 6, in > from ceilometer.storage import dbsync > File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in > > from oslo.config import cfg > ImportError: No module named config > ++ failed > ++ local r=1 > +++ jobs -p > ++ kill > ++ set +o xtrace > > Search gives me olso.config is installed. Please let me know of any solution. Devstack pulls oslo.config from git, so if you have it installed on the system through pip or something it could cause problems. If you can verify that it's only in /opt/stack/oslo.config, you might try deleting that directory and rerunning devstack to pull down a fresh copy. I don't know for sure what the problem is, but those are a couple of things to try. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
Also forgot to mention I can access the dashboard but I am unable to retrieve any information about the volumes. On Dec 18, 2013 8:56 PM, "Sayali Lunkad" wrote: > Hello, > > I get the following error when I run stack.sh on Devstack > > Traceback (most recent call last): > File "/usr/local/bin/ceilometer-dbsync", line 6, in > from ceilometer.storage import dbsync > File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in > > from oslo.config import cfg > ImportError: No module named config > ++ failed > ++ local r=1 > +++ jobs -p > ++ kill > ++ set +o xtrace > > Search gives me olso.config is installed. Please let me know of any > solution. > > Thanks, > Sayali. > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
Hey, I do need ceilometer so making changes to localrc won't help me here. And no corporate proxy! What could possibly be the issue because my Devstack had been working fine till now. Thanks, Sayali On Dec 18, 2013 9:14 PM, "iKhan" wrote: > If you are behind corporate proxy, make sure the proxy is set. > > > On Wed, Dec 18, 2013 at 8:56 PM, Sayali Lunkad wrote: > >> Hello, >> >> I get the following error when I run stack.sh on Devstack >> >> Traceback (most recent call last): >> File "/usr/local/bin/ceilometer-dbsync", line 6, in >> from ceilometer.storage import dbsync >> File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, >> in >> from oslo.config import cfg >> ImportError: No module named config >> ++ failed >> ++ local r=1 >> +++ jobs -p >> ++ kill >> ++ set +o xtrace >> >> Search gives me olso.config is installed. Please let me know of any >> solution. >> >> Thanks, >> Sayali. >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Thanks, > Ibad Khan > 9686594607 > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
Unless you need ceilometer, you can try in your localrc of eliminating ceilometer from the ENABLED_SERVICES. I know thats not the ulimate fix, but it will get you up and running with devstack. On Wed, Dec 18, 2013 at 8:26 AM, Sayali Lunkad wrote: > Hello, > > I get the following error when I run stack.sh on Devstack > > Traceback (most recent call last): > File "/usr/local/bin/ceilometer-dbsync", line 6, in > from ceilometer.storage import dbsync > File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in > > from oslo.config import cfg > ImportError: No module named config > ++ failed > ++ local r=1 > +++ jobs -p > ++ kill > ++ set +o xtrace > > Search gives me olso.config is installed. Please let me know of any > solution. > > Thanks, > Sayali. > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] olso.config error on running Devstack
If you are behind corporate proxy, make sure the proxy is set. On Wed, Dec 18, 2013 at 8:56 PM, Sayali Lunkad wrote: > Hello, > > I get the following error when I run stack.sh on Devstack > > Traceback (most recent call last): > File "/usr/local/bin/ceilometer-dbsync", line 6, in > from ceilometer.storage import dbsync > File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in > > from oslo.config import cfg > ImportError: No module named config > ++ failed > ++ local r=1 > +++ jobs -p > ++ kill > ++ set +o xtrace > > Search gives me olso.config is installed. Please let me know of any > solution. > > Thanks, > Sayali. > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Thanks, Ibad Khan 9686594607 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] olso.config error on running Devstack
Hello, I get the following error when I run stack.sh on Devstack Traceback (most recent call last): File "/usr/local/bin/ceilometer-dbsync", line 6, in from ceilometer.storage import dbsync File "/opt/stack/ceilometer/ceilometer/storage/__init__.py", line 23, in from oslo.config import cfg ImportError: No module named config ++ failed ++ local r=1 +++ jobs -p ++ kill ++ set +o xtrace Search gives me olso.config is installed. Please let me know of any solution. Thanks, Sayali. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
