Skip to content

Conversation

@hardcoretime
Copy link
Contributor

@hardcoretime hardcoretime commented Nov 10, 2025

Why do we need it, and what problem does it solve?

The current host redirects to another domain, which causes a test failure.

What is the expected result?

The new external host should return an HTTP status code of 200.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

The current host redirects to another domain.

Signed-off-by: Roman Sysoev <roman.sysoev@flant.com>
@hardcoretime hardcoretime merged commit 7a02ef2 into main Nov 10, 2025
30 of 33 checks passed
@hardcoretime hardcoretime deleted the test/vm/replace-external-host-in-connectivity-test branch November 10, 2025 09:55
nevermarine pushed a commit that referenced this pull request Nov 14, 2025
Signed-off-by: Roman Sysoev <roman.sysoev@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants