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

Bug 1863390: Fix arch for python3-bcrypt #39

Merged
merged 1 commit into from Aug 18, 2020

Conversation

elfosardo
Copy link

@elfosardo elfosardo commented Aug 17, 2020

The python3-bcrypt library is going to be installed inside the
ipa-ramdisk based on its architecture.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 17, 2020
@elfosardo elfosardo requested review from dtantsur, iurygregory, bfournie, derekhiggins and stbenjam and removed request for dhellmann August 17, 2020 10:33
@elfosardo
Copy link
Author

/retest

1 similar comment
@elfosardo
Copy link
Author

/retest

@elfosardo elfosardo changed the title Fix arch for python3-bcrypt Bug 1863390: Fix arch for python3-bcrypt Aug 18, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. label Aug 18, 2020
@openshift-ci-robot
Copy link

@elfosardo: This pull request references Bugzilla bug 1863390, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1863390: Fix arch for python3-bcrypt

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.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Aug 18, 2020
Dockerfile.ocp Outdated
@@ -13,7 +13,7 @@ RUN dnf upgrade -y && \
&& \
dnf download --destdir /tmp/packages \
openstack-ironic-python-agent \
python3-bcrypt \
python3-bcrypt.x86_64 \
Copy link

@hardys hardys Aug 18, 2020

Choose a reason for hiding this comment

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

Any idea how OCP multi-arch builds work? I assume some variable is passed in at build time, so I wonder can we find an example of that and do the same here to avoid hard-coding?

Copy link

Choose a reason for hiding this comment

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

Or I see we're using $(uname -m) to determine the arch for the IPA RPM, can we do the same here?

Copy link
Author

Choose a reason for hiding this comment

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

We need to hard-code here because we're installing in ipa-ramdisk which is x86-64 only
Unfortunately in the images both x86-64 and ppc64 repositories are included, which is ok if we need to control only what's installed on the image itself.
In case we need to do something exotic (like this case or like the builder in the ironic image), we have to force the arch.

Copy link
Author

Choose a reason for hiding this comment

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

scratch that, I forgot we also build (and install) ipa-ramdisk natively on ppc64, so we need to change arch to variable, not hard-code it
thanks for that!

The python3-bcrypt library is going to be installed inside the
ipa-ramdisk based on its architecture.
@openshift-ci-robot
Copy link

@elfosardo: This pull request references Bugzilla bug 1863390, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1863390: Fix arch for python3-bcrypt

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.

@hardys
Copy link

hardys commented Aug 18, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 18, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, hardys, iurygregory

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-merge-robot openshift-merge-robot merged commit e6b5fa9 into openshift:master Aug 18, 2020
@openshift-ci-robot
Copy link

@elfosardo: Some pull requests linked via external trackers have merged: openshift/ironic-ipa-downloader#39. The following pull requests linked via external trackers have not merged:

In response to this:

Bug 1863390: Fix arch for python3-bcrypt

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.

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. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants