Issue Tracker: Issueshttps://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182022-11-23T10:15:42ZIssue Tracker
Redmine Rudder - Enhancement #22124 (Pending release): Log all API errorshttps://issues.rudder.io/issues/221242022-11-23T10:15:42ZVincent MEMBRÉvme@rudder.io
<p>When an API call is made, and it makes an error, there is no error log message, so we have no way to know what happens if the response is ignored and we don't have any history so we will never know what happened. We need to log an error message so that we can understand what is going wrong and debug api errors afterwards</p> Rudder - Bug #21869 (Pending release): Update scala-lib version due to CVE2022-36944https://issues.rudder.io/issues/218692022-09-27T13:41:54ZFrançois ARMANDfrancois.armand@rudder.io
<p>There is a CVE that does not look exploitable in our case but we prefer to avoid it nonetheless.</p> Rudder - User story #21778 (Pending release): add an option to select where to log in sysloghttps://issues.rudder.io/issues/217782022-09-16T13:30:33ZNicolas CHARLESnicolas.charles@rudder.io
<p>By default, all logs from agent and cf-serverd go to LOG_LOCAL3<br />We need to be able to change facility, or move it to NONE (no syslog)</p>
<p>We will do that with a rudder/syslog_facility node property, used when feature syslog_disableable is defined</p> Rudder - Bug #21736 (Pending release): Broken report parsing when the key value contains line breakshttps://issues.rudder.io/issues/217362022-09-08T10:46:38ZNicolas CHARLESnicolas.charles@rudder.io
<p>If i want to use multi line key, the reporting breaks because agent adds text in the output</p>
<p>with command_execution, if i run the following command, i get<br /><pre>
cd /var/rudder/tmp/assets/
tar -xzvf /var/rudder/tmp/assets/fs-linux-agent-3.4.0.tar.gz
</pre></p>
<p>the reporting is<br /><pre>
cd /var/rudder/tmp/assets/
2022-09-08T10:44:12+00:00 tar -xzvf /var/rudder/tmp/assets/fs-linux-agent-3.4.0.tar.gz
</pre></p>
<p>so the webapp can't match it<br />happens in 7.1, most likely in older versions</p> Rudder - Bug #21707 (Pending release): Archive import does regenerate policieshttps://issues.rudder.io/issues/217072022-09-05T14:57:51ZFrançois ARMANDfrancois.armand@rudder.io
<p>When an archive is imported, we need to regenerate policies since rules/directives/etc have likely change.</p>
<p>The case for technique is a bit more complicated. We should reload technique library, but not sure about regeneration (see <a class="issue tracker-1 status-16 priority-16 priority-default closed child" title="Bug: Archive import does not regenerate techniques (Resolved)" href="https://issues.rudder.io/issues/21709">#21709</a> for that)</p> Rudder - Bug #21686 (Pending release): generated policies are invalid when using a generic method...https://issues.rudder.io/issues/216862022-08-31T13:44:33ZNicolas CHARLESnicolas.charles@rudder.io
<p>error was already present at that time</p> Rudder - Architecture #21539 (Pending release): Make campaign test workhttps://issues.rudder.io/issues/215392022-08-03T19:50:25ZFrançois ARMANDfrancois.armand@rudder.io
<p>Try to simplify a bit encoding of JSON too, currently it's very hard to test.</p> Rudder - Bug #21534 (Pending release): Some tests not run because of bad class namehttps://issues.rudder.io/issues/215342022-08-03T16:09:27ZFrançois ARMANDfrancois.armand@rudder.io
<p>Happens for SystemApiTests => SystemApiTest</p> Rudder - Architecture #21510 (Pending release): Don't overwrite config-repos from rudder-core in ...https://issues.rudder.io/issues/215102022-08-01T14:16:47ZFrançois ARMANDfrancois.armand@rudder.io
<p>Else, depending on the class loading order, we get either what we want, or pain and despair.</p> Rudder - Bug #21499 (Pending release): Several ps1.st technique files (fileTemplate, copyFileFrom...https://issues.rudder.io/issues/214992022-07-28T09:11:48ZFrançois ARMANDfrancois.armand@rudder.io
<p>The full list:</p>
<p>./applications/snmp/1.0/snmp.ps1.st: ASCII text<br />./fileDistribution/fileTemplate/1.0/fileTemplate.ps1.st: ASCII text, with very long lines (348)<br />./fileDistribution/copyGitFile/2.3/copyFileFromSharedFolder.ps1.st: ASCII text, with very long lines (341)<br />./systemSettings/systemManagement/motdConfiguration/3.3/motd.ps1.st: ASCII text<br />./systemSettings/userManagement/userManagement/9.0/userManagement.ps1.st: ASCII text</p> Rudder - Bug #21498 (Pending release): Correct BOM file in ps1.st used in testhttps://issues.rudder.io/issues/214982022-07-28T08:55:38ZFrançois ARMANDfrancois.armand@rudder.io
<p>Some ps1 template used for policy generation tests are not correct regarding the BOM, which leads to error in DSC agent tests</p> Rudder - Architecture #21478 (Pending release): Clean up test configuration repository to use it ...https://issues.rudder.io/issues/214782022-07-26T12:29:54ZFrançois ARMANDfrancois.armand@rudder.io
<p>We need to clean up the way we access test configuration repository from NodeConfigData so that it can be accessed also when it's in a test jar from a plugin for example.</p> Rudder - Architecture #21477 (Pending release): Port policy writting test to rudder 7.1https://issues.rudder.io/issues/214772022-07-25T23:00:51ZFrançois ARMANDfrancois.armand@rudder.io
<p>We didn't do it when we changed system technique in 7.0. It needs to be done to check for non-regression in ncf-agent rewriting.</p> Rudder - Bug #20758 (Pending release): Improve group node computationhttps://issues.rudder.io/issues/207582022-02-13T21:01:03ZNicolas CHARLESnicolas.charles@rudder.io
As a follow up of <a class="issue tracker-1 status-5 priority-16 priority-default closed" title="Bug: Improve dynamic group computation speed and fix inverted searched (Released)" href="https://issues.rudder.io/issues/20716">#20716</a>, we could improve the code lisibility by:
<ul>
<li>not having the `internalQueryProcessor` return a NodeInfo, but only NodeId. The overall cost of managing NodeInfo is tremendous in creating Sets</li>
<li>so rather than having a `nodeInfoFiltered`, we could have `nodeIdFiltered`
<ul>
<li>This is only possible in 7.0 and + because in branch 6.2 it still need the ServerRole postfilter</li>
</ul>
</li>
<li>in PostFilterNodeFromInfoService we can have a faster "toSet" for the OR composition by mapping to nodeId only</li>
<li>and `foundNodeInfos` could be a Seq rather than a Set (an make the toSet on the foundNodeInfos.map(_.nodeId) )</li>
<li>and so the results in internalQueryProcessor can also be a Seq</li>
</ul>
<p>The drawback is only for the SearchNodeComponent: it will have to explore back the cache with the list of nodeId to get the result</p>
<p>The overall cost a doing a toSet on collection of NodeInfo is very expensive</p> Rudder - Bug #18078 (New): SELinux error for relayd search access on krb5 on centos 8https://issues.rudder.io/issues/180782020-07-31T06:28:09ZFrançois ARMANDfrancois.armand@rudder.io
<pre>
Jul 31 06:05:44 server setroubleshoot[12830]: SELinux is preventing /opt/rudder/bin/rudder-relayd from search access on the directory krb5. For complete SELinux messages run: sealert -l 07e5b566-8a9d-4635-965f-22c336cc3c99
Jul 31 06:05:44 server platform-python[12830]: SELinux is preventing /opt/rudder/bin/rudder-relayd from search access on the directory krb5.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that rudder-relayd should be allowed search access on the krb5 directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'r2d2-worker-1' --raw | audit2allow -M my-r2d2worker1
# semodule -X 300 -i my-r2d2worker1.pp
</pre>