Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-6496 Improve CI checks
  3. HDDS-7645

Kubernetes check should fail fast if cluster cannot start

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0
    • CI

    Description

      Kubernetes check proceeds to tests even if cluster is not able to start up. It should exit without trying to run the tests.

      **** Waiting until the k8s cluster is running ****
      
      ...
      4 pods are running out from the 5
      100 'all_pods_are_running' is failed...
      
      **** Executing robot tests scm-0 ****
      
      Defaulted container "scm" out of: scm, init (init)
      Unable to use a TTY - input is not a terminal or the right kind of file
      error: unable to upgrade connection: container not found ("scm")
      

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            adoroszlai Attila Doroszlai Assign to me
            adoroszlai Attila Doroszlai
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment