CentOS PaaS SIG meeting (2018-06-20)

2018-06-19 Thread Ricardo Martinelli de Oliveira
Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Tomorrow Wedensday, 20 June 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/June/centos-devel.2018-06-13-17.01.log.html

-- 
Ricardo Martinelli de Oliveira
Senior Software Engineer
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev


Re: Custom SCC assigned to wrong pods

2018-06-19 Thread Vyacheslav Semushin
2018-06-19 10:31 GMT+02:00 Daniel Comnea :

>
>
> On Mon, Jun 18, 2018 at 11:19 PM, Jordan Liggitt 
> wrote:
>
>> Redeploying the application creates new pods.
>>
>> Since you removed the part of your custom scc that allowed it to apply to
>> your pods, those new pods were once again subject to the restricted policy.
>>
> [DC]: that was not removed, it was added in step 2) and never removed
> however during step 4) (open shift upgrade) something happened which made
> the new pods subject to default restricted policy.
>

If "pods started to crash", it means that they were re-created (or new ones
were added).

Could you show us a pod definition (oc get pod  -o yaml?


-- 
Slava Semushin | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev