Re: OpenShift Origin 3.7 Template Broker seems super flaky

> The TemplateInstance object should have an ownerReference to a BrokerTemplateInstance and that reference not being handled properly is the bug. If you remove that ownerRef from the TemplateInstance, you should be safe from undesired of the TemplateInstance (and the cascading delete of

Re: OpenShift Origin 3.7 Template Broker seems super flaky

On Sun, Jan 7, 2018 at 9:35 PM, Joel Pearson wrote: > Ahh, I looked into all the objects that were getting deleted and they all > have an ownerReference, eg: > > "ownerReferences": [ > { > "apiVersion":

Re: OpenShift Origin 3.7 Template Broker seems super flaky

Ahh, I looked into all the objects that were getting deleted and they all have an ownerReference, eg: "ownerReferences": [ { "apiVersion": "template.openshift.io/v1", "kind": "TemplateInstance", "name":

Re: OpenShift Origin 3.7 Template Broker seems super flaky

Garbage collection in particular could be related to https://bugzilla.redhat.com/show_bug.cgi?id=1525699 (fixed in https://github.com/openshift/origin/pull/17818 but not included in a point release yet) On Jan 7, 2018, at 8:17 PM, Joel Pearson wrote: Hi, Has

OpenShift Origin 3.7 Template Broker seems super flaky

Hi, Has anyone else noticed that the new OpenShift Origin 3.7 Template Broker seems super flaky? For example, if I deploy a Jenkins (Persistent or Ephemeral), and then I modify the route, by adding an annotation for example: kubernetes.io/tls-acme: 'true' I have

Re: OpenShift 3.6 on AWS creating EBS volumes in wrong region

Is the volume at least attached to the node where you were expecting? Can you post following: 1. oc get pvc -o json 2. oc get pv -o json 3. oc get pod -o json 4. oc describe pod 6. output of lsblk and /proc/self/mountinfo on node where volume was supposed to get attached and mounted. 7. Both

Re: OpenShift 3.6 on AWS creating EBS volumes in wrong region

sounds like the SELinux error is a red herring. found a red hat bug report showing this isn't an issue. This is all I'm seeing in the node's system log: Jan 7 19:50:08 ip-10-0-4-69 origin-node: I0107 19:50:08.3819381750 kubelet.go:1854] SyncLoop (ADD, "api"):

Re: OpenShift 3.6 on AWS creating EBS volumes in wrong region

The only errors I can find are in dmesg on the node thats running the pod: [ 1208.768340] XFS (dm-6): Mounting V5 Filesystem [ 1208.907628] XFS (dm-6): Ending clean mount [ 1208.937388] XFS (dm-6): Unmounting Filesystem [ 1209.016985] XFS (dm-6): Mounting V5 Filesystem [ 1209.148183] XFS (dm-6):