Skip to content

USHIFT-6133: Add more robot framework test cases#5776

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kasturinarra:host-file-update
Dec 1, 2025
Merged

USHIFT-6133: Add more robot framework test cases#5776
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kasturinarra:host-file-update

Conversation

@kasturinarra
Copy link
Contributor

@kasturinarra kasturinarra commented Nov 20, 2025

Which issue(s) this PR addresses: Adding three more robot framework test cases that check if hosts-file is dynamically updated with out restarting microshift, disabling microshift is deleting the hosts-file configmap in openshift-dns namespace, validating cluster DNS takes precedence over host file.

Closes #USHIFT-6133

@kasturinarra kasturinarra marked this pull request as draft November 20, 2025 13:51
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 20, 2025
@kasturinarra kasturinarra changed the title Add more robot framework test cases USHIFT-6133: Add more robot framework test cases Nov 20, 2025
@openshift-ci openshift-ci bot requested review from agullon and eslutsky November 20, 2025 13:51
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2025

@kasturinarra: This pull request references USHIFT-6133 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses: Adding three more robot framework test cases that check if hosts-file is dynamically updated with out restarting microshift, disabling microshift is deleting the hosts-file configmap in openshift-dns namespace, validating cluster DNS takes precedence over host file.

Closes #USHIFT-6133

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 20, 2025
@kasturinarra kasturinarra marked this pull request as ready for review December 1, 2025 09:37
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 1, 2025
@openshift-ci openshift-ci bot requested a review from ggiguash December 1, 2025 09:38
@kasturinarra kasturinarra force-pushed the host-file-update branch 2 times, most recently from 0dd9a18 to f31a87c Compare December 1, 2025 12:46
@kasturinarra
Copy link
Contributor Author

/retest

Router Should Resolve Hostname
[Documentation] Check if the router pod resolves the given hostname
[Arguments] ${hostname}
[Arguments] ${hostname} ${expected_ip}=${EMPTY}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need ${expected_ip}=${EMPTY}, where is that being called?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have used it for a different test case which i removed, but forgot to remove this. Now removed it. Could you please help review again ? thanks !!

@eslutsky
Copy link
Contributor

eslutsky commented Dec 1, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 1, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, kasturinarra

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [eslutsky,kasturinarra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

@kasturinarra: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@kasturinarra
Copy link
Contributor Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 1, 2025
@openshift-ci-robot
Copy link

@kasturinarra: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 24cd1f3 into openshift:main Dec 1, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants