Uploaded image for project: 'Container / Cluster Management (XCM) Strategy'
  1. Container / Cluster Management (XCM) Strategy
  2. XCMSTRAT-754

M2: Actionable error messages for cluster provisioning failures

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • XCMSTRAT-29OCM UI/UX
    • 100% To Do, 0% In Progress, 0% Done
    • 0

      Feature Overview (aka. Goal Summary)  

      As a customer, I should be provided with meaningful and actionable error messages when my cluster installation fails. The error messages should indicate why the failure happened and, if it is an issue at my end, how I can resolve it to successfully provision a new cluster.
       

      Goals (aka. expected user outcomes)

      • Include documentation links within error messages
      • Include KCS article links within error messages

      The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

       

      Requirements (aka. Acceptance Criteria):

      • Review existing error messages in OCM
      • Improve the error message based on discussion with Docs and UX teams
      • Reference docs links in error messages and bubble those up in the UI and CLI outputs
      • Include links to KCS articles for error messages where we have them
      • Create KCS articles for additional error messages where applicable

      KCS articles created for OCM errors:

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

            rhn-engineering-abhgupta Abhishek Gupta
            rhn-engineering-abhgupta Abhishek Gupta
            Jericho Keyne
            Ling Lan Ling Lan
            Yu Wang Yu Wang
            Kevin Blake Kevin Blake
            Allison Wolfe Allison Wolfe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: