[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-21 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42200  
 
 
  No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
Change By: 
 Jesse Haka  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-21 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka commented on  JENKINS-42200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
 Hi Thanks, now it works. I enabled also "Enable proxy compatibility" which was needed in order to work properly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-20 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42200  
 
 
  No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
Change By: 
 Jesse Haka  
 

  
 
 
 
 

 
  I am getting following when doing POST / PUT requests like in jenkins admin after installation. One use-case install some plugin:HTTP ERROR 403Problem accessing /pluginManager/install. Reason:No valid crumb was included in the requestPowered by Jetty://I am running this in top of kubernetes. This same happens also with blueocean version latestkube files:{code:yaml}apiVersion: extensions/v1beta1kind: Deploymentmetadata:  name: jenkins  namespace: blueoceanspec:  replicas: 1  template:metadata:  labels:run: jenkinsspec:  containers:  - image: jenkinsci/blueocean:1.0.0-b22imagePullPolicy: Alwaysname: jenkinsresources:  limits:cpu: 2memory: 2Gi  requests:cpu: 1memory: 1GivolumeMounts:- mountPath: /var/jenkins_home  name: jenkins-blueoceanports:- containerPort: 8080  protocol: TCP- containerPort: 5  protocol: TCP  dnsPolicy: ClusterFirst  nodeSelector:failure-domain.beta.kubernetes.io/zone: zone-1  restartPolicy: Always  securityContext: {}  volumes:  - name: jenkins-blueoceanpersistentVolumeClaim:  claimName: jenkins-blueocean{code}{code:yaml}---apiVersion: v1kind: Servicemetadata:  name: jenkins  namespace: blueoceanspec:  selector:run: jenkins  ports:  - name: httpport: 80protocol: TCPtargetPort: 8080  - name: syncport: 5protocol: TCPtargetPort: 5  type: LoadBalancer{code}{code:yaml} ---apiVersion: v1 kind:  Servicemetadata:  name: jenkins  namespace: blueoceanspec:  selector:run: jenkins  ports:  - name: httpport: 80protocol: TCPtargetPort: 8080  - name: syncport: 5protocol: TCPtargetPort: 5  type: LoadBalancer[root@tarmo-master-1-1 uudet]# cat pv.yamlkind:  PersistentVolumeapiVersion: v1metadata:  name: jenkins-blueocean  labels:type: localspec:  capacity:storage: 30Gi  accessModes:- ReadWriteOnce  persistentVolumeReclaimPolicy: Retain  cinder:volumeID: "4exxx827"fsType: "ext4"{code}{code:yaml}kind: PersistentVolumeClaimapiVersion: v1metadata:  name: jenkins-blueocean  namespace: blueoceanspec:  accessModes:- ReadWriteOnce  resources:requests:  storage: 30Gi{code}  
 

  
 
 
 
 

 
 
 

[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-20 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42200  
 
 
  No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
Change By: 
 Jesse Haka  
 
 
Attachment: 
 Screen Shot 2017-02-20 at 16.36.02.png  
 

  
 
 
 
 

 
 I am getting following when doing POST / PUT requests like in jenkins admin after installation. One use-case install some plugin:HTTP ERROR 403Problem accessing /pluginManager/install. Reason:No valid crumb was included in the requestPowered by Jetty://I am running this in top of kubernetes. This same happens also with blueocean version latestkube files:{code:yaml}apiVersion: extensions/v1beta1kind: Deploymentmetadata:  name: jenkins  namespace: blueoceanspec:  replicas: 1  template:metadata:  labels:run: jenkinsspec:  containers:  - image: jenkinsci/blueocean:1.0.0-b22imagePullPolicy: Alwaysname: jenkinsresources:  limits:cpu: 2memory: 2Gi  requests:cpu: 1memory: 1GivolumeMounts:- mountPath: /var/jenkins_home  name: jenkins-blueoceanports:- containerPort: 8080  protocol: TCP- containerPort: 5  protocol: TCP  dnsPolicy: ClusterFirst  nodeSelector:failure-domain.beta.kubernetes.io/zone: zone-1  restartPolicy: Always  securityContext: {}  volumes:  - name: jenkins-blueoceanpersistentVolumeClaim:  claimName: jenkins-blueocean{code}{code:yaml}---apiVersion: v1kind: Servicemetadata:  name: jenkins  namespace: blueoceanspec:  selector:run: jenkins  ports:  - name: httpport: 80protocol: TCPtargetPort: 8080  - name: syncport: 5protocol: TCPtargetPort: 5  type: LoadBalancer{code}{code:yaml}kind: PersistentVolumeapiVersion: v1metadata:  name: jenkins-blueocean  labels:type: localspec:  capacity:storage: 30Gi  accessModes:- ReadWriteOnce  persistentVolumeReclaimPolicy: Retain  cinder:volumeID: "4exxx827"fsType: "ext4"{code}{code:yaml}kind: PersistentVolumeClaimapiVersion: v1metadata:  name: jenkins-blueocean  namespace: blueoceanspec:  accessModes:- ReadWriteOnce  resources:requests:  storage: 30Gi{code}Logfiles:WARNING: Found invalid crumb  eaed7b7a22ba625a708d7e607d7becbd  4d1aebe90b7e7023e44aabf9b077346f .  Will check remaining parameters for a valid one...Feb 20, 2017 2: 13 34 : 20 52  PM hudson.security.csrf.CrumbFilter doFilterWARNING: No valid crumb was included in request for /pluginManager/install. Returning 403.  
 

  
 
 
 
   

[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-20 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42200  
 
 
  No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
Change By: 
 Jesse Haka  
 

  
 
 
 
 

 
 I am getting following when doing POST / PUT requests like in jenkins admin after installation. One use-case install some plugin:HTTP ERROR 403Problem accessing /pluginManager/install. Reason:No valid crumb was included in the requestPowered by Jetty://I am running this in top of kubernetes. This same happens also with blueocean version latestkube files:{code:yaml}apiVersion: extensions/v1beta1kind: Deploymentmetadata:  name: jenkins  namespace: blueoceanspec:  replicas: 1  template:metadata:  labels:run: jenkinsspec:  containers:  - image: jenkinsci/blueocean:1.0.0-b22imagePullPolicy: Alwaysname: jenkinsresources:  limits:cpu: 2memory: 2Gi  requests:cpu: 1memory: 1GivolumeMounts:- mountPath: /var/jenkins_home  name: jenkins-blueoceanports:- containerPort: 8080  protocol: TCP- containerPort: 5  protocol: TCP  dnsPolicy: ClusterFirst  nodeSelector:failure-domain.beta.kubernetes.io/zone: zone-1  restartPolicy: Always  securityContext: {}  volumes:  - name: jenkins-blueoceanpersistentVolumeClaim:  claimName: jenkins-blueocean{code}{code:yaml}---apiVersion: v1kind: Servicemetadata:  name: jenkins  namespace: blueoceanspec:  selector:run: jenkins  ports:  - name: httpport: 80protocol: TCPtargetPort: 8080  - name: syncport: 5protocol: TCPtargetPort: 5  type: LoadBalancer{code}{code:yaml}kind: PersistentVolumeapiVersion: v1metadata:  name: jenkins-blueocean  labels:type: localspec:  capacity:storage: 30Gi  accessModes:- ReadWriteOnce  persistentVolumeReclaimPolicy: Retain  cinder:volumeID: "4exxx827"fsType: "ext4"{code}{code:yaml}kind: PersistentVolumeClaimapiVersion: v1metadata:  name: jenkins-blueocean  namespace: blueoceanspec:  accessModes:- ReadWriteOnce  resources:requests:  storage: 30Gi{code} Logfiles:WARNING: Found invalid crumb eaed7b7a22ba625a708d7e607d7becbd.  Will check remaining parameters for a valid one...Feb 20, 2017 2:13:20 PM hudson.security.csrf.CrumbFilter doFilterWARNING: No valid crumb was included in request for /pluginManager/install. Returning 403.  
 

  
 
 
 
 

 
 
 

 

[JIRA] (JENKINS-42200) No valid crumb was included in the request in kubernetes

2017-02-20 Thread jesse.h...@elisa.fi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Haka created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42200  
 
 
  No valid crumb was included in the request in kubernetes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Feb/20 2:31 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Haka  
 

  
 
 
 
 

 
 I am getting following when doing POST / PUT requests like in jenkins admin after installation. One use-case install some plugin: HTTP ERROR 403 Problem accessing /pluginManager/install. Reason:  No valid crumb was included in the request Powered by Jetty:// I am running this in top of kubernetes. This same happens also with blueocean version latest kube files: 

 

Unable to find source-code formatter for language: yaml. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: jenkins
  namespace: blueocean
spec:
  replicas: 1
  template:
metadata:
  labels:
run: jenkins
spec:
  containers:
  - image: jenkinsci/blueocean:1.0.0-b22
imagePullPolicy: Always
name: jenkins
resources:
  limits:
cpu: 2
memory: 2Gi
  requests:
cpu: 1
memory: 1Gi
volumeMounts:
- mountPath: /var/jenkins_home
  name: jenkins-blueocean
ports:
- containerPort: 8080
  protocol: TCP
- containerPort: 5
  protocol: TCP
  dnsPolicy: ClusterFirst
  nodeSelector:
failure-domain.beta.kubernetes.io/zone: zone-1
  restartPolicy: Always
  securityContext: {}
  volumes:
  -