NO-JIRA: feat(tnf): add resource-agents steps under baremetalds/two-node/fencing#75815
NO-JIRA: feat(tnf): add resource-agents steps under baremetalds/two-node/fencing#75815jaypoulz wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
@jaypoulz: This pull request explicitly references no jira issue. DetailsIn response to this:
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
added
the
jira/valid-reference
openshift-merge-robot
added
the
needs-rebase
openshift-ci-robot
added
the
rehearsals-ack
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jaypoulz The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
jaypoulz
force-pushed
the
tnf-update-rhcos-resource-agents
branch
from
918c12a to
57e8ba8
Compare
openshift-merge-robot
removed
the
needs-rebase
openshift-ci-robot
removed
the
rehearsals-ack
jaypoulz
force-pushed
the
tnf-update-rhcos-resource-agents
branch
2 times, most recently
from
017321d to
bde5021
Compare
| - nested-podman | ||
| cron: 19 10,20 * * * | ||
| steps: | ||
| cluster_profile: equinix-edge-enablement |
There was a problem hiding this comment.
Silly question - is actually pointing to OFICR?
There was a problem hiding this comment.
Yes, the legacy name was likely kept due to too many places to find/replace
There was a problem hiding this comment.
@eggfoobar is the expert here, but I don't think we changed the cluster profile name to offcir. We just added offcir secrets to the old profile.
There was a problem hiding this comment.
ack. Let's make sure we have a Jira somewhere in the backlog to fix this since it falls into the "tribal knowledge" category.
There was a problem hiding this comment.
Yup, it's just an alias for our creds, future housekeeping we can change it, just needs some coordination. It's low priority until we get some cycles since there might be CI interruptions during the move.
More info on it can be found in the ci docs, https://docs.ci.openshift.org/how-tos/adding-a-cluster-profile/#what-is-a-cluster-profile
|
/pj-rehease periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview periodic-ci-openshift-release-main-nightly-5.0-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview |
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview periodic-ci-openshift-release-main-nightly-5.0-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview |
|
@jaypoulz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
…ode/fencing - Move update-rhcos-resource-agents and delete-rhcos-resource-agents-image to baremetalds/two-node/fencing; rename to baremetalds-two-node-fencing-* - Wire agent and baremetalds-two-node-fencing-recovery workflows to new step refs; set OWNERS to edge-enablement approvers/reviewers - REPO path: get release image and version from deployed cluster (clusterversion) only; step must run after cluster deployment - Add hack/tnf-resource-agents-build test (Stream 9/10) and align CI step with local build (CRB/EPEL, libqb from source when needed) - Add TNF REPO job variant and nested-podman in release nightlies (4.22, 5.0) and installer presubmits Made-with: Cursor
jaypoulz
force-pushed
the
tnf-update-rhcos-resource-agents
branch
from
bde5021 to
dd11412
Compare
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview periodic-ci-openshift-release-main-nightly-5.0-e2e-metal-ovn-two-node-fencing-recovery-repo-ra-techpreview |
|
@jaypoulz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@jaypoulz: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
6 participants
Made-with: Cursor