Uploaded image for project: 'Puppet Enterprise'
  1. Puppet Enterprise
  2. ENTERPRISE-1183

Console classification regex behaving differently on PE version 2018.1.x

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PE 2018.1.0
    • Fix Version/s: PE 2018.1.3
    • Component/s: Puppet Server, PuppetDB
    • Labels:
      None
    • Template:
    • Console Browser:
      Chrome
    • Acceptance Criteria:
      Hide

      2018.1.x also has to accept the filter and list applicable nodes 

      Show
      2018.1.x also has to accept the filter and list applicable nodes 
    • Method Found:
      Needs Assessment
    • CS Priority:
      Reviewed
    • CS Impact:
      This tracks back to an issue in PDB-3930. Will log CS Triage feedback there.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Hi,

      Node classification regex is behaving differently on latest version PEs (2018.1.0 and 2018.1.2).

      "rule": [  "and", [ "~", [ "fact", "hostname" ], "^pe-" ] ],  

      When I tried to add new nodes using above rule on 2016.4.11, 2017.3.2  and 2017.3.5, I can see nodes got filtered and listed on the console. 

      When I tried to use same rule on version 2018.1.0 and 2018.1.2, showing listed nodes as "0". 

      When I try symbol ^ only , this is listing all nodes, when I try to add character after the symbol* ^ *it's not listing. 

      I have attached my test case with this ticket for reference. 

       

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  karthikeyan.kanagaraj Karthikeyan Kanagaraj
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support