Skip to content

Conversation

@sosiouxme
Copy link
Member

The registry for imagestreams was previously recorded as an IP, which
could change if the registry service were re-created. Now it is a
cluster hostname, which should be unchanging even if re-created. Just
ensure it is the right hostname.

fix bug 1488059
https://bugzilla.redhat.com/show_bug.cgi?id=1488059

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 6, 2017
@openshift-merge-robot openshift-merge-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 6, 2017
@sosiouxme sosiouxme added component/diagnostics kind/bug Categorizes issue or PR as related to a bug. labels Sep 6, 2017
@sosiouxme sosiouxme requested review from liggitt and soltysh September 6, 2017 20:51
@sosiouxme sosiouxme assigned sosiouxme and unassigned soltysh and liggitt Sep 6, 2017
serviceIpPort := fmt.Sprintf("%s:%d", service.Spec.ClusterIP, service.Spec.Ports[0].Port)
serviceHostPort := fmt.Sprintf("%s.%s.svc:%d", registryName, service.ObjectMeta.Namespace, service.Spec.Ports[0].Port)
if cacheHost != serviceIpPort && cacheHost != serviceHostPort {
r.Error("DClu1019", nil, fmt.Sprintf(clRegISMismatch, registryName, serviceIpPort, cacheHost))
Copy link
Contributor

Choose a reason for hiding this comment

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

Should the message say something about serviceHostPort?

Copy link
Member Author

Choose a reason for hiding this comment

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

I guess that would make sense, thanks.

The registry for imagestreams was previously recorded as an IP, which
could change if the registry service were re-created.  Now it is a
cluster hostname, which should be unchanging even if re-created. Just
ensure it is the right hostname.

fixes bug 1488059
https://bugzilla.redhat.com/show_bug.cgi?id=1488059
@sosiouxme sosiouxme force-pushed the 20170906-oadm-diag-clusterregistry-bz1488059 branch from 17065ca to 5bbe044 Compare September 7, 2017 13:36
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 7, 2017
@sosiouxme
Copy link
Member Author

@liggitt addressed that.

Is there a magic bot command to indicate this should be cherry-picked to 3.6?

@liggitt
Copy link
Contributor

liggitt commented Sep 7, 2017

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 7, 2017
@openshift-merge-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, sosiouxme

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@sosiouxme sosiouxme removed the request for review from soltysh September 7, 2017 15:24
@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue (batch tested with PRs 14825, 15756, 16178, 16188, 16189)

@openshift-merge-robot openshift-merge-robot merged commit 5c677dc into openshift:master Sep 7, 2017
@sosiouxme sosiouxme deleted the 20170906-oadm-diag-clusterregistry-bz1488059 branch November 13, 2017 18:50
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. component/diagnostics kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants