Skip to content

Conversation

eslutsky
Copy link
Contributor

fixing in rebase periodic-ci-openshift-microshift-main-rebase-on-nightlies jobs

2025-05-16 23:59:41,998     DEBUG      Copying assets/crd/0000_03_config-operator_01_securitycontextconstraints.crd.yaml <- _output/staging/release-manifests/0000_03_config-operator_01_securitycontextconstraints-Default.crd.yaml
Traceback (most recent call last):
  File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 162, in <module>
    main()
  File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 155, in main
    handle_dir(asset)
  File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 129, in handle_dir
    handle_file(file, dst, new_src_prefix)
  File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 112, in handle_file
    copy(src, dst)
  File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 71, in copy
    shutil.copyfile(src, dst)
  File "/usr/lib64/python3.9/shutil.py", line 264, in copyfile
    with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: '_output/staging/release-manifests/0000_03_config-operator_01_securitycontextconstraints-Default.crd.yaml'

@openshift-ci openshift-ci bot requested review from dhensel-rh and ggiguash May 19, 2025 08:37
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2025
@eslutsky eslutsky changed the title file naming issue in config-operator scc USHIFT-5763: file naming issue in config-operator scc May 19, 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 May 19, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 19, 2025

@eslutsky: This pull request references USHIFT-5763 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

fixing in rebase periodic-ci-openshift-microshift-main-rebase-on-nightlies jobs

2025-05-16 23:59:41,998     DEBUG      Copying assets/crd/0000_03_config-operator_01_securitycontextconstraints.crd.yaml <- _output/staging/release-manifests/0000_03_config-operator_01_securitycontextconstraints-Default.crd.yaml
Traceback (most recent call last):
 File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 162, in <module>
   main()
 File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 155, in main
   handle_dir(asset)
 File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 129, in handle_dir
   handle_file(file, dst, new_src_prefix)
 File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 112, in handle_file
   copy(src, dst)
 File "/go/src/github.com/openshift/microshift/scripts/auto-rebase/handle_assets.py", line 71, in copy
   shutil.copyfile(src, dst)
 File "/usr/lib64/python3.9/shutil.py", line 264, in copyfile
   with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory: '_output/staging/release-manifests/0000_03_config-operator_01_securitycontextconstraints-Default.crd.yaml'

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.

Copy link
Contributor

@pacevedom pacevedom 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 May 19, 2025
Copy link
Contributor

openshift-ci bot commented May 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@eslutsky
Copy link
Contributor Author

/test e2e-aws-tests-bootc

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a7ec197 and 2 for PR HEAD 671ad1c in total

@pacevedom
Copy link
Contributor

/override ci/prow/e2e-aws-tests-bootc
This PR does not impact tests.

Copy link
Contributor

openshift-ci bot commented May 19, 2025

@pacevedom: Overrode contexts on behalf of pacevedom: ci/prow/e2e-aws-tests-bootc

In response to this:

/override ci/prow/e2e-aws-tests-bootc
This PR does not impact tests.

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.

Copy link
Contributor

openshift-ci bot commented May 19, 2025

@eslutsky: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit ee108d3 into openshift:main May 19, 2025
10 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants