Hi Jhon, Updating the os-client-config has done the trick for me. Rest of the requirements are still the same and have done no updates on it.
On Fri, Aug 14, 2015 at 11:16 PM, John Griffith <[email protected] > wrote: > > > On Fri, Aug 14, 2015 at 11:41 AM, Jeremy Stanley <[email protected]> > wrote: > >> On 2015-08-14 22:55:47 +0530 (+0530), Abhishek Shrivastava wrote: >> > Found out that the os-client-config present was 1.6.2 so I >> > upgraded it to 1.6.3, is it ok ? >> >> Yes, I believe 1.6.3 is supposed to fix the error you're seeing. >> Does it? >> -- >> Jeremy Stanley >> >> _______________________________________________ >> OpenStack-Infra mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> > > FWIW, I was seeing this as well Wed night. There was an update pushed > out early Thursday morning that cleared it up on my side and I had things > working again for free. I'd be curious if you just did a fresh update on > everything if it puts you back in business. > > John > > > > _______________________________________________ > OpenStack-Infra mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > -- *Thanks & Regards,* *Abhishek* *Cloudbyte Inc. <http://www.cloudbyte.com>*
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
