Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-15066

[Tech debt] Enhance status sync logic to deal with ManifestWorks whose spec changes rapidly

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • MCE 2.8.0
    • ACM 2.13.0, MCE 2.8.0
    • Server Foundation
    • None
    • [Tech debt] Enhance status sync logic to deal with ManifestWorks whose spec changes rapidly
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 100% In Progress, 0% Done
    • Important

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      Epic Goal

      Resource leftover when ManifestWork changes rapidly.

      Steps to reproduce the behavior:

      • Create a ManifestWork that includes two resources: A and B.
      • After creating the ManifestWork, update its spec immediately to remove resource A.
      • There is a possibility that resource A may never be removed from the managed cluster.

      The community issue: https://github.com/open-cluster-management-io/ocm/issues/632

      Why is this important?

      ...

      Scenarios

      ...

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

              jqiu@redhat.com Jian Qiu
              leyan@redhat.com Le Yang
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: