Jenkins build pestered by 'no such option: --disable-pip-version-check'

Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Willem Jan Withagen]

Since somewhere last week all my Jenkins test are aborted this.
And I was under the assumption that issue would have been fixed?

--WjW

See:
https://jenkins.ceph.com/job/ceph-pull-requests/9255/console

Running virtualenv with interpreter /usr/bin/python2.7

Usage:
  pip <command> [options]

no such option: --disable-pip-version-check

Usage:
  pip <command> [options]

no such option: --disable-pip-version-check

Usage:
  pip <command> [options]

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Alfredo Deza]

On Mon, Jul 18, 2016 at 9:57 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
> Since somewhere last week all my Jenkins test are aborted this.
> And I was under the assumption that issue would have been fixed?
>
> --WjW
>
> See:
> https://jenkins.ceph.com/job/ceph-pull-requests/9255/console
>
> Running virtualenv with interpreter /usr/bin/python2.7
>
> Usage:
>   pip <command> [options]
>
> no such option: --disable-pip-version-check
>
> Usage:
>   pip <command> [options]
>
> no such option: --disable-pip-version-check
>
> Usage:
>   pip <command> [options]


That seems to be a problem in the code that creates the ceph-disk
virtual environment (python's virtualenv).

That code lives within the Ceph source tree so a fix would need to
happen there (the Jenkins job can't really fix this)

The full error (to make it easier for others to see) is:

New python executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python2.7
Also creating executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python
Installing setuptools, pip...
done.
Running virtualenv with interpreter /usr/bin/python2.7

Usage:
  pip <command> [options]

no such option: --disable-pip-version-check

Usage:
  pip <command> [options]

no such option: --disable-pip-version-check

Usage:
  pip <command> [options]

no such option: --disable-pip-version-check
make[3]: *** [src/ceph-disk/CMakeFiles/ceph-disk] Error 2
make[2]: *** [src/ceph-disk/CMakeFiles/ceph-disk.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....


> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Willem Jan Withagen]

On 18-7-2016 20:48, Alfredo Deza wrote:
> On Mon, Jul 18, 2016 at 9:57 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>> Since somewhere last week all my Jenkins test are aborted this.
>> And I was under the assumption that issue would have been fixed?
>>
>> --WjW
>>
>> See:
>> https://jenkins.ceph.com/job/ceph-pull-requests/9255/console
>>
>> Running virtualenv with interpreter /usr/bin/python2.7
>>
>> Usage:
>>   pip <command> [options]
>>
>> no such option: --disable-pip-version-check
>>
>> Usage:
>>   pip <command> [options]
>>
>> no such option: --disable-pip-version-check
>>
>> Usage:
>>   pip <command> [options]
> 
> 
> That seems to be a problem in the code that creates the ceph-disk
> virtual environment (python's virtualenv).
> 
> That code lives within the Ceph source tree so a fix would need to
> happen there (the Jenkins job can't really fix this)
> 
> The full error (to make it easier for others to see) is:
> 
> New python executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python2.7
> Also creating executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python
> Installing setuptools, pip...
> done.
> Running virtualenv with interpreter /usr/bin/python2.7
> 
> Usage:
>   pip <command> [options]
> 
> no such option: --disable-pip-version-check
> 
> Usage:
>   pip <command> [options]
> 
> no such option: --disable-pip-version-check
> 
> Usage:
>   pip <command> [options]
> 
> no such option: --disable-pip-version-check
> make[3]: *** [src/ceph-disk/CMakeFiles/ceph-disk] Error 2
> make[2]: *** [src/ceph-disk/CMakeFiles/ceph-disk.dir/all] Error 2
> make[2]: *** Waiting for unfinished jobs....

Yup,
I totally agree, but why am I (the only one) suffering from this?

Where as the code is plainly in the tree if you
   grep -R disable-pip-version-check .
at the root of the tree.
And I think more pepeles tests should suffer from this if they are
running in env's where pip does not have this option.

Even more wierd is that the VM claims to be running trusty, and I'd
expect it to run a rather recent pip after installation?

But I'm still trying get the hang of all this python trickery.

--WjW

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Daniel Gryniewicz]

On 07/18/2016 03:08 PM, Willem Jan Withagen wrote:
> On 18-7-2016 20:48, Alfredo Deza wrote:
>> On Mon, Jul 18, 2016 at 9:57 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>>> Since somewhere last week all my Jenkins test are aborted this.
>>> And I was under the assumption that issue would have been fixed?
>>>
>>> --WjW
>>>
>>> See:
>>> https://jenkins.ceph.com/job/ceph-pull-requests/9255/console
>>>
>>> Running virtualenv with interpreter /usr/bin/python2.7
>>>
>>> Usage:
>>>   pip <command> [options]
>>>
>>> no such option: --disable-pip-version-check
>>>
>>> Usage:
>>>   pip <command> [options]
>>>
>>> no such option: --disable-pip-version-check
>>>
>>> Usage:
>>>   pip <command> [options]
>>
>>
>> That seems to be a problem in the code that creates the ceph-disk
>> virtual environment (python's virtualenv).
>>
>> That code lives within the Ceph source tree so a fix would need to
>> happen there (the Jenkins job can't really fix this)
>>
>> The full error (to make it easier for others to see) is:
>>
>> New python executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python2.7
>> Also creating executable in /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python
>> Installing setuptools, pip...
>> done.
>> Running virtualenv with interpreter /usr/bin/python2.7
>>
>> Usage:
>>   pip <command> [options]
>>
>> no such option: --disable-pip-version-check
>>
>> Usage:
>>   pip <command> [options]
>>
>> no such option: --disable-pip-version-check
>>
>> Usage:
>>   pip <command> [options]
>>
>> no such option: --disable-pip-version-check
>> make[3]: *** [src/ceph-disk/CMakeFiles/ceph-disk] Error 2
>> make[2]: *** [src/ceph-disk/CMakeFiles/ceph-disk.dir/all] Error 2
>> make[2]: *** Waiting for unfinished jobs....
>
> Yup,
> I totally agree, but why am I (the only one) suffering from this?
>
> Where as the code is plainly in the tree if you
>    grep -R disable-pip-version-check .
> at the root of the tree.
> And I think more pepeles tests should suffer from this if they are
> running in env's where pip does not have this option.
>
> Even more wierd is that the VM claims to be running trusty, and I'd
> expect it to run a rather recent pip after installation?
>
> But I'm still trying get the hang of all this python trickery.
>
> --WjW
>

You have a very old version of pip.  There's a PR in the works to fix this.

Daniel

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Willem Jan Withagen]

On 19-7-2016 14:58, Daniel Gryniewicz wrote:
> On 07/18/2016 03:08 PM, Willem Jan Withagen wrote:
>> On 18-7-2016 20:48, Alfredo Deza wrote:
>>> On Mon, Jul 18, 2016 at 9:57 AM, Willem Jan Withagen
>>> <wjw@digiware.nl> wrote:
>>>> Since somewhere last week all my Jenkins test are aborted this.
>>>> And I was under the assumption that issue would have been fixed?
>>>>
>>>> --WjW
>>>>
>>>> See:
>>>> https://jenkins.ceph.com/job/ceph-pull-requests/9255/console
>>>>
>>>> Running virtualenv with interpreter /usr/bin/python2.7
>>>>
>>>> Usage:
>>>>   pip <command> [options]
>>>>
>>>> no such option: --disable-pip-version-check
>>>>
>>>> Usage:
>>>>   pip <command> [options]
>>>>
>>>> no such option: --disable-pip-version-check
>>>>
>>>> Usage:
>>>>   pip <command> [options]
>>>
>>>
>>> That seems to be a problem in the code that creates the ceph-disk
>>> virtual environment (python's virtualenv).
>>>
>>> That code lives within the Ceph source tree so a fix would need to
>>> happen there (the Jenkins job can't really fix this)
>>>
>>> The full error (to make it easier for others to see) is:
>>>
>>> New python executable in
>>> /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python2.7
>>> Also creating executable in
>>> /tmp/ceph.V2f/ceph-disk-virtualenv/bin/python
>>> Installing setuptools, pip...
>>> done.
>>> Running virtualenv with interpreter /usr/bin/python2.7
>>>
>>> Usage:
>>>   pip <command> [options]
>>>
>>> no such option: --disable-pip-version-check
>>>
>>> Usage:
>>>   pip <command> [options]
>>>
>>> no such option: --disable-pip-version-check
>>>
>>> Usage:
>>>   pip <command> [options]
>>>
>>> no such option: --disable-pip-version-check
>>> make[3]: *** [src/ceph-disk/CMakeFiles/ceph-disk] Error 2
>>> make[2]: *** [src/ceph-disk/CMakeFiles/ceph-disk.dir/all] Error 2
>>> make[2]: *** Waiting for unfinished jobs....
>>
>> Yup,
>> I totally agree, but why am I (the only one) suffering from this?
>>
>> Where as the code is plainly in the tree if you
>>    grep -R disable-pip-version-check .
>> at the root of the tree.
>> And I think more pepeles tests should suffer from this if they are
>> running in env's where pip does not have this option.
>>
>> Even more wierd is that the VM claims to be running trusty, and I'd
>> expect it to run a rather recent pip after installation?
>>
>> But I'm still trying get the hang of all this python trickery.
>>
>> --WjW
>>
> 
> You have a very old version of pip.  There's a PR in the works to fix this.

Well the problem is, that it is not me that has an old version of pip.
But this is in Jenkins and that is on the test environment where there
is fetched fresh very test-build.
I would not know how to influence this?

--WjW

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Dan Mick]

> Well the problem is, that it is not me that has an old version of pip.
> But this is in Jenkins and that is on the test environment where there
> is fetched fresh very test-build.
> I would not know how to influence this?

It looks as though one massive commit in
https://github.com/ceph/ceph/pull/10283 included a fix that should
resolve this.  Perhaps pull that into your branch?

Re: Jenkins build pestered by 'no such option: --disable-pip-version-check'

[Willem Jan Withagen]

On 20-7-2016 08:02, Dan Mick wrote:
> ....but I guess that's also broken at the moment
> 
> Sent from Nine <http://www.9folders.com/>
> ------------------------------------------------------------------------
> *From:* Dan Mick
> *Sent:* Jul 19, 2016 8:21 PM
> *To:* Willem Jan Withagen; dang@redhat.com; Alfredo Deza
> *Cc:* Ceph Development
> *Subject:* Re: Jenkins build pestered by 'no such option:
> --disable-pip-version-check'
> 
> 
>> Well the problem is, that it is not me that has an old version of pip.
>> But this is in Jenkins and that is on the test environment where there
>> is fetched fresh very test-build.
>> I would not know how to influence this?
> 
> It looks as though one massive commit in
> https://github.com/ceph/ceph/pull/10283 included a fix that should
> resolve this.  Perhaps pull that into your branch?

That would mean that my pull contains code that is already in HEAD.
I guess that would work locally, but not during Jenkins testing.
Beter I check why I did not get it with a rebase?

--WjW