Project

General

Profile

Actions

Bug #16820

closed

Technical logs display error when almost identical reports are reported

Added by Félix DALLIDET over 4 years ago. Updated 12 months ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

With a broken agent I had some almost identical reports. They only differ from their message part and were displayed as "ERROR|ERROR" in the UI.

This double report could happen in some cases and should not be displayed this way on the interface.

Here are the responsible reports:

6 14:05:09+01:00##e637370d-a9be-42ac-9fef-cd42e66d7110@#Checking dsc resource User with parameters: {  $name = 'bobouioui' $secpasswd = ConvertTo-SecureString 'PlainTextPassword' -AsPlainText -Force $mycreds = New-Object System.Management.Automation.PSCredential ($Name, $secpasswd) $Ensure = 'Present' $UserName = $name $Password = $mycreds $table = @{} $table.Add("Ensure", $Ensure) $table.Add("UserName", $UserName) $table.Add("Password", $Password) $table  }
Feb 26 14:05:26 WIN-6REVNN94M8O Rudder[0]: @@DSC@@result_error@@afdc2b5a-0780-45da-a5ab-eb36d5e2a5b8@@7a363ed3-1418-4b17-873f-b9a26b0bc94c@@0@@DSC resource@@Creating user bobouioui@@2020-02-26 14:05:09+01:00##e637370d-a9be-42ac-9fef-cd42e66d7110@#Checking dsc resource User with parameters: {  $name = 'bobouioui' $secpasswd = ConvertTo-SecureString 'PlainTextPassword' -AsPlainText -Force $mycreds = New-Object System.Management.Automation.PSCredential ($Name, $secpasswd) $Ensure = 'Present' $UserName = $name $Password = $mycreds $table = @{} $table.Add("Ensure", $Ensure) $table.Add("UserName", $UserName) $table.Add("Password", $Password) $table  }         Log level informations:\nThere could be a possible multiple matches exception while trying to use the System.DirectoryServices API's.Exception calling "Save" with "0" argument(s): "The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.  " 

See the screenshot attached for the UX part.


Files

dsc_error.png (19.2 KB) dsc_error.png Félix DALLIDET, 2020-02-26 14:13
Actions #1

Updated by Félix DALLIDET over 4 years ago

repost of the reports:

Feb 26 14:05:26 WIN-6REVNN94M8O Rudder[0]: @@DSC@@result_error@@afdc2b5a-0780-45da-a5ab-eb36d5e2a5b8@@7a363ed3-1418-4b17-873f-b9a26b0bc94c@@0@@DSC resource@@Creating user bobouioui@@2020-02-26 14:05:09+01:00##e637370d-a9be-42ac-9fef-cd42e66d7110@#Checking dsc resource User with parameters: {  $name = 'bobouioui' $secpasswd = ConvertTo-SecureString 'PlainTextPassword' -AsPlainText -Force $mycreds = New-Object System.Management.Automation.PSCredential ($Name, $secpasswd) $Ensure = 'Present' $UserName = $name $Password = $mycreds $table = @{} $table.Add("Ensure", $Ensure) $table.Add("UserName", $UserName) $table.Add("Password", $Password) $table  }
Feb 26 14:05:26 WIN-6REVNN94M8O Rudder[0]: @@DSC@@result_error@@afdc2b5a-0780-45da-a5ab-eb36d5e2a5b8@@7a363ed3-1418-4b17-873f-b9a26b0bc94c@@0@@DSC resource@@Creating user bobouioui@@2020-02-26 14:05:09+01:00##e637370d-a9be-42ac-9fef-cd42e66d7110@#Checking dsc resource User with parameters: {  $name = 'bobouioui' $secpasswd = ConvertTo-SecureString 'PlainTextPassword' -AsPlainText -Force $mycreds = New-Object System.Management.Automation.PSCredential ($Name, $secpasswd) $Ensure = 'Present' $UserName = $name $Password = $mycreds $table = @{} $table.Add("Ensure", $Ensure) $table.Add("UserName", $UserName) $table.Add("Password", $Password) $table  }         Log level informations:\nThere could be a possible multiple matches exception while trying to use the System.DirectoryServices API's.Exception calling "Save" with "0" argument(s): "The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.  " 

Actions #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.4 to 6.0.5
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.5 to 6.0.6
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #6

Updated by François ARMAND over 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority changed from 0 to 20
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
Actions #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.9 to 6.0.10
Actions #9

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 20 to 19
Actions #10

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 798 to 6.1.14
  • Priority changed from 19 to 18
Actions #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #12

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #13

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #15

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #18

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #19

Updated by François ARMAND 12 months ago

  • Status changed from New to Resolved
  • Priority changed from 18 to 0
  • Regression set to No

We now compare based on component id, it should happen anymore.

Actions

Also available in: Atom PDF