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
TRT-1503: Tools image no longer has python;adding #1682
TRT-1503: Tools image no longer has python;adding #1682
Conversation
https://prow.ci.openshift.org/?type=periodic&job=*nightly*4.16*&cluster=vsphere02
|
71be14c
to
4f34e8a
Compare
/jira refresh |
@jcpowermac: No Jira issue is referenced in the title of this pull request. 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. |
@jcpowermac: This pull request references TRT-1503 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 story to target the "4.16.0" version, but no target version was set. 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. |
/assign ardaguclu |
/assign @soltysh |
@@ -36,6 +36,7 @@ RUN INSTALL_PKGS="\ | |||
xfsprogs \ | |||
fio \ | |||
stress-ng \ | |||
python36 \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why strictly python 3.6?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was the package available when I tested it locally. I am not partial to a specific minor of 3.x if you have another suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
first version of this PR was python3
, I am wondering is there any reason to use python36
. If not, I'd prefer to move forward with python3
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jcpowermac you are right. python3
gaves an error package python3 is not installed
with an exit code 1
. We have to use python36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the reason why I set it to python36
1cda4c8
to
227e8d9
Compare
Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
python39.x86_64 : Version 3.9 of the Python interpreter
seems to be the latest available Red Hat Enterprise Linux release 8.6 (Ootpa)
227e8d9
to
4b6689a
Compare
Switched to 39, let's see if it works. |
Also, I just did:
so it looks like the tools image already has the necessary python, so I'm confused now. |
Hmmm, I check the one referenced above that does not have python registry.ci.openshift.org/ocp/4.16-art-latest-2024-02-12-052140:tools. It seems that registry.ci.openshift.org/ocp/release:4.16.0-0.ci-2024-02-12-052859 has it. |
Likewise, only periodics are failing with missing python in the vsphere dns step. I narrowed it down to: has python - registry.ci.openshift.org/ocp/4.16-art-latest-2024-02-08-073857:tools |
Yeah, I just checked the nightlies (registry.ci.openshift.org/ocp/release:4.16.0-0.nightly-2024-02-11-143825) those indeed are missing the python. But to keep it consistent, let's use the one that's already included in the ci builds, in that case. That was 3.6.8, so can you revert to that? Sorry for the back and forth 😅 |
4b6689a
to
9433753
Compare
np! moved back |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold cancel
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, jcpowermac, soltysh 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 |
cf7b09c
into
openshift:master
[ART PR BUILD NOTIFIER] This PR has been included in build openshift-enterprise-cli-container-v4.16.0-202402130109.p0.gcf7b09c.assembly.stream.el8 for distgit openshift-enterprise-cli. |
Something has recently changed with the parent images of the tools image where it no longer has python causing CI failures. Adding
python3
to the tools image.