Re: Unable to mount GCE Persistent Disks

2017-03-14 Thread Mateus Caruccio 
Thanks Clayton, Andrew and Erik.

It was exactly the hostname. It's being defined by ansible into
node-config.yaml instead (short) nodename.


--
Mateus Caruccio / Master of Puppets
GetupCloud.com
We make the infrastructure invisible

2017-03-14 12:36 GMT-03:00 Clayton Coleman :

> Resending to whole list, sorry Erik.
>
> On Mon, Mar 13, 2017 at 6:49 PM, Clayton Coleman 
> wrote:
>
>> I think your node names in 1.4.1 need to match the GCE instance name, and
>> not be fully qualified domain names.  I hit this in origin-gce and we don't
>> have a fix for this until Kube 1.6
>>
>> On Mar 13, 2017, at 6:23 PM, Mateus Caruccio <
>> mateus.caruc...@getupcloud.com> wrote:
>>
>> Hi there. I'm trying to setup GCE persistent disk for my PVCs but kep
>> getting this error:
>>
>> Mar 13 22:18:22 n-0 origin-node[18945]: E0313 22:18:22.849255   18945
>> attacher.go:90] Error attaching PD "disk1" to node
>> "n-0.c.endless-duality-161113.internal": googleapi: Error 400: Invalid
>> value 'n-0.c.endless-duality-161113.internal'. Values must match the
>> following regular expression: '[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?',
>> invalidParameter
>> Mar 13 22:18:22 n-0 origin-node[18945]: E0313 22:18:22.849330   18945
>> nestedpendingoperations.go:253] Operation for "\"
>> kubernetes.io/gce-pd/disk1\ ""
>> failed. No retries permitted until 2017-03-13 22:20:22.849310037 + UTC
>> (durationBeforeRetry 2m0s). Error: Failed to attach volume "pv-disk1" on
>> node "n-0.c.endless-duality-161113.internal" with: googleapi: Error 400:
>> Invalid value 'n-0.c.endless-duality-161113.internal'. Values must match
>> the following regular expression: '[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?',
>> invalidParameter
>>
>> # openshift version
>> openshift v1.4.1
>> kubernetes v1.4.0+776c994
>> etcd 3.1.0-rc.0
>>
>> # oc export pv/pv-disk1
>> apiVersion: v1
>> kind: PersistentVolume
>> metadata:
>>   annotations:
>> pv.kubernetes.io/bound-by-controller: "yes"
>>   creationTimestamp: null
>>   labels:
>> failure-domain.beta.kubernetes.io/region: us-east1
>> failure-domain.beta.kubernetes.io/zone: us-east1-b
>>   name: pv-disk1
>> spec:
>>   accessModes:
>>   - ReadWriteOnce
>>   capacity:
>> storage: 10Gi
>>   claimRef:
>> apiVersion: v1
>> kind: PersistentVolumeClaim
>> name: pvc-disk1
>> namespace: mateus
>> resourceVersion: "6166"
>> uid: a60391d7-083a-11e7-805a-42010a03
>>   gcePersistentDisk:
>> fsType: ext4
>> pdName: disk1
>>   persistentVolumeReclaimPolicy: Retain
>> status: {}
>>
>>
>> # oc get pvc -n mateus
>> NAME  STATUSVOLUME   CAPACITY   ACCESSMODES   AGE
>> pvc-01Bound pv-disk-01   10Gi   RWO   41m
>>
>>
>> Is that something wrong with GCE API client? How can I increase node log
>> level?
>>
>> Thanks!
>>
>> --
>> Mateus Caruccio / Master of Puppets
>> GetupCloud.com
>> We make the infrastructure invisible
>>
>> ___
>> dev mailing list
>> dev@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>>
>
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Re: Unable to mount GCE Persistent Disks

2017-03-14 Thread Clayton Coleman 
Resending to whole list, sorry Erik.

On Mon, Mar 13, 2017 at 6:49 PM, Clayton Coleman 
wrote:

> I think your node names in 1.4.1 need to match the GCE instance name, and
> not be fully qualified domain names.  I hit this in origin-gce and we don't
> have a fix for this until Kube 1.6
>
> On Mar 13, 2017, at 6:23 PM, Mateus Caruccio  com> wrote:
>
> Hi there. I'm trying to setup GCE persistent disk for my PVCs but kep
> getting this error:
>
> Mar 13 22:18:22 n-0 origin-node[18945]: E0313 22:18:22.849255   18945
> attacher.go:90] Error attaching PD "disk1" to node
> "n-0.c.endless-duality-161113.internal": googleapi: Error 400: Invalid
> value 'n-0.c.endless-duality-161113.internal'. Values must match the
> following regular expression: '[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?',
> invalidParameter
> Mar 13 22:18:22 n-0 origin-node[18945]: E0313 22:18:22.849330   18945
> nestedpendingoperations.go:253] Operation for "\"
> kubernetes.io/gce-pd/disk1\ ""
> failed. No retries permitted until 2017-03-13 22:20:22.849310037 + UTC
> (durationBeforeRetry 2m0s). Error: Failed to attach volume "pv-disk1" on
> node "n-0.c.endless-duality-161113.internal" with: googleapi: Error 400:
> Invalid value 'n-0.c.endless-duality-161113.internal'. Values must match
> the following regular expression: '[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?',
> invalidParameter
>
> # openshift version
> openshift v1.4.1
> kubernetes v1.4.0+776c994
> etcd 3.1.0-rc.0
>
> # oc export pv/pv-disk1
> apiVersion: v1
> kind: PersistentVolume
> metadata:
>   annotations:
> pv.kubernetes.io/bound-by-controller: "yes"
>   creationTimestamp: null
>   labels:
> failure-domain.beta.kubernetes.io/region: us-east1
> failure-domain.beta.kubernetes.io/zone: us-east1-b
>   name: pv-disk1
> spec:
>   accessModes:
>   - ReadWriteOnce
>   capacity:
> storage: 10Gi
>   claimRef:
> apiVersion: v1
> kind: PersistentVolumeClaim
> name: pvc-disk1
> namespace: mateus
> resourceVersion: "6166"
> uid: a60391d7-083a-11e7-805a-42010a03
>   gcePersistentDisk:
> fsType: ext4
> pdName: disk1
>   persistentVolumeReclaimPolicy: Retain
> status: {}
>
>
> # oc get pvc -n mateus
> NAME  STATUSVOLUME   CAPACITY   ACCESSMODES   AGE
> pvc-01Bound pv-disk-01   10Gi   RWO   41m
>
>
> Is that something wrong with GCE API client? How can I increase node log
> level?
>
> Thanks!
>
> --
> Mateus Caruccio / Master of Puppets
> GetupCloud.com
> We make the infrastructure invisible
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev