Issue Tracker: Alexandre Anriothttps://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182016-12-29T11:01:46ZIssue Tracker
Redmine Rudder - User story #9868: Node maintenance / deactivation switchhttps://issues.rudder.io/issues/9868#change-686502016-12-29T11:01:46ZAlexandre Anriot
<p>Whoops, sorry.</p>
<p>Alexis MOUSSET wrote:</p>
<blockquote>
<p>That would indeed be useful, this is a very common usecase.</p>
<p>Closing as duplicate of <a class="issue tracker-2 status-6 priority-16 priority-default closed" title="User story: Option to disable a node (Rejected)" href="https://issues.rudder.io/issues/4658">#4658</a>.</p>
</blockquote> Rudder - User story #9868 (Rejected): Node maintenance / deactivation switchhttps://issues.rudder.io/issues/98682016-12-29T10:42:02ZAlexandre Anriot
<p>Hello,</p>
<p>Sometimes, we have to switch some nodes in maintenance.</p>
<p>Could it be possible to have a such mode in the node settings, in order to suspend operations on that node?</p>
<p>It could be helpful to keep good compliance ratios and stats, by ignoring these nodes.</p>
<p>Alexandre</p> Rudder - Bug #9858: When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ...https://issues.rudder.io/issues/9858#change-686062016-12-28T08:10:43ZAlexandre Anriot
<p>Thanks for the ticket Nicolas.</p>
<p>Nicolas CHARLES wrote:</p>
<blockquote>
<p>When we upgrade rudder-agent, the file /etc/cron.d/rudder-agent-uuid is created (see <a class="external" href="http://www.rudder-project.org/redmine/issues/3930">http://www.rudder-project.org/redmine/issues/3930</a> and <a class="external" href="http://www.rudder-project.org/redmine/issues/3925">http://www.rudder-project.org/redmine/issues/3925</a> )<br />This file now calls check_rudder_agent, and it became verbose in 4.0</p>
<p>So during upgrade, we create this cron file ( <a class="external" href="https://github.com/Normation/rudder-packages/blob/master/rudder-agent/SOURCES/rudder-agent-postinst">https://github.com/Normation/rudder-packages/blob/master/rudder-agent/SOURCES/rudder-agent-postinst</a> ) without the > /dev/null, and the file is deleted afterward by techniques</p>
We should probably:
<ul>
<li>in 4.0 redirect to > /dev/null in the cron</li>
<li>remove this cron in version 4.1 (cause of the file was in 2.7.2 ...)</li>
</ul>
</blockquote> Rudder - Bug #9799 (Released): Grep error when running the agenthttps://issues.rudder.io/issues/97992016-12-12T16:05:40ZAlexandre Anriot
<p>Hello,</p>
<p>When running the agent, I get on some servers:</p>
<pre>
# /opt/rudder/bin/rudder agent check
grep: : No such file or directory
# /opt/rudder/bin/rudder agent check -i
grep: -i: No such file or directory
</pre>
<p>Here is a few more informations :</p>
<pre>
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.6 (jessie)
Release: 8.6
Codename: jessie
# dpkg -l|grep rudder-agent
ii rudder-agent 4.0.1-jessie0 amd64 Configuration management and audit tool - agent
</pre>
<p>It seems to be related to the rerouting of stderr in <em>/opt/rudder/share/lib/common.sh</em> line 2:</p>
<pre>
# Warn on potentially invalid arguments
if grep -- -- "$*" > /dev/null
</pre>
<p>Thanks.</p>
<p>Alexandre</p> Rudder - Enhancement #9752: Document stopping process before Postgres restore maintenance to avoi...https://issues.rudder.io/issues/9752#change-682492016-12-08T15:28:42ZAlexandre Anriot
<p>Several changes have been done when the platforms were setup, it's indeed probably something like this.</p>
<p>I think that Rudder is not guilty.</p>
<p>Nicolas CHARLES wrote:</p>
<blockquote>
<p>This is weird indeed<br />my guess: table was restored or copied, and constraint was dropped during restore (possibly, concurrent writing of data prevented constraint to apply)</p>
</blockquote> Rudder - Enhancement #9752: Document stopping process before Postgres restore maintenance to avoi...https://issues.rudder.io/issues/9752#change-682452016-12-08T14:48:56ZAlexandre Anriot
<p>François,</p>
<p>It's probably a local issue, as I have 23 primary keys on the database of another Rudder instance, VS 21 pkeys on this database.</p>
<p>I just added the one you mentionned, as well as <em>statusupdate_pkey</em>.</p>
<p>I guess that you can now close the ticket.</p>
<p>Thanks a lot.</p>
<p>François ARMAND wrote:</p>
<blockquote>
<p>hum. <br />I just checked, and there is something strange.</p>
<p>On a fresh installation, I have <br />[...]</p>
<p>And trying to insert the same properties fails on pkey violation constraint.</p>
<p>But on the schema definition, we do have the primary key, and we have it since the addition of the table in <a class="changeset" title="Ref #3018 : Add non compliant report logger." href="https://issues.rudder.io/projects/rudder/repository/rudder/revisions/ca2380af1529a0a717df88c6c57de54e78f31e4e">ca2380af1529a0a717df88c6c57de54e78f31e4e</a></p>
<p>So I don't get it. You can correct the problem with the following table alteration:</p>
<p>[...]</p>
<p>But I don't understand why there is no pk declaration.</p>
<p>For information, could you provide the result of the following query, to see if other pk constraint are missing:<br />[...]</p>
</blockquote> Rudder - Enhancement #9752: Document stopping process before Postgres restore maintenance to avoi...https://issues.rudder.io/issues/9752#change-676502016-12-02T10:34:47ZAlexandre Anriot
<p>I don't see any such constraint. I did this twice a few minutes ago:</p>
<pre>
rudder=# INSERT INTO rudderproperties VALUES ('reportLoggerLastId', 161072834);
INSERT 0 1
</pre>
<p>and got:</p>
<pre>
rudder=# select * from rudderproperties where name='reportLoggerLastId';
name | value
--------------------+-----------
reportLoggerLastId | 161072834
reportLoggerLastId | 161072834
reportLoggerLastId | 161072834
(3 rows)
</pre>
<p>Could it be a DB issue on our side?</p>
<p>François ARMAND wrote:</p>
<blockquote>
<p>How can it happens, the property name has an unicity constraint on it?</p>
</blockquote> Rudder - Bug #9691: Broken node.env variable in 4.0https://issues.rudder.io/issues/9691#change-675782016-11-30T12:58:00ZAlexandre Anriot
<p>Alexis,</p>
<p>Indeed, I have the same kind of output on Debian 8.</p>
<p>During the rendering, it leads to:</p>
<pre>
R: Templating error: Invalid control character at: line 2704 column 19 (char 106901)
</pre>
<p>Alexis MOUSSET wrote:</p>
<blockquote>
<p>Seen on Ubuntu 14.04 with Rudder 4.0:</p>
<p>[...]</p>
<p>instead of something like:</p>
<p>[...]</p>
</blockquote> Rudder - Enhancement #9578 (New): Ensure that python is presenthttps://issues.rudder.io/issues/95782016-10-28T13:58:25ZAlexandre Anriot
<p>Hello,</p>
<p>We just triggered an issue which happens on minimalist systems (i.e. without Python), when you try to install a package:</p>
<pre>
error: unsupported package module wrapper API version: -1
error: Some error occurred while contacting package module - promise: curl
error: Method 'package_state' failed in some repairs
</pre>
<p>In a such case, contrary to [[<a class="external" href="https://www.rudder-project.org/redmine/issues/9576">https://www.rudder-project.org/redmine/issues/9576</a>]], I guess that it's not possible to add the dependency through a promise as 'package_*' methods are broken?</p>
<p>Thanks.</p> Rudder - Enhancement #9576 (New): Ensure that the python-jinja2 library is presenthttps://issues.rudder.io/issues/95762016-10-28T12:25:29ZAlexandre Anriot
<p>Hello,</p>
<p>At the moment, the rendering of a <em>Jinja2</em> template fails on a server without <em>python-jinja2</em>.</p>
<p>Could it be possible to add the library either:</p>
<p>- In the dependencies of the <em>rudder-agent</em> package ;<br />- Through a promise, when it's needed.</p>
<p>Thanks.</p> Rudder - User story #9575 (New): Display when a technique is not used by any directivehttps://issues.rudder.io/issues/95752016-10-28T12:21:18ZAlexandre Anriot
<p>Hello,</p>
<p>As discussed with Alexis, it could be helpful to display an information / warning in the <em>Technique Editor</em> when a technique is not used by any directive.</p>
<p>Cleaning of deprecated techniques would become easier.</p>
<p>Thanks.</p> Rudder - User story #9507: Add file headers automaticallyhttps://issues.rudder.io/issues/9507#change-659362016-10-24T09:40:52ZAlexandre Anriot
<p>And may be that the content could even be included as an header or a footer.</p>
<p>Alexandre Anriot wrote:</p>
<blockquote>
<p>Hello,</p>
<p>As discussed with Jonathan, it could be useful to have an option in the techniques of the <em>Distributing files</em> category allowing to add an header automatically, such as the content of the <em>rudder_file_edit_header</em> parameter. Adding it manually in every shared files is a bit heavy and modifications take more time. :)</p>
<p>Thanks.</p>
</blockquote> Rudder - User story #9507 (New): Add file headers automaticallyhttps://issues.rudder.io/issues/95072016-10-24T09:38:21ZAlexandre Anriot
<p>Hello,</p>
<p>As discussed with Jonathan, it could be useful to have an option in the techniques of the <em>Distributing files</em> category allowing to add an header automatically, such as the content of the <em>rudder_file_edit_header</em> parameter. Adding it manually in every shared files is a bit heavy and modifications take more time. :)</p>
<p>Thanks.</p> Rudder - User story #4248: Proposal: Auto Accept listhttps://issues.rudder.io/issues/4248#change-639882016-10-13T12:33:27ZAlexandre Anriot
<p>+1</p>
<p>SaltStack supports this through <em>autosign_file</em> (regexp allowed). :)</p> Rudder - User story #9336 (New): User management technique and home directory permissionshttps://issues.rudder.io/issues/93362016-10-12T13:36:40ZAlexandre Anriot
<p>Hello,</p>
<p>When using the <em>User management</em> technique, could it be possible to specify the permissions in the <em>Home directory</em> section?</p>
<p>It could be nice to be able to create it with perms 700 for example, without having to use another technique such as <em>Set the permissions on files</em>.</p>
<p>Thanks.</p>