Skip to content

Conversation

@kasturinarra
Copy link
Contributor

@kasturinarra kasturinarra commented Oct 8, 2025

Which issue(s) this PR addresses: This PR helps to add a scenario that enables all configs.

Closes #USHIFT-6168

@openshift-ci openshift-ci bot requested review from jerpeter1 and pmtk October 8, 2025 10:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kasturinarra

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 8, 2025
@kasturinarra kasturinarra changed the title Adding scenario to enable all configs USHIFT-6168: Adding scenario to enable all configs Oct 8, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@kasturinarra: This pull request references USHIFT-6168 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

Which issue(s) this PR addresses: This PR helps to add a scenario that enables all configs.

Closes #USHIFT-6168

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.

EOF"

# Restart MicroShift to apply TLS configuration
run_command_on_vm host1 "sudo systemctl restart microshift"
Copy link
Contributor

Choose a reason for hiding this comment

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

Use healthcheck to verify that MicroShift is fully initialized after restart.
Otherwise, we're risking to run into race conditions in the subsequent scripts.

EOF"

# Restart MicroShift to apply TLS configuration
run_command_on_vm host1 "sudo systemctl restart microshift"
Copy link
Contributor

Choose a reason for hiding this comment

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

Use healthcheck to verify that MicroShift is fully initialized after restart.
Otherwise, we're risking to run into race conditions in the subsequent scripts.

@kasturinarra kasturinarra force-pushed the USHIFT-6168 branch 2 times, most recently from 0ae05f9 to 16cac1b Compare October 21, 2025 06:34
@kasturinarra
Copy link
Contributor Author

/retest

@kasturinarra kasturinarra force-pushed the USHIFT-6168 branch 4 times, most recently from 24aabf9 to dd1724b Compare October 22, 2025 16:51
@kasturinarra
Copy link
Contributor Author

/test e2e-aws-tests-release

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@kasturinarra: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-tests-release-arm f4d77fc link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-bootc-release f4d77fc link true /test e2e-aws-tests-bootc-release
ci/prow/e2e-aws-tests-release f4d77fc link true /test e2e-aws-tests-release
ci/prow/e2e-aws-tests-bootc-release-arm f4d77fc link true /test e2e-aws-tests-bootc-release-arm

Full PR test history. Your PR dashboard.

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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants