Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STOR-1499: inital config for azure-storage-azcopy repo #47814

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

RomanBednar
Copy link
Contributor

@RomanBednar RomanBednar commented Jan 18, 2024

Enhancement: openshift/enhancements#1542

This PR is a prerequisite to requesting ART to manage new content: https://source.redhat.com/groups/public/openshift/openshift_wiki/guidelines_for_requesting_new_content_managed_by_ocp_art

cc @openshift/storage

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 18, 2024
@RomanBednar RomanBednar changed the title inital config for azure-storage-azcopy repo STOR-1499: inital config for azure-storage-azcopy repo Jan 18, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 18, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 18, 2024

@RomanBednar: This pull request references STOR-1499 which is a valid jira issue.

In 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.

@RomanBednar RomanBednar force-pushed the azcopy-repo-conf branch 2 times, most recently from c03e02c to 5ba12dd Compare January 18, 2024 14:45
@RomanBednar RomanBednar changed the title STOR-1499: inital config for azure-storage-azcopy repo WIP: STOR-1499: inital config for azure-storage-azcopy repo Jan 18, 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 Jan 18, 2024
@RomanBednar RomanBednar changed the title WIP: STOR-1499: inital config for azure-storage-azcopy repo STOR-1499: inital config for azure-storage-azcopy repo Jan 19, 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 Jan 19, 2024
name: release
namespace: openshift
tag: golang-1.19
images:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

as:
- registry.ci.openshift.org/ocp/4.16:base
to: azure-storage-azcopy-base
promotion:
Copy link
Contributor Author

@RomanBednar RomanBednar Jan 19, 2024

Choose a reason for hiding this comment

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

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 19, 2024

@RomanBednar: This pull request references STOR-1499 which is a valid jira issue.

In response to this:

Enhancement: openshift/enhancements#1542

This PR is a prerequisite to requesting ART to manage new content: https://source.redhat.com/groups/public/openshift/openshift_wiki/guidelines_for_requesting_new_content_managed_by_ocp_art

cc @openshift/storage

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.

@RomanBednar
Copy link
Contributor Author

/retest

1 similar comment
@RomanBednar
Copy link
Contributor Author

/retest

@RomanBednar RomanBednar force-pushed the azcopy-repo-conf branch 2 times, most recently from aa067ca to 4ccc13a Compare January 22, 2024 15:19
@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 22, 2024
@jsafrane
Copy link
Contributor

/pj-rehearse

@RomanBednar RomanBednar force-pushed the azcopy-repo-conf branch 2 times, most recently from 56544d8 to 526e36b Compare January 29, 2024 12:22
@RomanBednar
Copy link
Contributor Author

/retest

Comment on lines 6 to 10
build_root:
image_stream_tag:
name: release
namespace: openshift
tag: golang-1.19
Copy link
Contributor

Choose a reason for hiding this comment

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

Go version should be defined in openshift/azure-storage-azcopy repository in .ci-operator.yaml, so ART can change it easily. Here we need:

build_root:
  from_repository: true

In addition, I am not sure we support 1.19 go images in 4.16.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jsafrane I see, that's better. I followed what we have in efs-utils and we don't use from_repository there. I'm adding ci-operator config to azcopy repo, should be merged first: openshift/azure-storage-azcopy#3

Copy link
Contributor

Choose a reason for hiding this comment

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

efs-utils are in python, I'm not sure why we use a go base image there... Maybe because it just works.

@jsafrane
Copy link
Contributor

/pj-rehearse

@jsafrane
Copy link
Contributor

/pj-rehearse pull-ci-openshift-azure-storage-azcopy-main-images

@jsafrane
Copy link
Contributor

/lgtm
/approve
(the storage parts)

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

jsafrane commented Jan 30, 2024

/pj-rehearse

why it does not rehearse the image build ?! it finally did a rehearsal

@RomanBednar
Copy link
Contributor Author

The rehearsal failed now because of the go shim in the builder image which enforces vendor mode, the build of azcopy works fine with RUN go build -o ./bin/azcopy . - adding vendor dir to azcopy repo should fix this: openshift/azure-storage-azcopy#4

Do we need to change the build so it's more similar or same to the way our CI does it?

@jsafrane
Copy link
Contributor

jsafrane commented Feb 5, 2024

/pj-rehearse

@RomanBednar
Copy link
Contributor Author

Current failure is caused by some .gitignore entries causing a few dependencies to be left out from vendor dir, I opened a PR to fix this: openshift/azure-storage-azcopy#5

@jsafrane
Copy link
Contributor

jsafrane commented Feb 6, 2024

/pj-rehearse

Copy link
Contributor

openshift-ci bot commented Feb 6, 2024

@RomanBednar: all tests passed!

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

@RomanBednar
Copy link
Contributor Author

/assign @bparees for approval

Copy link
Contributor

openshift-ci bot commented Feb 6, 2024

@RomanBednar: GitHub didn't allow me to assign the following users: for, approval.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @bparees for approval

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.

@bparees
Copy link
Contributor

bparees commented Feb 6, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Feb 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, jsafrane, RomanBednar

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 Feb 6, 2024
@RomanBednar
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 7, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit a95c74f into openshift:master Feb 7, 2024
21 checks passed
Copy link
Contributor

openshift-ci bot commented Feb 7, 2024

@RomanBednar: Updated the following 3 configmaps:

  • image-mirror-mappings configmap in namespace ci at cluster app.ci using the following files:
    • key mapping_origin_4_16 using file core-services/image-mirroring/openshift/mapping_origin_4_16
  • plugins configmap in namespace ci at cluster app.ci using the following files:
    • key core-services-prow-02_config-openshift-azure-storage-azcopy-_pluginconfig.yaml using file core-services/prow/02_config/openshift/azure-storage-azcopy/_pluginconfig.yaml
  • config configmap in namespace ci at cluster app.ci using the following files:
    • key core-services-prow-02_config-openshift-azure-storage-azcopy-_prowconfig.yaml using file core-services/prow/02_config/openshift/azure-storage-azcopy/_prowconfig.yaml

In response to this:

Enhancement: openshift/enhancements#1542

This PR is a prerequisite to requesting ART to manage new content: https://source.redhat.com/groups/public/openshift/openshift_wiki/guidelines_for_requesting_new_content_managed_by_ocp_art

cc @openshift/storage

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.

afaranha pushed a commit to afaranha/release that referenced this pull request Feb 8, 2024
ritmun pushed a commit to ritmun/release that referenced this pull request Feb 8, 2024
memodi pushed a commit to memodi/release that referenced this pull request Mar 14, 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants