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

Draft: Skip broken symlink when copying /etc/pki #1112

Closed
wants to merge 2 commits into from

Conversation

dkubek
Copy link
Member

@dkubek dkubek commented Aug 13, 2023

Currently, when copying the /etc/pki folder into the container, the context.copytree_from function is used which crashes when it encounters a broken symlink. Instead, we copy directory manually skipping all broken symlinks.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1969978

dkubek added 2 commits August 9, 2023 12:18
Currently, upgrades with custom repositories hosted on private https
servers are not functional. The reason is that the server certificates
are unavailable in the upgrade container as they are not copied from the
source system; therefore, the upgrade fails when trying to access the
custom repository.

This change fixes the issue by copying all files from the ``/etc/pki``
folder of the source system, while respecting any new files installed by
packages into the container. If a conflict arises a file installed by a
package into a container is preferred. Any broken symlinks are skipped
and ignored.
@github-actions
Copy link

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

  • review please @oamg/developers to notify leapp developers of the review request
  • /packit copr-build to submit a public copr build using packit

Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build. If you need a different version of leapp from PR#42, use /packit test oamg/leapp#42

To launch regression testing public members of oamg organization can leave the following comment:

  • /rerun to schedule basic regression tests using this pr build and latest upstream leapp build as artifacts
  • /rerun 42 to schedule basic regression tests using this pr build and leapp*PR42* as artifacts
  • /rerun-sst to schedule sst tests using this pr build and latest upstream leapp build as artifacts
  • /rerun-sst 42 to schedule sst tests using this pr build and leapp*PR42* as artifacts

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra.

@pirat89 pirat89 modified the milestones: 8.9/9.3, 8.10/9.4 Aug 15, 2023
@fernflower fernflower marked this pull request as draft September 7, 2023 14:09
@abadger
Copy link
Member

abadger commented Nov 2, 2023

@dkubek Is this PR obsoleted by #1135 ?

@dkubek
Copy link
Member Author

dkubek commented Nov 2, 2023

@abadger Oh yes, this will be fixed in #1135 now. Closing

@dkubek dkubek closed this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants