[jira] [Updated] (HDDS-14896) Use separate container for clients in rolling-upgrade suite

["Zita Dombi (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-14896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zita Dombi updated HDDS-14896:
------------------------------
    Description: 
This is in the rolling-upgrade suite's driver.sh:
{code:java}
  # Check if this SCM container is running, as during a rolling upgrade it does stop-start one-by-one and
  # we want to run write/read tests while one service is unavailable. Choose SCM (the container where the generate and
  # validate robot tests are running) considering availability.
  if [[ "$(docker inspect -f '{{.State.Running}}' "ha-${SCM}-1" 2>/dev/null)" != "true" ]]; then
    local fallback_scm
    fallback_scm="$(docker-compose --project-directory="$TEST_DIR/compose/ha" config --services | grep scm | grep -v "^${SCM}$" | head -n1)"
    if [[ -n "$fallback_scm" ]]; then
      export SCM="$fallback_scm"
    fi
  fi
{code}
Remove this workaround and use a separate container for the clients, similar to the xcompat tests.

[ref review comment|https://github.com/apache/ozone/pull/9877#discussion_r2966914076]

  was:
This is in the rolling-upgrade suite's driver.sh:

{code:java}
  # Check if this SCM container is running, as during a rolling upgrade it does stop-start one-by-one and
  # we want to run write/read tests while one service is unavailable. Choose SCM (the container where the generate and
  # validate robot tests are running) considering availability.
  if [[ "$(docker inspect -f '{{.State.Running}}' "ha-${SCM}-1" 2>/dev/null)" != "true" ]]; then
    local fallback_scm
    fallback_scm="$(docker-compose --project-directory="$TEST_DIR/compose/ha" config --services | grep scm | grep -v "^${SCM}$" | head -n1)"
    if [[ -n "$fallback_scm" ]]; then
      export SCM="$fallback_scm"
    fi
  fi
{code}

Remove this workaround and use a separate container for the clients, similar to the xcompat tests.



> Use separate container for clients in rolling-upgrade suite
> -----------------------------------------------------------
>
>                 Key: HDDS-14896
>                 URL: https://issues.apache.org/jira/browse/HDDS-14896
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Zita Dombi
>            Assignee: Zita Dombi
>            Priority: Major
>
> This is in the rolling-upgrade suite's driver.sh:
> {code:java}
>   # Check if this SCM container is running, as during a rolling upgrade it does stop-start one-by-one and
>   # we want to run write/read tests while one service is unavailable. Choose SCM (the container where the generate and
>   # validate robot tests are running) considering availability.
>   if [[ "$(docker inspect -f '{{.State.Running}}' "ha-${SCM}-1" 2>/dev/null)" != "true" ]]; then
>     local fallback_scm
>     fallback_scm="$(docker-compose --project-directory="$TEST_DIR/compose/ha" config --services | grep scm | grep -v "^${SCM}$" | head -n1)"
>     if [[ -n "$fallback_scm" ]]; then
>       export SCM="$fallback_scm"
>     fi
>   fi
> {code}
> Remove this workaround and use a separate container for the clients, similar to the xcompat tests.
> [ref review comment|https://github.com/apache/ozone/pull/9877#discussion_r2966914076]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org