[opensuse-cloud] Starting of quantum-server not possible because of wrong python-SQLAlchemy and python-quantumclient versions
pkg_resources.DistributionNotFound: sqlalchemy==0.7.9 pkg_resources.DistributionNotFound: python-quantumclient>=2.2.0,<3.0.0 python-SQLAlchemy-0.7.10-47.1 is installed on the system. Maybe a patch of the tools/pip-requires is sufficient, changing == to >=? Not sure about that. Maybe it's better to offer a separate in the correct version (0.7.9) as required by the upstream. Also python-quantumclient is only available in a wrong version. Latest version on PyPi is python-quantumclient 2.2.0. I think the version in the SPEC should be fixed. At the moment it's 2.1.2.9+git.1363006690.f96219d. But I'm not sure about the usage of the source services. I have something in mind that they will change the Version parameter in the SPEC. Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
2013/3/12 Christian Berendt
python-SQLAlchemy-0.7.10-47.1 is installed on the system. Maybe a patch of the tools/pip-requires is sufficient, changing == to >=?
Hi Christian, yes, 0.7.10 is compatible. I'm in progress of upstreaming such a change (it is actually a series of patches to all projects in order to consolidate requires). I've added the patch locally temporarily.
Also python-quantumclient is only available in a wrong version. Latest version on PyPi is python-quantumclient 2.2.0.
I've updated to the 2.2.0 version. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/12/2013 11:16 PM, Dirk Müller wrote:
yes, 0.7.10 is compatible. I'm in progress of upstreaming such a change (it is actually a series of patches to all projects in order to consolidate requires). I've added the patch locally temporarily.
What's the ID of the review request in the upstream?
Also python-quantumclient is only available in a wrong version. Latest version on PyPi is python-quantumclient 2.2.0.
I've updated to the 2.2.0 version.
Thanks. Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Le mercredi 13 mars 2013, à 10:28 +0100, Christian Berendt a écrit :
On 03/12/2013 11:16 PM, Dirk Müller wrote:
yes, 0.7.10 is compatible. I'm in progress of upstreaming such a change (it is actually a series of patches to all projects in order to consolidate requires). I've added the patch locally temporarily.
What's the ID of the review request in the upstream?
I guess looking at Dirk's requests is where this can be found :-) https://review.openstack.org/#/dashboard/6593 (just click on the name of the person when you're on review.openstack.org) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/12/2013 05:26 PM, Christian Berendt wrote:
pkg_resources.DistributionNotFound: sqlalchemy==0.7.9 pkg_resources.DistributionNotFound: python-quantumclient>=2.2.0,<3.0.0
Christian, thanks a lot for all your testing. I'm also impressed how quick these issues gets fixed by all here ;) One question: IMHO most of these issues should have been caught by our automatic tests. Are these not setup yet to catch these? Or why where they not caught? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
2013/3/13 Andreas Jaeger
One question: IMHO most of these issues should have been caught by our automatic tests. Are these not setup yet to catch these? Or why where they not caught?
Hi AJ, the answer is simple: Those kind of issues are not covered by automatic tests, unless one of the unit tests (accidentally) triggers them. We don't have any checks for rpm -V / starting / stopping services or similar. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Le jeudi 14 mars 2013, à 06:44 +0100, Dirk Müller a écrit :
2013/3/13 Andreas Jaeger
: One question: IMHO most of these issues should have been caught by our automatic tests. Are these not setup yet to catch these? Or why where they not caught?
Hi AJ,
the answer is simple: Those kind of issues are not covered by automatic tests, unless one of the unit tests (accidentally) triggers them. We don't have any checks for rpm -V / starting / stopping services or similar.
Well, we're also supposed to have a cleanvm test (https://ci.opensuse.org/view/Cloud/job/cloud-cleanvm/) which actually deploys and starts the components. It's just not running right now. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On Thursday, March 14, 2013 07:55:50 Vincent Untz wrote:
Le jeudi 14 mars 2013, à 06:44 +0100, Dirk Müller a écrit :
2013/3/13 Andreas Jaeger
: One question: IMHO most of these issues should have been caught by our automatic tests. Are these not setup yet to catch these? Or why where they not caught?
Hi AJ,
the answer is simple: Those kind of issues are not covered by automatic tests, unless one of the unit tests (accidentally) triggers them. We don't have any checks for rpm -V / starting / stopping services or similar.
Well, we're also supposed to have a cleanvm test (https://ci.opensuse.org/view/Cloud/job/cloud-cleanvm/) which actually deploys and starts the components. It's just not running right now.
Good. So, when do you expect to have it running? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/14/2013 09:04 AM, Andreas Jaeger wrote:
On Thursday, March 14, 2013 07:55:50 Vincent Untz wrote:
Le jeudi 14 mars 2013, à 06:44 +0100, Dirk Müller a écrit :
2013/3/13 Andreas Jaeger
: One question: IMHO most of these issues should have been caught by our automatic tests. Are these not setup yet to catch these? Or why where they not caught?
Hi AJ,
the answer is simple: Those kind of issues are not covered by automatic tests, unless one of the unit tests (accidentally) triggers them. We don't have any checks for rpm -V / starting / stopping services or similar.
Well, we're also supposed to have a cleanvm test (https://ci.opensuse.org/view/Cloud/job/cloud-cleanvm/) which actually deploys and starts the components. It's just not running right now.
Good.
So, when do you expect to have it running?
Depends on how much time we're allowed to spend on Jenkins ;-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/14/2013 09:08 AM, Sascha Peilicke wrote:
So, when do you expect to have it running?
Depends on how much time we're allowed to spend on Jenkins ;-)
Is someone actively restricting time on that? I would definitely push tasks like this up to the top. Automated tests are very important and overall saves the team a lot of time down the road. Cheers, James T. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
participants (6)
-
Andreas Jaeger
-
Christian Berendt
-
Dirk Müller
-
James Tan
-
Sascha Peilicke
-
Vincent Untz