I don't think it is a bug in Go. ..data is a symlink, not a directory, os
IsDir() returning false is not unexpected. Unfortunately, there isn't a
way to determine if the symlink points at a file or a directory without
following the link.
However, if you modify your code to skip entries in the di
We finally found the issue with these secrets:
https://github.com/openshift/origin/issues/11164#issuecomment-269912867
The secrets are mounted in a different way in os 1.3, and our go code was
not reading the files anymore.
[ta-pla-imac:~/dev/go/src/test]$ ls -ail secrets
total 16
34464066 drwxr-x
There you go, thanks!
https://github.com/openshift/origin/issues/11164
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Please open an issue with the related details - we don't have any other
reports of this yet, but I suspect it's related to filesystem aspects and
we'll need to recreate it.
On Thu, Sep 29, 2016 at 9:51 AM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
> Any news on this?
> T
Any news on this?
This is really a blocking issue to upgrade to 1.3.0 for us.
Thanks
Philippe
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
It's definitely an issue related to 1.3.0. I have downgraded the cluster to
1.2.1, and it works again :(
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Is this what you're looking for?
secret.go:152] Setting up volume airbrake-secrets for pod
41cdd02f-84ea-11e6-be87-005056b17dcc at
/var/lib/origin/openshift.local.volumes/pods/41cdd02f-84ea-11e6-be87-005056b17dcc/volumes/
kubernetes.io~secret/airbrake-secrets
nsenter_mount.go:183] findmnt comman
There was a bug at one point where the Kubelet was looking inside the
container for a command instead of outside the container. If you turn on
"--loglevel=5" on your node you should be able to see where it calls the
mounter to launch the secret (search for the secret name in your logs).
On Tue, S
On Tue, Sep 27, 2016 at 3:44 PM, Clayton Coleman
wrote:
> Which version of Docker are you running? Paul, do those propagation
> settings look correct?
We're running centos atomic (latest 7.20160920), so docker 1.10.3
It really seems to be related to the scratch images, the others seem to be
wo
Which version of Docker are you running? Paul, do those propagation
settings look correct?
On Tue, Sep 27, 2016 at 3:40 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
> Hi,
>
> We're testing OS 1.3.0 on our test cluster, and have something weird
> happening.
> The secret
Hi,
We're testing OS 1.3.0 on our test cluster, and have something weird
happening.
The secrets are mounted, but apparently not readable anymore in _some_ pods:
This is on openshift 1.2.1:
{
"Source":
"/var/lib/origin/openshift.local.volumes/pods/3f7a5adc-84b1-11e6-8101-005056b12d45/volumes/
11 matches
Mail list logo
