Make remediation scripts checking for log id 6698300 have distinct methods of checking if issue is remediated

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2025-02-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, rewrite_embedded_bucket_id_control_min_mismatch.js and rewrite_timeseries_bucket_version_mismatch.js both check for log id 6698300 to determine if the remediation is successful/unsuccessful. However, in the case that a user has both of these issues, this can be confusing because a user running one of the scripts may be confused if there is still the log id 6698300 but it may be due to the other 6698300 error. We want to use getLog and then parse the information that would enable us to see the cause of the 6698300 log id to distinguish between these two issues happening.

            Assignee:
            Stephanie Eristoff
            Reporter:
            Stephanie Eristoff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: