Re: [OpenStack-Infra] Askbot-staging puppet venv update
Yeap, it is an open issue, because a patch is required for vamsee-solr, my pull request was accepted there, and I asked the maintainer to make a 0.0.8 release of solr module. It will solve this issue. M. On Sun, Jul 19, 2015 at 1:09 PM Jeremy Stanley wrote: > On 2015-07-19 06:58:17 + (+), Marton Kiss wrote: > [...] > > Do you think that the puppet-agent was disabled on that host due the > > smartcn failure? The last update was on July 15. I put back the agent > into > > disabled state, until we resolve this issue. > [...] > > Nope, as I explained in IRC last week, the cloudflare implementation > breaks assumptions made by our puppetry (specifically, that our > puppetmaster will be able to SSH to the server by its > fully-qualified domain name, which is now a CNAME to some Web > proxies somewhere). If there is a desire to actually use that, we > would need to deploy a new server so that the hostname can be > something other than the Web site name. > > However, when updating it manually, I do still get: > > Could not evaluate: Could not retrieve information from > environment production source(s) > > file:/tmp/solr-4.10.4/contrib/analysis-extras/lucene-libs/lucene-analyzers-smartcn-4.10.4.jar > > -- > Jeremy Stanley > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Askbot-staging puppet venv update
On 2015-07-19 06:58:17 + (+), Marton Kiss wrote: [...] > Do you think that the puppet-agent was disabled on that host due the > smartcn failure? The last update was on July 15. I put back the agent into > disabled state, until we resolve this issue. [...] Nope, as I explained in IRC last week, the cloudflare implementation breaks assumptions made by our puppetry (specifically, that our puppetmaster will be able to SSH to the server by its fully-qualified domain name, which is now a CNAME to some Web proxies somewhere). If there is a desire to actually use that, we would need to deploy a new server so that the hostname can be something other than the Web site name. However, when updating it manually, I do still get: Could not evaluate: Could not retrieve information from environment production source(s) file:/tmp/solr-4.10.4/contrib/analysis-extras/lucene-libs/lucene-analyzers-smartcn-4.10.4.jar -- Jeremy Stanley ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Askbot-staging puppet venv update
Hi Jeremy, thanks for quickly accepting the venv patch. When I wake up in the morning, I checked the ask-staging host and see no sign of the changes by the new puppet module, nor on the host and the puppet board logs. That was a bit strange, because the patch was applied several hours before. Then I invoked a 'puppet agent', and the changeset was magically applied: http://puppetboard.openstack.org/report/ask-staging.openstack.org/d0dbf46e36443acd61cf59c672b032e25b145737 Do you think that the puppet-agent was disabled on that host due the smartcn failure? The last update was on July 15. I put back the agent into disabled state, until we resolve this issue. Anyway the venv patch seems to be non disruptive, so the ask-staging.o.o is running with python virtualenv now. I need to update the op docs to reflect the changes. (the python manage.py must be invoked as /usr/askbot-env/bin/python manage.py) Brgds, Marton ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
