-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
fix up latest tags and add new scl image versions #5409
Conversation
@smarterclayton @soltysh ptal. Note that latest still points to the older versions for now because the SCL images aren't actually released yet, so the rhel images aren't available. So we'll need to update this one more time before 3.1 ships, unless we want to ship 3.1 using the existing platform versions. |
(also note that i think the reference logic was backwards before... i had the "2.0" tag following/referencing the "latest" tag in the spec, instead of the other way around. that is fixed with this PR. |
LGTM |
I'm removing my LGTM, because with current configuration |
@@ -14,7 +14,11 @@ | |||
"dockerImageRepository": "openshift/ruby-20-centos7", |
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.
Remove this and every occurence, where you specify images to be imported manually.
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.
yeah i was debating whether to leave that or not... if i remove it, nothing (ie tags we don't specify explicitly) will get automatically imported, i'm not sure that's what we want. so i think it's appropriate to leave it.
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.
Hrm - that may actually be what we want. We only want to import tags we
whitelist for openshift customers.
On Tue, Oct 27, 2015 at 12:43 PM, Ben Parees notifications@github.com
wrote:
In examples/image-streams/image-streams-centos7.json
#5409 (comment):@@ -14,7 +14,11 @@
"dockerImageRepository": "openshift/ruby-20-centos7",yeah i was debating whether to leave that or not... if i remove it,
nothing (ie tags we don't specify explicitly) will get automatically
imported, i'm not sure that's what we want. so i think it's appropriate to
leave it.—
Reply to this email directly or view it on GitHub
https://github.com/openshift/origin/pull/5409/files#r43149082.
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.
ok. if we're in agreement that we only want to import explicit tags i'll remove the dockerImageRepository field.
2fc7e71
to
5da3431
Compare
LGTM, thanks @bparees ! |
5da3431
to
117867d
Compare
@@ -64,7 +64,7 @@ oc describe istag/mysql:latest | |||
[ "$(oc describe istag/mysql:latest | grep "Image Created:")" ] | |||
[ "$(oc describe istag/mysql:latest | grep "Image Name:")" ] | |||
name=$(oc get istag/mysql:latest --template='{{ .image.metadata.name }}') | |||
imagename="isimage/mysql@${name:0:7}" | |||
imagename="isimage/mysql@${name}" |
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.
@smarterclayton i'm not clear on why were were truncating this value previously? but it seems to be causing failures now that we have two valid images that start with mysql
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.
To verify that you can retrieve images by their short ID. Which we still
want to do, but if there are two we should be able to choose the first.
I'm not sure why there are 2 now though.
On Tue, Oct 27, 2015 at 11:58 PM, Ben Parees notifications@github.com
wrote:
In test/cmd/images.sh
#5409 (comment):@@ -64,7 +64,7 @@ oc describe istag/mysql:latest
[ "$(oc describe istag/mysql:latest | grep "Image Created:")" ]
[ "$(oc describe istag/mysql:latest | grep "Image Name:")" ]
name=$(oc get istag/mysql:latest --template='{{ .image.metadata.name }}')
-imagename="isimage/mysql@${name:0:7}"
+imagename="isimage/mysql@${name}"@smarterclayton https://github.com/smarterclayton i'm not clear on why
were were truncating this value previously? but it seems to be causing
failures now that we have two valid images that start with mysql—
Reply to this email directly or view it on GitHub
https://github.com/openshift/origin/pull/5409/files#r43216441.
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.
Mysql 55 and mysql 56.
Ben Parees | OpenShift
On Oct 28, 2015 12:23 AM, "Clayton Coleman" notifications@github.com
wrote:
In test/cmd/images.sh
#5409 (comment):@@ -64,7 +64,7 @@ oc describe istag/mysql:latest
[ "$(oc describe istag/mysql:latest | grep "Image Created:")" ]
[ "$(oc describe istag/mysql:latest | grep "Image Name:")" ]
name=$(oc get istag/mysql:latest --template='{{ .image.metadata.name }}')
-imagename="isimage/mysql@${name:0:7}"
+imagename="isimage/mysql@${name}"To verify that you can retrieve images by their short ID. Which we still
want to do, but if there are two we should be able to choose the first. I'm
not sure why there are 2 now though.
… <#150acafb50312f2c_>
On Tue, Oct 27, 2015 at 11:58 PM, Ben Parees notifications@github.com
wrote: In test/cmd/images.sh <#5409 (comment)
https://github.com/openshift/origin/pull/5409#discussion_r43216441>: >
@@ -64,7 +64,7 @@ oc describe istag/mysql:latest > [ "$(oc describe
istag/mysql:latest | grep "Image Created:")" ] > [ "$(oc describe
istag/mysql:latest | grep "Image Name:")" ] > name=$(oc get
istag/mysql:latest --template='{{ .image.metadata.name }}') >
-imagename="isimage/mysql@${name:0:7}" > +imagename="isimage/mysql@${name}"
@smarterclayton https://github.com/smarterclayton <
https://github.com/smarterclayton> i'm not clear on why were were
truncating this value previously? but it seems to be causing failures now
that we have two valid images that start with mysql — Reply to this email
directly or view it on GitHub <
https://github.com/openshift/origin/pull/5409/files#r43216441>.—
Reply to this email directly or view it on GitHub
https://github.com/openshift/origin/pull/5409/files#r43217260.
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.
To verify that you can retrieve images by their short ID. Which we still want to do, but if there are two we should be able to choose the first. I'm not sure why there are 2 now though.
what is the "short id"? what this code was grabbing was something like "mysql@sha:"
and there are now 2 because you have the mysql56 and mysql55 images, both of which start with that string.
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.
Then grow the length. The sha is different
On Wed, Oct 28, 2015 at 1:11 PM, Ben Parees notifications@github.com
wrote:
In test/cmd/images.sh
#5409 (comment):@@ -64,7 +64,7 @@ oc describe istag/mysql:latest
[ "$(oc describe istag/mysql:latest | grep "Image Created:")" ]
[ "$(oc describe istag/mysql:latest | grep "Image Name:")" ]
name=$(oc get istag/mysql:latest --template='{{ .image.metadata.name }}')
-imagename="isimage/mysql@${name:0:7}"
+imagename="isimage/mysql@${name}"To verify that you can retrieve images by their short ID. Which we still
want to do, but if there are two we should be able to choose the first. I'm
not sure why there are 2 now though.what is the "short id"? what this code was grabbing was something like
"mysql@sha:"and there are now 2 because you have the mysql56 and mysql55 images, both
of which start with that string.—
Reply to this email directly or view it on GitHub
https://github.com/openshift/origin/pull/5409/files#r43286739.
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.
Sure, i'm just trying to understand what "retrieve images by their short ID" means... is short ID specifically defined, or are you just saying "something shorter than the full id"?
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.
Yes, the REST API uses the provided image id for image stream images as a
prefix and will find all matches - if there is just one, it is accepted, if
there are multiple, it gives an error. Basically like Git.
On Wed, Oct 28, 2015 at 3:06 PM, Ben Parees notifications@github.com
wrote:
In test/cmd/images.sh
#5409 (comment):@@ -64,7 +64,7 @@ oc describe istag/mysql:latest
[ "$(oc describe istag/mysql:latest | grep "Image Created:")" ]
[ "$(oc describe istag/mysql:latest | grep "Image Name:")" ]
name=$(oc get istag/mysql:latest --template='{{ .image.metadata.name }}')
-imagename="isimage/mysql@${name:0:7}"
+imagename="isimage/mysql@${name}"Sure, i'm just trying to understand what "retrieve images by their short
ID" means... is short ID specifically defined, or are you just saying
"something shorter than the full id"?—
Reply to this email directly or view it on GitHub
https://github.com/openshift/origin/pull/5409/files#r43302985.
085a0de
to
8f1f6a9
Compare
[test] |
8f1f6a9
to
7f18ec0
Compare
imagestreams appear to be disturbingly unreliable with these changes.... not sure what is going on.
|
Individual tags are added in order - it's possible that the end result is On Oct 28, 2015, at 11:01 PM, Ben Parees notifications@github.com wrote: imagestreams appear to be disturbingly unreliable with these changes.... !!! Error in test/cmd/newapp.sh:41 — |
7f18ec0
to
6413f84
Compare
do they get displayed in sorted order, or did i just get lucky on that in my local testing and i need to make my grep more tolerant? |
I thought Michal added a sort in string flexographic order. On Wed, Oct 28, 2015 at 11:14 PM, Ben Parees notifications@github.com
|
flexographic Is my new favorite word |
@liggitt it's your ability to jump into a pull you weren't tagged in, within mere seconds, that makes me default to the assumption that all comments i read were posted by you. you're everywhere. and yes, +1 to flexographic. I pity my next interview candidate......."how would you write a flexographic sort?" |
The look of panic on the interviewee's face would be worth the eternity in Hell. |
4396ae3
to
328b98f
Compare
328b98f
to
aa60db9
Compare
this might finally be passing. [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6406/) (Image: devenv-rhel7_2594) |
Evaluated for origin merge up to aa60db9 |
Evaluated for origin test up to aa60db9 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6406/) |
Merged by openshift-bot
No description provided.