Skip to content

AGENT-858: Agent day2 ignition services#8093

Merged
openshift-merge-bot[bot] merged 14 commits intoopenshift:masterfrom
andfasano:agent-day2-ignition-services
Apr 8, 2024
Merged

AGENT-858: Agent day2 ignition services#8093
openshift-merge-bot[bot] merged 14 commits intoopenshift:masterfrom
andfasano:agent-day2-ignition-services

Conversation

@andfasano
Copy link
Contributor

This patch is based on PR #8080 (and also reuses service definitions from PR #8051 thanks @rwsu)

In this patch the Ignition asset is modified to enable the required services in case of add-node workflow

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 1, 2024

@andfasano: This pull request references AGENT-858 which is a valid jira issue.

Details

In response to this:

This patch is based on PR #8080 (and also reuses service definitions from PR #8051 thanks @rwsu)

In this patch the Ignition asset is modified to enable the required services in case of add-node workflow

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 Mar 1, 2024
@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 Mar 1, 2024
@openshift-ci openshift-ci bot requested review from AnnaZivkovic and bfournie March 1, 2024 18:09
@andfasano andfasano force-pushed the agent-day2-ignition-services branch from 247e237 to 275814a Compare March 6, 2024 14:43
@andfasano andfasano changed the title [WIP] AGENT-858: Agent day2 ignition services AGENT-858: Agent day2 ignition services Mar 6, 2024
@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 Mar 6, 2024
@andfasano andfasano force-pushed the agent-day2-ignition-services branch 4 times, most recently from c5d4bb9 to 6d34d8e Compare March 6, 2024 16:39
@andfasano
Copy link
Contributor Author

/retest

@andfasano andfasano force-pushed the agent-day2-ignition-services branch 2 times, most recently from 71b098a to 45e8797 Compare March 7, 2024 17:09
@rwsu
Copy link
Contributor

rwsu commented Mar 14, 2024

/test golint

Copy link
Contributor

@rwsu rwsu left a comment

Choose a reason for hiding this comment

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

/lgtm

In a follow up PR, it would be useful to log out some information about the ISO to help with debugging customer issues: perhaps cluster name and the IP addresses for the nodes being added.

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed lgtm Indicates that a PR is ready to be merged. labels Mar 14, 2024
Copy link
Contributor

@rwsu rwsu left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 15, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 26, 2024
@andfasano andfasano force-pushed the agent-day2-ignition-services branch from ad47230 to 828612c Compare March 29, 2024 13:25
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2024
@andfasano andfasano force-pushed the agent-day2-ignition-services branch from 479d224 to cac843c Compare April 2, 2024 10:32
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 2, 2024
if [[ "${cluster_id}" = "" ]]; then
sleep 2
fi
done
Copy link
Contributor

@sadasu sadasu Apr 4, 2024

Choose a reason for hiding this comment

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

Do we need a timeout followed by error message here? Alternatively, do we need a status_issue for this step?

Copy link
Contributor

Choose a reason for hiding this comment

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

Good question. I think here, the cluster_id should be available fairly quickly as the agent-add-node service has an After dependency on apply-host-config.service, which itself, has a dependency on agent-register-infra.service and it on agent-import-cluster.service. So by the time this script/service runs the cluster_id should be available.

@sadasu What is a status_issue? Could you explain? Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, as per the agent services architecture I'd expect that in case of issue the agent-register-cluster would prevent the other services, the loop here it's just to cope in case of slower execution (similar approach in another scritps)

Copy link
Contributor

Choose a reason for hiding this comment

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

@sadasu Please disregard my question. I see status_issue updated below.

@sadasu
Copy link
Contributor

sadasu commented Apr 4, 2024

/lgtm

One inline comment that doesn't have to stop progress of PR.

Copy link
Contributor

@rwsu rwsu left a comment

Choose a reason for hiding this comment

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

/approve

if [[ "${cluster_id}" = "" ]]; then
sleep 2
fi
done
Copy link
Contributor

Choose a reason for hiding this comment

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

Good question. I think here, the cluster_id should be available fairly quickly as the agent-add-node service has an After dependency on apply-host-config.service, which itself, has a dependency on agent-register-infra.service and it on agent-import-cluster.service. So by the time this script/service runs the cluster_id should be available.

@sadasu What is a status_issue? Could you explain? Thanks!

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rwsu

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:

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 Apr 4, 2024
@bfournie
Copy link
Contributor

bfournie commented Apr 5, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ac3ac89 and 2 for PR HEAD cac843c in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 304af67 and 1 for PR HEAD cac843c in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD b5ed3cd and 0 for PR HEAD cac843c in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision cac843c was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 7, 2024

@andfasano: 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-agent-compact-ipv4-appliance cac843c link false /test e2e-agent-compact-ipv4-appliance
ci/prow/okd-e2e-aws-ovn-upgrade cac843c link false /test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-agent-ha-dualstack cac843c link false /test e2e-agent-ha-dualstack
ci/prow/okd-e2e-agent-compact-ipv4 cac843c link false /test okd-e2e-agent-compact-ipv4
ci/prow/e2e-agent-compact-ipv4-appliance-diskimage cac843c link false /test e2e-agent-compact-ipv4-appliance-diskimage

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/test-infra repository. I understand the commands that are listed here.

@andfasano
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 8, 2024
@andfasano
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9a8b820 and 2 for PR HEAD cac843c in total

@openshift-merge-bot openshift-merge-bot bot merged commit 54d9c8e into openshift:master Apr 8, 2024
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants