https://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182016-01-31T23:18:08ZIssue TrackerRudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=517472016-01-31T23:18:08ZNicolas CHARLESnicolas.charles@rudder.io
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-7 priority-lowest closed" href="/issues/7758">Bug #7758</a>: When several directives value have a CFEngine var, we get "unexpected" due to bad regex matching</i> added</li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=518332016-02-05T12:42:09ZNicolas CHARLESnicolas.charles@rudder.io
<ul></ul><p>Ok, could not reproduce :(</p> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=518342016-02-05T12:44:16ZNicolas CHARLESnicolas.charles@rudder.io
<ul></ul><p>but the expected report and the ruddersysevent table do match correctly, so there is no reason the the unknown</p> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=526712016-03-01T14:46:17ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.0.14</i> to <i>3.0.15</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=538482016-04-08T14:51:45ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.0.15</i> to <i>3.0.16</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=555642016-05-24T21:50:19ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.0.16</i> to <i>3.0.17</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=563312016-06-02T16:22:13ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.0.17</i> to <i>2.11.23</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=564672016-06-02T16:32:17ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>2.11.23</i> to <i>302</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=569572016-06-10T09:31:57ZAlexis Moussetalexis.mousset@rudder.io
<ul><li><strong>Target version</strong> changed from <i>302</i> to <i>3.1.12</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=581962016-07-29T12:27:20ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.12</i> to <i>3.1.13</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=596582016-08-27T10:06:39ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.13</i> to <i>3.1.14</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=619832016-09-28T20:50:01ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.14</i> to <i>3.1.15</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=624902016-10-03T10:13:28ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.15</i> to <i>3.1.16</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=635982016-10-11T13:11:06ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.16</i> to <i>3.1.17</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=678042016-12-05T14:20:40ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.17</i> to <i>3.1.18</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=710102017-02-17T22:20:35ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>3.1.18</i> to <i>3.1.19</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=735432017-03-21T15:52:35ZJonathan CLARKEjonathan.clarke@normation.com
<ul><li><strong>Severity</strong> set to <i>Major - prevents use of part of Rudder | no simple workaround</i></li><li><strong>User visibility</strong> set to <i>Getting started - demo | first install | level 1 Techniques</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=739442017-03-28T14:31:17ZBenoît PECCATTEbenoit.peccatte@rudder.io
<ul><li><strong>Priority</strong> set to <i>45</i></li></ul> Rudder - Bug #7855: When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpectedhttps://issues.rudder.io/issues/7855?journal_id=746092017-04-04T10:45:34ZNicolas CHARLESnicolas.charles@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>Cannot reproduce, closing</p>