And what about error with teardown network? https://bugzilla.redhat.com/show_bug.cgi?id=1322077
It seems that this particular error is there for 1.1.6 also - or is this caused also because of SCC? David Strejc t: +420734270131 e: [email protected] On Mon, Apr 11, 2016 at 2:58 PM, David Strejc <[email protected]> wrote: > Where exactly should this be done globally? > > > David Strejc > t: +420734270131 > e: [email protected] > > On Mon, Apr 11, 2016 at 2:50 PM, Clayton Coleman <[email protected]> > wrote: > >> The default security context constraint was tightened to prevent >> unauthorized users from directly using any volume in the cluster. You can >> add glusterfs to the "restricted" SCC's allowedFSType field (or create your >> own SCC) >> >> On Apr 11, 2016, at 3:34 AM, David Strejc <[email protected]> wrote: >> >> Dear all, >> >> we got following errors appearing since 1.1.6: >> >> >> Error syncing pod, skipping: failed to "TeardownNetwork" for >> "redmine-app-1-deploy_masi" with TeardownNetworkError: "Failed to teardown >> network for pod \"ca572238-ffb2-11e5-9cfc-386077264a54\" using network >> plugins \"redhat/openshift-ovs-subnet\": exit status 1" >> >> Error creating: pods "redmine-app-1-" is forbidden: unable to validate >> against any security context constraint: >> [spec.containers[0].securityContext.volumes[0]: Invalid value: "glusterfs": >> glusterfs volumes are not allowed to be used] >> >> Cannot update deployment masi/redmine-app-2 status to Pending: >> replicationcontrollers "redmine-app-2" cannot be updated: the object has >> been modified; please apply your changes to the latest version and try again >> >> >> David Strejc >> t: +420734270131 >> e: [email protected] >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
