----- Original Message ----- > From: "Daryl Walleck" <daryl.walleck at RACKSPACE.COM> > To: openstack-qa at lists.openstack.org > Sent: Wednesday, November 28, 2012 8:48:27 PM > Subject: [openstack-qa] Tempest broken post EC2 merge > > It could be that I'm missing something, but I no longer can run any > Tempest test without an immediate failure for different boto > modules. Am I the only one having this issue, or is there something > new I'm missing here? For a quick fix I'd like to suggest we do something like this and disable exception logging when the EC2/S3 clients fail to be configured correctly. https://review.openstack.org/#/c/17202/ This gets rid of the stack traces that I think most people might complain about. Dan > > Daryl > > _______________________________________________ > openstack-qa mailing list > openstack-qa at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa >