Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-2031

Connection information is wrongly listed for noobaa-cli diagnose health --all_connection_details

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • odf-4.19
    • odf-4.18.2
    • noobaa-nc
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • ?
    • ?
    • Committed
    • Release Note Not Required
    • None

       

      *Description of problem - connection is proper but still it is getting listed in invalid storages. i am not sure why it is invalid storages it should be invalid connections

       

      *The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI): Bare metal

       

      *The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):5.18.2

       

       

      The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):

       RHEL

       

      Does this issue impact your ability to continue to work with the product?

       

       

      Is there any workaround available to the best of your knowledge?

       

       

      Can this issue be reproduced? If so, please provide the hit rate

       

       

      Can this issue be reproduced from the UI?

       

      If this is a regression, please provide more details to justify this:

       

      Steps to Reproduce:

      1. # /usr/local/bin/noobaa-cli diagnose health --all_connection_details 2>/dev/null
      {
      "response": {
      "code": "HealthStatus",
      "message": "Health status retrieved successfully",
      "reply": {
      "service_name": "noobaa",
      "status": "OK",
      "memory": "312.6M",
      "checks": {
      "services": [

      { "name": "noobaa", "service_status": "active", "pid": "903187" }

      ],
      "endpoint": {
      "endpoint_state": {
      "response":

      { "response_code": "RUNNING", "response_message": "Endpoint running successfuly." }

      ,
      "total_fork_count": 2,
      "running_workers": [
      2,
      1
      ]
      },
      "error_type": "TEMPORARY"
      },
      "config_directory_status": {
      "phase": "CONFIG_DIR_UNLOCKED",
      "config_dir_version": "1.0.0",
      "upgrade_package_version": "5.18.0",
      "upgrade_status":

      { "message": "there is no in-progress upgrade" }

      },
      "connections_status": {
      "invalid_storages": [

      { "name": "http_notif", "config_path": "/mnt/cesSharedRoot/ces/s3-config/connections/http_notif.json", "code": "ENOENT" }

      ],
      "valid_storages": [],
      "error_type": "TEMPORARY"
      }
      }
      }
      }
      }

      2.

      3.

       

      The exact date and time when the issue was observed, including timezone details:

       

      Actual results:

       

       

      Expected results:

       

      Logs collected and log location:

       

      Additional info:

       
       

              rh-ee-nbecker Nimrod Becker
              ramya.c3 Ramya MC (Inactive)
              Nimrod Becker
              Uday Kurundwade Uday Kurundwade
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: