Uploaded image for project: 'OpenShift CFE'
  1. OpenShift CFE
  2. CFE-540

Sprint-222 SDN embedding work - Arkadeep

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • 13
    • False
    • None
    • False
    • CFE Sprint 222
    • 0

    Description

      This user story keeps track of the contribution of the SDN embedding work by Arkadeep for the sprint 222.

       

      Tentative story points:

      SDN-3050 - Created a BZ bug and assigned to Apiserver team as the issue is related to kube-apiserver (https://bugzilla.redhat.com/show_bug.cgi?id=2112022) (3 points)

      SDN-2997 - Created a BZ bug and assigned to Node team as the issue is related to cri-o (https://bugzilla.redhat.com/show_bug.cgi?id=2102722) (5 points)

      Attachments

        Issue Links

          clones

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-523 Sprint-221 SDN embedding work - Arkadeep

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-564 Sprint-223 SDN embedding work - Arkadeep

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. SDN-3050 healthz ProbeError - connection refused

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. SDN-2997 failure in test case "[sig-network] pods should successfully create sandboxes by other" - requests timing out

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rh-ee-arsen Arkadeep Sen
              rh-ee-arsen Arkadeep Sen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: