Skip to content

Conversation

@abhinavdahiya
Copy link
Contributor

cluster-image-registry-operator now owns setting these up for access to internal registry.
https://github.com/openshift/cluster-image-registry-operator/blob/master/deploy/08-ca-daemonset.yaml#L26-L46

This fixes MCD and the cluster-image-registry-operator stepping on each other. And MCD currently reboot on syncing any
change which causes disruption on masters recurringly.

Should help dropping ownership of /etc/hosts and /etc/docker.d/certs/... from daemon
#224 (comment)

`cluster-image-registry-operator` now owns setting these up for access to internal registry.
https://github.com/openshift/cluster-image-registry-operator/blob/master/deploy/08-ca-daemonset.yaml#L26-L46

This fixes MCD and the `cluster-image-registry-operator` stepping on each other. And MCD currently reboot on syncing any
change which causes disruption on masters recurringly.
@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 8, 2018
@wking
Copy link
Member

wking commented Dec 8, 2018

/lgtm

Offloading registry certs to the registry operator and /etc/hosts to the DNS operator makes sense to me. And if this greens CI, I'm fine landing it without waiting for everyone else to wake up ;). We can always revert in the morning if it doesn't hold up to sunlight 🦇 😉

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 8, 2018
@wking
Copy link
Member

wking commented Dec 8, 2018

Hrm, router didn't come up:

timeout waiting for openshift-ingress/deploy/router-default to be available
2018/12/08 09:37:40 Container test in pod e2e-aws failed, exit code 1, reason Error

Maybe there's a chicken/egg with one of these files?

@wking
Copy link
Member

wking commented Dec 8, 2018

/retest

Just in case we get lucky...

@crawford
Copy link
Contributor

crawford commented Dec 9, 2018

/retest

@wking
Copy link
Member

wking commented Dec 9, 2018

So one potential issue with being able to unilaterally merge this would be that, as described in openshift/cluster-dns-operator#63, the DNS operator is currently just appending to /etc/hosts. It will need to start managing the file. Does the content we're removing here differ from what RHCOS ships?

@abhinavdahiya
Copy link
Contributor Author

/retest

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2018
@wking
Copy link
Member

wking commented Dec 9, 2018

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2018
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2018
@abhinavdahiya
Copy link
Contributor Author

openshift/cluster-storage-operator#5

Need this ^^

@wking
Copy link
Member

wking commented Dec 10, 2018

/override ci/prow/e2e-aws

@crawford crawford closed this Dec 10, 2018
@crawford crawford reopened this Dec 10, 2018
@crawford
Copy link
Contributor

Fat-fingered it.

Should we remove the debug commit?

@crawford
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2018
@crawford
Copy link
Contributor

/lgtm
/override ci/prow/e2e-aws

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, crawford, wking

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [abhinavdahiya,crawford,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@wking
Copy link
Member

wking commented Dec 10, 2018

e2e-aws:

level=fatal msg="Error executing openshift-install: waiting for bootstrap-complete: timed out waiting for the condition"

@wking
Copy link
Member

wking commented Dec 10, 2018

/retest

@smarterclayton
Copy link
Contributor

Why is that oc error being printed?

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2018
@openshift-ci-robot
Copy link
Contributor

New changes are detected. LGTM label has been removed.

@abhinavdahiya
Copy link
Contributor Author

abhinavdahiya commented Dec 10, 2018

force pushed as previously i have seen the release image being reused in same namespace. so that i can get the changes from openshift/cluster-storage-operator#5

@abhinavdahiya abhinavdahiya added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2018
@smarterclayton
Copy link
Contributor

Link?

@smarterclayton
Copy link
Contributor

Ah, you aren’t getting a new release image when other tags change (outside of this project). Might be time to change that.

@abhinavdahiya
Copy link
Contributor Author

abhinavdahiya commented Dec 10, 2018

Ah, you aren’t getting a new release image when other tags change (outside of this project). Might be time to change that.

Yeah, in one of my PRs in this repo i vaguely remember something like that happening.. i don't remember which 😇

@openshift-merge-robot openshift-merge-robot merged commit 1b2309b into openshift:master Dec 10, 2018
@abhinavdahiya abhinavdahiya deleted the drop_registry_files branch December 10, 2018 05:25
osherdp pushed a commit to osherdp/machine-config-operator that referenced this pull request Apr 13, 2021
enable sample imagestreams and templates on Z
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. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants