Re: oc cluster up - dns issue?

[Lionel Orellana]

Further info

$ oc get endpoints --namespace=default --selector=router

NAME ENDPOINTS AGE
router  1h

Router has no endpoints?



On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana  wrote:

> Forgot to mention
>
> Openshift v1.3.0-alpha.2
> Docker 1.11.2
> Ubuntu 15.10
>
> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
> wrote:
>
>> Hi
>>
>> I'm trying the new cluster up command. It seems to run Ok and I can
>> deploy an app (Jenkins, from the template) that also seems to start fine.
>> But I can't hit it. When I go to the url shown in the route chrome says
>> "site can't be reached".
>>
>> If I login to the host I can curl the aplication on the internal ip/port.
>>
>> Seems like a dns issue but I thought xip.io was supposed to take care of
>> that.
>>
>> Do I need to do anything to make my service accessible from outside?
>>
>> Thanks
>>
>>
>> Lionel.
>>
>>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Disable self-provisioning

[Robson Ramos Barreto]

Hello Jordan

It  worked

Thank you


2016-07-26 16:48 GMT-03:00 Jordan Liggitt :

> To delete that cluster role binding:
> oc delete clusterrolebinding self-provisioners
>
>
> To just remove that role from the authenticated groups of users:
> oadm policy remove-cluster-role-from-group self-provisioner
> system:authenticated system:authenticated:oauth
>
>
>
>
>
> On Tue, Jul 26, 2016 at 3:43 PM, Robson Ramos Barreto <
> robson.rbarr...@gmail.com> wrote:
>
>> Hello Guys,
>>
>> How can I disable self-provisioning role to any users so that they can't
>> create new projects on the OpenShift Enterprise ?
>>
>> Taking a look at documentation [1] it says to delete self-provisioners
>> cluster role binding but I don't understand how I can do that
>>
>> [1]
>> https://docs.openshift.com/enterprise/3.2/admin_guide/managing_projects.html
>>
>> Thank you
>>
>> Regards
>>
>> Robson
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Self-signed certificate and oadm diagnostics

[Andre Esser]

Hi,

I'm using a self-signed certificate for the public host names of the 
OpenShift API and web console. Subsequently 'oadm diagnostics' errors with:


ERROR: [DCli0006 from diagnostic 
ConfigContexts@openshift/origin/pkg/diagnostics/client/config_contexts.go:285]
   For client config context 
'default/osdev-gede-voidbridge-biz:8443/system:admin':

   The server URL is 'https://osdev.gede.voidbridge.biz:8443'
   The user authentication is 
'system:admin/osdev-lb-100-gede-voidbridge:8443'

   The current project is 'default'
   (*url.Error) Get https://osdev.gede.voidbridge.biz:8443/api: 
x509: certificate signed by unknown authority



Where can I specify my CA cert for this test to succeed?


Thanks,

Andre

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Docker layering for jenkins image issue

[Akshaya Khare]

Hi

While going through the documentation for using *jenkins* image, I found
that we can use the updated image of jenkins by:

   -

   Use Docker layering.
   -

   Use the image as a Source-To-Image builder

Now i found docker layering to be ideal in my case since I have created a
new project and made many configurations to make it work.

I ran the below command for getting the new image

*# docker commit -m "my message"  *

I pushed it to my local registry and used it to create a new application in
openshift.

It did get deployed, but the jenkins image doesn't contain any of my
changes...

comparing the history of both the original image and the modified image, it
looks like it did add a new layer:



*IMAGE  CREATED CREATED
BY  SIZE
COMMENTe99517b97a3e21 hours ago
/usr/libexec/s2i/run 1.886
MBjenkins 3rd attemptc014669e27a011 days ago
/bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *

So finally coming to my question, am I missing something while creating a
new docker layer for my jenkins image?

Or should i just use Source to image builder for my changes?


Thanks & Regards,

AK
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Docker layering for jenkins image issue

[Akshaya Khare]

Hi Ben,

Using the below commands I pushed it to my local docker registry:



*# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker push
localhost:5000/jenkins-bmi3:latest*Then I created a new app using the below
command, and a pod got deployed shortly after the app was created



*# oc new-app -e JENKINS_PASSWORD= localhost:5000/jenkins-bmi2*
Thats all I did...
As per your advice, I'll try using s2i for extending an image, and thanks
for replying so quickly...

Regards,
AK

On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees  wrote:

>
>
> On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare 
> wrote:
>
>> Hi
>>
>> While going through the documentation for using *jenkins* image, I found
>> that we can use the updated image of jenkins by:
>>
>>-
>>
>>Use Docker layering.
>>-
>>
>>Use the image as a Source-To-Image builder
>>
>> Now i found docker layering to be ideal in my case since I have created a
>> new project and made many configurations to make it work.
>>
>> I ran the below command for getting the new image
>>
>> *# docker commit -m "my message"  *
>>
>
> ​first of all i'd strongly discourage you from creating images in this way
> since you don't have a recreatable pattern.  you should definitely create a
> dockerfile if you're going to extend an image (or use s2i).
> ​
>
>
>> I pushed it to my local registry and used it to create a new application
>> in openshift.
>>
>
> ​what did you tag it as an how did you create the new application?
> ​
>
>
>> It did get deployed, but the jenkins image doesn't contain any of my
>> changes...
>>
>
> ​how did you deploy the new image?​
>
>
>> comparing the history of both the original image and the modified image,
>> it looks like it did add a new layer:
>>
>>
>>
>> *IMAGE  CREATED CREATED
>> BY  SIZE
>> COMMENTe99517b97a3e21 hours ago
>> /usr/libexec/s2i/run 1.886
>> MBjenkins 3rd attemptc014669e27a011 days ago
>> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>>
>> So finally coming to my question, am I missing something while creating a
>> new docker layer for my jenkins image?
>>
>
> ​i'm guessing you just didn't actually deploy your new image, but we'll
> need some more details about your steps to know for sure.
> ​
>
>
>> Or should i just use Source to image builder for my changes?
>>
>>
>> Thanks & Regards,
>>
>> AK
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
> --
> Ben Parees | OpenShift
>
>


-- 
*Thanks & Regards,*
*Akshaya Khare*
*312-785-3508*
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Docker layering for jenkins image issue

[Ben Parees]

On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare 
wrote:

> sorry, that was an old command, I ran this command
>
> *oc new-app -e JENKINS_PASSWORD=password localhost:5000/jenkins-bmi3*
>

​ok, i'd certainly expect that to result in a pod running your new image.
Can you inspect the pod definition to confirm what image the container is
running?  And can you oc rsh into the running container and poke around to
see if your changes are present?

have you confirmed if you "docker run localhost:5000/jenkins-bmi3 /bin/sh"
that it contains your changes?

Also i'm assuming you only have a single node and it's the same machine as
"localhost", otherwise it's not clear how the image is going to get pulled
to the node that's running the pod.
​


>
>
> On Wed, Jul 27, 2016 at 1:20 PM, Ben Parees  wrote:
>
>>
>>
>> On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare 
>> wrote:
>>
>>> Hi Ben,
>>>
>>> Using the below commands I pushed it to my local docker registry:
>>>
>>>
>>>
>>> *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker
>>> push  localhost:5000/jenkins-bmi3:latest*Then I created a new app using
>>> the below command, and a pod got deployed shortly after the app was created
>>>
>>> *# oc new-app -e JENKINS_PASSWORD=
>>> localhost:5000/jenkins-bmi2*
>>>
>>
>> ​you pushed it to bmi3 and deployed bmi-2?
>> ​
>>
>>
>>>
>>>
>>> Thats all I did...
>>> As per your advice, I'll try using s2i for extending an image, and
>>> thanks for replying so quickly...
>>>
>>> Regards,
>>> AK
>>>
>>> On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees  wrote:
>>>


 On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare  wrote:

> Hi
>
> While going through the documentation for using *jenkins* image, I
> found that we can use the updated image of jenkins by:
>
>-
>
>Use Docker layering.
>-
>
>Use the image as a Source-To-Image builder
>
> Now i found docker layering to be ideal in my case since I have
> created a new project and made many configurations to make it work.
>
> I ran the below command for getting the new image
>
> *# docker commit -m "my message"  *
>

 ​first of all i'd strongly discourage you from creating images in this
 way since you don't have a recreatable pattern.  you should definitely
 create a dockerfile if you're going to extend an image (or use s2i).
 ​


> I pushed it to my local registry and used it to create a new
> application in openshift.
>

 ​what did you tag it as an how did you create the new application?
 ​


> It did get deployed, but the jenkins image doesn't contain any of my
> changes...
>

 ​how did you deploy the new image?​


> comparing the history of both the original image and the modified
> image, it looks like it did add a new layer:
>
>
>
> *IMAGE  CREATED CREATED
> BY  SIZE
> COMMENTe99517b97a3e21 hours ago
> /usr/libexec/s2i/run 1.886
> MBjenkins 3rd attemptc014669e27a011 days ago
> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>
> So finally coming to my question, am I missing something while
> creating a new docker layer for my jenkins image?
>

 ​i'm guessing you just didn't actually deploy your new image, but we'll
 need some more details about your steps to know for sure.
 ​


> Or should i just use Source to image builder for my changes?
>
>
> Thanks & Regards,
>
> AK
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


 --
 Ben Parees | OpenShift


>>>
>>>
>>> --
>>> *Thanks & Regards,*
>>> *Akshaya Khare*
>>> *312-785-3508 <312-785-3508>*
>>>
>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>
>
> --
> *Thanks & Regards,*
> *Akshaya Khare*
> *312-785-3508 <312-785-3508>*
>



-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Docker layering for jenkins image issue

[Akshaya Khare]

ok, the changes are not present in the running container.
And yes the pod is working on the latest image, which means my image is
somehow not updated...

So I guess I should create a new image using s2i and then try again?

On Wed, Jul 27, 2016 at 1:26 PM, Ben Parees  wrote:

>
>
> On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare 
> wrote:
>
>> sorry, that was an old command, I ran this command
>>
>> *oc new-app -e JENKINS_PASSWORD=password localhost:5000/jenkins-bmi3*
>>
>
> ​ok, i'd certainly expect that to result in a pod running your new image.
> Can you inspect the pod definition to confirm what image the container is
> running?  And can you oc rsh into the running container and poke around to
> see if your changes are present?
>
> have you confirmed if you "docker run localhost:5000/jenkins-bmi3 /bin/sh"
> that it contains your changes?
>
> Also i'm assuming you only have a single node and it's the same machine as
> "localhost", otherwise it's not clear how the image is going to get pulled
> to the node that's running the pod.
> ​
>
>
>>
>>
>> On Wed, Jul 27, 2016 at 1:20 PM, Ben Parees  wrote:
>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare 
>>> wrote:
>>>
 Hi Ben,

 Using the below commands I pushed it to my local docker registry:



 *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker
 push  localhost:5000/jenkins-bmi3:latest*Then I created a new app
 using the below command, and a pod got deployed shortly after the app was
 created

 *# oc new-app -e JENKINS_PASSWORD=
 localhost:5000/jenkins-bmi2*

>>>
>>> ​you pushed it to bmi3 and deployed bmi-2?
>>> ​
>>>
>>>


 Thats all I did...
 As per your advice, I'll try using s2i for extending an image, and
 thanks for replying so quickly...

 Regards,
 AK

 On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees 
 wrote:

>
>
> On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare <
> khare...@husky.neu.edu> wrote:
>
>> Hi
>>
>> While going through the documentation for using *jenkins* image, I
>> found that we can use the updated image of jenkins by:
>>
>>-
>>
>>Use Docker layering.
>>-
>>
>>Use the image as a Source-To-Image builder
>>
>> Now i found docker layering to be ideal in my case since I have
>> created a new project and made many configurations to make it work.
>>
>> I ran the below command for getting the new image
>>
>> *# docker commit -m "my message"  *
>>
>
> ​first of all i'd strongly discourage you from creating images in this
> way since you don't have a recreatable pattern.  you should definitely
> create a dockerfile if you're going to extend an image (or use s2i).
> ​
>
>
>> I pushed it to my local registry and used it to create a new
>> application in openshift.
>>
>
> ​what did you tag it as an how did you create the new application?
> ​
>
>
>> It did get deployed, but the jenkins image doesn't contain any of my
>> changes...
>>
>
> ​how did you deploy the new image?​
>
>
>> comparing the history of both the original image and the modified
>> image, it looks like it did add a new layer:
>>
>>
>>
>> *IMAGE  CREATED CREATED
>> BY  SIZE
>> COMMENTe99517b97a3e21 hours ago
>> /usr/libexec/s2i/run 1.886
>> MBjenkins 3rd attemptc014669e27a011 days ago
>> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>>
>> So finally coming to my question, am I missing something while
>> creating a new docker layer for my jenkins image?
>>
>
> ​i'm guessing you just didn't actually deploy your new image, but
> we'll need some more details about your steps to know for sure.
> ​
>
>
>> Or should i just use Source to image builder for my changes?
>>
>>
>> Thanks & Regards,
>>
>> AK
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
> --
> Ben Parees | OpenShift
>
>


 --
 *Thanks & Regards,*
 *Akshaya Khare*
 *312-785-3508 <312-785-3508>*

>>>
>>>
>>>
>>> --
>>> Ben Parees | OpenShift
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,*
>> *Akshaya Khare*
>> *312-785-3508 <312-785-3508>*
>>
>
>
>
> --
> Ben Parees | OpenShift
>
>


-- 
*Thanks & Regards,*
*Akshaya Khare*
*312-785-3508*
___
users mailing list

Re: Docker layering for jenkins image issue

[Ben Parees]

On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare 
wrote:

> Hi
>
> While going through the documentation for using *jenkins* image, I found
> that we can use the updated image of jenkins by:
>
>-
>
>Use Docker layering.
>-
>
>Use the image as a Source-To-Image builder
>
> Now i found docker layering to be ideal in my case since I have created a
> new project and made many configurations to make it work.
>
> I ran the below command for getting the new image
>
> *# docker commit -m "my message"  *
>

​first of all i'd strongly discourage you from creating images in this way
since you don't have a recreatable pattern.  you should definitely create a
dockerfile if you're going to extend an image (or use s2i).
​


> I pushed it to my local registry and used it to create a new application
> in openshift.
>

​what did you tag it as an how did you create the new application?
​


> It did get deployed, but the jenkins image doesn't contain any of my
> changes...
>

​how did you deploy the new image?​


> comparing the history of both the original image and the modified image,
> it looks like it did add a new layer:
>
>
>
> *IMAGE  CREATED CREATED
> BY  SIZE
> COMMENTe99517b97a3e21 hours ago
> /usr/libexec/s2i/run 1.886
> MBjenkins 3rd attemptc014669e27a011 days ago
> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>
> So finally coming to my question, am I missing something while creating a
> new docker layer for my jenkins image?
>

​i'm guessing you just didn't actually deploy your new image, but we'll
need some more details about your steps to know for sure.
​


> Or should i just use Source to image builder for my changes?
>
>
> Thanks & Regards,
>
> AK
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Docker layering for jenkins image issue

[Ben Parees]

On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare 
wrote:

> Hi Ben,
>
> Using the below commands I pushed it to my local docker registry:
>
>
>
> *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker
> push  localhost:5000/jenkins-bmi3:latest*Then I created a new app using
> the below command, and a pod got deployed shortly after the app was created
>
> *# oc new-app -e JENKINS_PASSWORD= localhost:5000/jenkins-bmi2*
>

​you pushed it to bmi3 and deployed bmi-2?
​


>
>
> Thats all I did...
> As per your advice, I'll try using s2i for extending an image, and thanks
> for replying so quickly...
>
> Regards,
> AK
>
> On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees  wrote:
>
>>
>>
>> On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare 
>> wrote:
>>
>>> Hi
>>>
>>> While going through the documentation for using *jenkins* image, I
>>> found that we can use the updated image of jenkins by:
>>>
>>>-
>>>
>>>Use Docker layering.
>>>-
>>>
>>>Use the image as a Source-To-Image builder
>>>
>>> Now i found docker layering to be ideal in my case since I have created
>>> a new project and made many configurations to make it work.
>>>
>>> I ran the below command for getting the new image
>>>
>>> *# docker commit -m "my message"  *
>>>
>>
>> ​first of all i'd strongly discourage you from creating images in this
>> way since you don't have a recreatable pattern.  you should definitely
>> create a dockerfile if you're going to extend an image (or use s2i).
>> ​
>>
>>
>>> I pushed it to my local registry and used it to create a new application
>>> in openshift.
>>>
>>
>> ​what did you tag it as an how did you create the new application?
>> ​
>>
>>
>>> It did get deployed, but the jenkins image doesn't contain any of my
>>> changes...
>>>
>>
>> ​how did you deploy the new image?​
>>
>>
>>> comparing the history of both the original image and the modified image,
>>> it looks like it did add a new layer:
>>>
>>>
>>>
>>> *IMAGE  CREATED CREATED
>>> BY  SIZE
>>> COMMENTe99517b97a3e21 hours ago
>>> /usr/libexec/s2i/run 1.886
>>> MBjenkins 3rd attemptc014669e27a011 days ago
>>> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>>>
>>> So finally coming to my question, am I missing something while creating
>>> a new docker layer for my jenkins image?
>>>
>>
>> ​i'm guessing you just didn't actually deploy your new image, but we'll
>> need some more details about your steps to know for sure.
>> ​
>>
>>
>>> Or should i just use Source to image builder for my changes?
>>>
>>>
>>> Thanks & Regards,
>>>
>>> AK
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>
>
> --
> *Thanks & Regards,*
> *Akshaya Khare*
> *312-785-3508 <312-785-3508>*
>



-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Docker layering for jenkins image issue

[Ben Parees]

On Wed, Jul 27, 2016 at 1:36 PM, Akshaya Khare 
wrote:

> ok, the changes are not present in the running container.
> And yes the pod is working on the latest image, which means my image is
> somehow not updated...
>
> So I guess I should create a new image using s2i and then try again?
>

up to you how many variables you want to introduce, but yes you should
probably start from either a Dockerfile or a repo you can build with s2i,
so you can easily iterate on your changes as you sort this out.
​



>
> On Wed, Jul 27, 2016 at 1:26 PM, Ben Parees  wrote:
>
>>
>>
>> On Wed, Jul 27, 2016 at 1:23 PM, Akshaya Khare 
>> wrote:
>>
>>> sorry, that was an old command, I ran this command
>>>
>>> *oc new-app -e JENKINS_PASSWORD=password localhost:5000/jenkins-bmi3*
>>>
>>
>> ​ok, i'd certainly expect that to result in a pod running your new
>> image.  Can you inspect the pod definition to confirm what image the
>> container is running?  And can you oc rsh into the running container and
>> poke around to see if your changes are present?
>>
>> have you confirmed if you "docker run localhost:5000/jenkins-bmi3
>> /bin/sh" that it contains your changes?
>>
>> Also i'm assuming you only have a single node and it's the same machine
>> as "localhost", otherwise it's not clear how the image is going to get
>> pulled to the node that's running the pod.
>> ​
>>
>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 1:20 PM, Ben Parees  wrote:
>>>


 On Wed, Jul 27, 2016 at 1:19 PM, Akshaya Khare 
 wrote:

> Hi Ben,
>
> Using the below commands I pushed it to my local docker registry:
>
>
>
> *# docker tag jenkins_bmi3 localhost:5000/jenkins-bmi3:latest# docker
> push  localhost:5000/jenkins-bmi3:latest*Then I created a new app
> using the below command, and a pod got deployed shortly after the app was
> created
>
> *# oc new-app -e JENKINS_PASSWORD=
> localhost:5000/jenkins-bmi2*
>

 ​you pushed it to bmi3 and deployed bmi-2?
 ​


>
>
> Thats all I did...
> As per your advice, I'll try using s2i for extending an image, and
> thanks for replying so quickly...
>
> Regards,
> AK
>
> On Wed, Jul 27, 2016 at 12:37 PM, Ben Parees 
> wrote:
>
>>
>>
>> On Wed, Jul 27, 2016 at 11:48 AM, Akshaya Khare <
>> khare...@husky.neu.edu> wrote:
>>
>>> Hi
>>>
>>> While going through the documentation for using *jenkins* image, I
>>> found that we can use the updated image of jenkins by:
>>>
>>>-
>>>
>>>Use Docker layering.
>>>-
>>>
>>>Use the image as a Source-To-Image builder
>>>
>>> Now i found docker layering to be ideal in my case since I have
>>> created a new project and made many configurations to make it work.
>>>
>>> I ran the below command for getting the new image
>>>
>>> *# docker commit -m "my message"  *
>>>
>>
>> ​first of all i'd strongly discourage you from creating images in
>> this way since you don't have a recreatable pattern.  you should 
>> definitely
>> create a dockerfile if you're going to extend an image (or use s2i).
>> ​
>>
>>
>>> I pushed it to my local registry and used it to create a new
>>> application in openshift.
>>>
>>
>> ​what did you tag it as an how did you create the new application?
>> ​
>>
>>
>>> It did get deployed, but the jenkins image doesn't contain any of my
>>> changes...
>>>
>>
>> ​how did you deploy the new image?​
>>
>>
>>> comparing the history of both the original image and the modified
>>> image, it looks like it did add a new layer:
>>>
>>>
>>>
>>> *IMAGE  CREATED CREATED
>>> BY  SIZE
>>> COMMENTe99517b97a3e21 hours ago
>>> /usr/libexec/s2i/run 1.886
>>> MBjenkins 3rd attemptc014669e27a011 days ago
>>> /bin/sh -c #(nop) LABEL io.openshift.builder-   0 B *
>>>
>>> So finally coming to my question, am I missing something while
>>> creating a new docker layer for my jenkins image?
>>>
>>
>> ​i'm guessing you just didn't actually deploy your new image, but
>> we'll need some more details about your steps to know for sure.
>> ​
>>
>>
>>> Or should i just use Source to image builder for my changes?
>>>
>>>
>>> Thanks & Regards,
>>>
>>> AK
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>>
>> --

Re: oc cluster up - dns issue?

[Lionel Orellana]

Even running cluster up as root the router can't bind to ports 80 and 443.

On Wed, 27 Jul 2016 at 9:52 PM, Lionel Orellana  wrote:

> Don't think so.
>
> $ sudo netstat -tulpn
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreign Address State
>   PID/Program name
> tcp0  0 104.236.65.18:530.0.0.0:*
> LISTEN  1268/openshift
> tcp0  0 0.0.0.0:80530.0.0.0:*
> LISTEN  1268/openshift
> tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  776/sshd
> tcp0  0 0.0.0.0:84430.0.0.0:*
> LISTEN  1268/openshift
> tcp6   0  0 :::4001 :::*LISTEN
>  1268/openshift
> tcp6   0  0 :::2376 :::*LISTEN
>  595/docker
> tcp6   0  0 :::10250:::*LISTEN
>  1268/openshift
> tcp6   0  0 :::22   :::*LISTEN
>  776/sshd
> tcp6   0  0 :::7001 :::*LISTEN
>  1268/openshift
> udp0  0 0.0.0.0:80530.0.0.0:*
>   1268/openshift
> udp0  0 104.236.65.18:530.0.0.0:*
>   1268/openshift
>
> But the pod was unable to bind to those ports for some reason.
>
> $ oc logs -f pod/router-1-y5prn
> I0727 11:45:41.395016   1 router.go:161] Router is including routes in
> all namespaces
> E0727 11:45:41.493170   1 ratelimiter.go:50] error reloading router:
> exit status 1
> [ALERT] 208/114541 (30) : Starting frontend public: cannot bind socket [
> 0.0.0.0:80]
> [ALERT] 208/114541 (30) : Starting frontend public_ssl: cannot bind socket
> [0.0.0.0:443]
>
>
> On 27 July 2016 at 21:21, Clayton Coleman  wrote:
>
>> Is anything already listening on port 80/443/1936 on your host?  Did the
>> router pod get created successfully (oc get pods -n default)?
>>
>>
>>
>> On Jul 27, 2016, at 7:12 AM, Lionel Orellana  wrote:
>>
>> My  iptables has these rules. Is this normal?
>>
>> Chain KUBE-SERVICES (1 references)
>> target prot opt source   destination
>> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
>> default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with
>> icmp-port-unreachable
>> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
>> default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with
>> icmp-port-unreachable
>> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
>> default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with
>> icmp-port-unreachable
>>
>>
>> On 27 July 2016 at 16:08, Lionel Orellana  wrote:
>>
>>> Further info
>>>
>>> $ oc get endpoints --namespace=default --selector=router
>>>
>>> NAME ENDPOINTS AGE
>>> router  1h
>>>
>>> Router has no endpoints?
>>>
>>>
>>>
>>> On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana 
>>> wrote:
>>>
 Forgot to mention

 Openshift v1.3.0-alpha.2
 Docker 1.11.2
 Ubuntu 15.10

 On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
 wrote:

> Hi
>
> I'm trying the new cluster up command. It seems to run Ok and I can
> deploy an app (Jenkins, from the template) that also seems to start fine.
> But I can't hit it. When I go to the url shown in the route chrome says
> "site can't be reached".
>
> If I login to the host I can curl the aplication on the internal
> ip/port.
>
> Seems like a dns issue but I thought xip.io was supposed to take care
> of that.
>
> Do I need to do anything to make my service accessible from outside?
>
> Thanks
>
>
> Lionel.
>
>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc cluster up - dns issue?

[Clayton Coleman]

Is anything already listening on port 80/443/1936 on your host?  Did the
router pod get created successfully (oc get pods -n default)?



On Jul 27, 2016, at 7:12 AM, Lionel Orellana  wrote:

My  iptables has these rules. Is this normal?

Chain KUBE-SERVICES (1 references)
target prot opt source   destination
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with
icmp-port-unreachable
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with
icmp-port-unreachable
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with
icmp-port-unreachable


On 27 July 2016 at 16:08, Lionel Orellana  wrote:

> Further info
>
> $ oc get endpoints --namespace=default --selector=router
>
> NAME ENDPOINTS AGE
> router  1h
>
> Router has no endpoints?
>
>
>
> On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana 
> wrote:
>
>> Forgot to mention
>>
>> Openshift v1.3.0-alpha.2
>> Docker 1.11.2
>> Ubuntu 15.10
>>
>> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
>> wrote:
>>
>>> Hi
>>>
>>> I'm trying the new cluster up command. It seems to run Ok and I can
>>> deploy an app (Jenkins, from the template) that also seems to start fine.
>>> But I can't hit it. When I go to the url shown in the route chrome says
>>> "site can't be reached".
>>>
>>> If I login to the host I can curl the aplication on the internal ip/port.
>>>
>>> Seems like a dns issue but I thought xip.io was supposed to take care
>>> of that.
>>>
>>> Do I need to do anything to make my service accessible from outside?
>>>
>>> Thanks
>>>
>>>
>>> Lionel.
>>>
>>>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc cluster up - dns issue?

[Lionel Orellana]

Don't think so.

$ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State
PID/Program name
tcp0  0 104.236.65.18:530.0.0.0:*   LISTEN
 1268/openshift
tcp0  0 0.0.0.0:80530.0.0.0:*   LISTEN
 1268/openshift
tcp0  0 0.0.0.0:22  0.0.0.0:*   LISTEN
 776/sshd
tcp0  0 0.0.0.0:84430.0.0.0:*   LISTEN
 1268/openshift
tcp6   0  0 :::4001 :::*LISTEN
 1268/openshift
tcp6   0  0 :::2376 :::*LISTEN
 595/docker
tcp6   0  0 :::10250:::*LISTEN
 1268/openshift
tcp6   0  0 :::22   :::*LISTEN
 776/sshd
tcp6   0  0 :::7001 :::*LISTEN
 1268/openshift
udp0  0 0.0.0.0:80530.0.0.0:*
1268/openshift
udp0  0 104.236.65.18:530.0.0.0:*
1268/openshift

But the pod was unable to bind to those ports for some reason.

$ oc logs -f pod/router-1-y5prn
I0727 11:45:41.395016   1 router.go:161] Router is including routes in
all namespaces
E0727 11:45:41.493170   1 ratelimiter.go:50] error reloading router:
exit status 1
[ALERT] 208/114541 (30) : Starting frontend public: cannot bind socket [
0.0.0.0:80]
[ALERT] 208/114541 (30) : Starting frontend public_ssl: cannot bind socket [
0.0.0.0:443]


On 27 July 2016 at 21:21, Clayton Coleman  wrote:

> Is anything already listening on port 80/443/1936 on your host?  Did the
> router pod get created successfully (oc get pods -n default)?
>
>
>
> On Jul 27, 2016, at 7:12 AM, Lionel Orellana  wrote:
>
> My  iptables has these rules. Is this normal?
>
> Chain KUBE-SERVICES (1 references)
> target prot opt source   destination
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with
> icmp-port-unreachable
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with
> icmp-port-unreachable
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with
> icmp-port-unreachable
>
>
> On 27 July 2016 at 16:08, Lionel Orellana  wrote:
>
>> Further info
>>
>> $ oc get endpoints --namespace=default --selector=router
>>
>> NAME ENDPOINTS AGE
>> router  1h
>>
>> Router has no endpoints?
>>
>>
>>
>> On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana 
>> wrote:
>>
>>> Forgot to mention
>>>
>>> Openshift v1.3.0-alpha.2
>>> Docker 1.11.2
>>> Ubuntu 15.10
>>>
>>> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
>>> wrote:
>>>
 Hi

 I'm trying the new cluster up command. It seems to run Ok and I can
 deploy an app (Jenkins, from the template) that also seems to start fine.
 But I can't hit it. When I go to the url shown in the route chrome says
 "site can't be reached".

 If I login to the host I can curl the aplication on the internal
 ip/port.

 Seems like a dns issue but I thought xip.io was supposed to take care
 of that.

 Do I need to do anything to make my service accessible from outside?

 Thanks


 Lionel.


> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc cluster up - dns issue?

[Andrew Lau]

I had a similar issue on F23 and oc cluster up, the dns service couldn't be
reached by the pods.
Restarting firewalld then docker fixed it for me.

On Wed, 27 Jul 2016 at 21:22 Clayton Coleman  wrote:

> Is anything already listening on port 80/443/1936 on your host?  Did the
> router pod get created successfully (oc get pods -n default)?
>
>
>
> On Jul 27, 2016, at 7:12 AM, Lionel Orellana  wrote:
>
> My  iptables has these rules. Is this normal?
>
> Chain KUBE-SERVICES (1 references)
> target prot opt source   destination
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with
> icmp-port-unreachable
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with
> icmp-port-unreachable
> REJECT tcp  --  0.0.0.0/0172.30.52.230/*
> default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with
> icmp-port-unreachable
>
>
> On 27 July 2016 at 16:08, Lionel Orellana  wrote:
>
>> Further info
>>
>> $ oc get endpoints --namespace=default --selector=router
>>
>> NAME ENDPOINTS AGE
>> router  1h
>>
>> Router has no endpoints?
>>
>>
>>
>> On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana 
>> wrote:
>>
>>> Forgot to mention
>>>
>>> Openshift v1.3.0-alpha.2
>>> Docker 1.11.2
>>> Ubuntu 15.10
>>>
>>> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
>>> wrote:
>>>
 Hi

 I'm trying the new cluster up command. It seems to run Ok and I can
 deploy an app (Jenkins, from the template) that also seems to start fine.
 But I can't hit it. When I go to the url shown in the route chrome says
 "site can't be reached".

 If I login to the host I can curl the aplication on the internal
 ip/port.

 Seems like a dns issue but I thought xip.io was supposed to take care
 of that.

 Do I need to do anything to make my service accessible from outside?

 Thanks


 Lionel.


> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc cluster up - dns issue?

[Lionel Orellana]

My  iptables has these rules. Is this normal?

Chain KUBE-SERVICES (1 references)
target prot opt source   destination
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:80-tcp has no endpoints */ tcp dpt:80 reject-with
icmp-port-unreachable
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:443-tcp has no endpoints */ tcp dpt:443 reject-with
icmp-port-unreachable
REJECT tcp  --  0.0.0.0/0172.30.52.230/*
default/router:1936-tcp has no endpoints */ tcp dpt:1936 reject-with
icmp-port-unreachable


On 27 July 2016 at 16:08, Lionel Orellana  wrote:

> Further info
>
> $ oc get endpoints --namespace=default --selector=router
>
> NAME ENDPOINTS AGE
> router  1h
>
> Router has no endpoints?
>
>
>
> On Wed, 27 Jul 2016 at 3:22 PM, Lionel Orellana 
> wrote:
>
>> Forgot to mention
>>
>> Openshift v1.3.0-alpha.2
>> Docker 1.11.2
>> Ubuntu 15.10
>>
>> On Wed, 27 Jul 2016 at 3:17 PM, Lionel Orellana 
>> wrote:
>>
>>> Hi
>>>
>>> I'm trying the new cluster up command. It seems to run Ok and I can
>>> deploy an app (Jenkins, from the template) that also seems to start fine.
>>> But I can't hit it. When I go to the url shown in the route chrome says
>>> "site can't be reached".
>>>
>>> If I login to the host I can curl the aplication on the internal ip/port.
>>>
>>> Seems like a dns issue but I thought xip.io was supposed to take care
>>> of that.
>>>
>>> Do I need to do anything to make my service accessible from outside?
>>>
>>> Thanks
>>>
>>>
>>> Lionel.
>>>
>>>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Every user can authenticate on docker registry on openshift

[Jordan Liggitt]

Correct, the username is ignored, the password is the API token.


On Wed, Jul 27, 2016 at 9:34 AM, Den Cowboy  wrote:

> Okay, and how is this used for Jenkins.
> I have a global service account on OpenShift which provides a token which
> can be used to authenticate on my registry.
> So our jenkins is performing a docker login -u everyuser -p $TOKEN
> https://registry...
>
> (our jenins is outside our environment)
>
> --
> From: ccole...@redhat.com
> Date: Wed, 27 Jul 2016 09:27:22 -0400
> Subject: Re: Every user can authenticate on docker registry on openshift
> To: dencow...@hotmail.com
> CC: users@lists.openshift.redhat.com
>
>
> You can authenticate - but you can only pull things you have access to.
>
> On Wed, Jul 27, 2016 at 8:59 AM, Den Cowboy  wrote:
>
> Is it normal that every user can authenticate on the docker-registry of
> openshift?
> I was always using the same user as my cluster-admin in my openshift.
> But now I tried something else:
>
> docker login -u userdoesnotexist \
> > -p u89cSfZVXBBxw1cYsIlGKcHHYM_ycxxxlI 172.30.xx.xx:5000
> Email (a...@mail.com):
> WARNING: login credentials saved in /home/centos/.docker/config.json
> Login Succeeded
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Persistent Storage MYSQL

[Ben Parees]

what are the permissions of the NFS exported volume?  and what is in the
export definition?


On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy  wrote:

> I try to make my MySQL pod persistent.
> I always did this on training-environmnents where my DNS-server was on my
> master and I had never issues.
> Now my NFS is on another server.
>
> My pv looks like this
> {
>   "apiVersion": "v1",
>   "kind": "PersistentVolume",
>   "metadata": {
> "name": "mysql-data"
>   },
>   "spec": {
> "capacity": {
> "storage": "20Gi"
> },
> "accessModes": [ "ReadWriteMany" ],
> "nfs": {
> "path": "/path/mysql",
> "server": "server-IP"
> }
>   }
> }
>
> I also created a pvc and edited the dc of my mysql to use it. Just like I
> always did on my training environment.
> After editting the dc there is a new deploy triggered but my pod is going
> in a recreation loop.
>
>
> 2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld
> (mysqld 5.6.26) starting as process 18 ...
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> *[*10:17*]*
> 
> 2016-07-27 08:17:01 7fd2befc3840  InnoDB: Operating system error number 13
> in a file operation.
> InnoDB: The error means mysqld does not have the access rights to
> InnoDB: the directory.
> 2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or opening ./ibdata1
> failed!
>
> Does someone know what could be the issue?
> When I create a directory /mnt on my node-host of OS I'm able to mount to
> my NFS storage server. So why isn't this working for my mysql container?
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

RE: Persistent Storage MYSQL

[Den Cowboy]

all users and all groups which are coming from that IP-range have access.
We're able to mount when we're using just a /mnt directory on our host. But not 
from inside our container.

From: dencow...@hotmail.com
To: bpar...@redhat.com; users@lists.openshift.redhat.com
Subject: RE: Persistent Storage MYSQL
Date: Wed, 27 Jul 2016 13:11:13 +




Yeah, that's something which is different. On my master I was working with 
exportfs -a etc.
But now it doesn't matter. The permissions are IP based. (we hadded the range 
in which are cluster is running)
[3:09] 

From: bpar...@redhat.com
Date: Wed, 27 Jul 2016 09:04:12 -0400
Subject: Re: Persistent Storage MYSQL
To: dencow...@hotmail.com
CC: users@lists.openshift.redhat.com

what are the permissions of the NFS exported volume?  and what is in the export 
definition?


On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy  wrote:



I try to make my MySQL pod persistent.
I always did this on training-environmnents where my DNS-server was on my 
master and I had never issues.
Now my NFS is on another server.

My pv looks like this
{
  "apiVersion": "v1",
  "kind": "PersistentVolume",
  "metadata": {
"name": "mysql-data"
  },
  "spec": {
"capacity": {
"storage": "20Gi"
},
"accessModes": [ "ReadWriteMany" ],
"nfs": {
"path": "/path/mysql",
"server": "server-IP"
}
  }
}

I also created a pvc and edited the dc of my mysql to use it. Just like I 
always did on my training environment.
After editting the dc there is a new deploy triggered but my pod is going in a 
recreation loop.


2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld (mysqld 
5.6.26) starting as process 18 ...
2016-07-27 08:17:01 18 [Warning] Can't create test file 
/var/lib/mysql/data/mysql-2-edp7q.lower-test
2016-07-27 08:17:01 18 [Warning] Can't create test file 
/var/lib/mysql/data/mysql-2-edp7q.lower-test
[10:17] 2016-07-27 08:17:01 7fd2befc3840  InnoDB: Operating system error number 
13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or opening ./ibdata1 failed!
Does someone know what could be the issue?
When I create a directory /mnt on my node-host of OS I'm able to mount to my 
NFS storage server. So why isn't this working for my mysql container?

  

___

users mailing list

users@lists.openshift.redhat.com

http://lists.openshift.redhat.com/openshiftmm/listinfo/users




-- 
Ben Parees | OpenShift


  

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Every user can authenticate on docker registry on openshift

[Clayton Coleman]

You can authenticate - but you can only pull things you have access to.

On Wed, Jul 27, 2016 at 8:59 AM, Den Cowboy  wrote:

> Is it normal that every user can authenticate on the docker-registry of
> openshift?
> I was always using the same user as my cluster-admin in my openshift.
> But now I tried something else:
>
> docker login -u userdoesnotexist \
> > -p u89cSfZVXBBxw1cYsIlGKcHHYM_ycxxxlI 172.30.xx.xx:5000
> Email (a...@mail.com):
> WARNING: login credentials saved in /home/centos/.docker/config.json
> Login Succeeded
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Persistent Storage MYSQL

[Den Cowboy]

I try to make my MySQL pod persistent.
I always did this on training-environmnents where my DNS-server was on my 
master and I had never issues.
Now my NFS is on another server.

My pv looks like this
{
  "apiVersion": "v1",
  "kind": "PersistentVolume",
  "metadata": {
"name": "mysql-data"
  },
  "spec": {
"capacity": {
"storage": "20Gi"
},
"accessModes": [ "ReadWriteMany" ],
"nfs": {
"path": "/path/mysql",
"server": "server-IP"
}
  }
}

I also created a pvc and edited the dc of my mysql to use it. Just like I 
always did on my training environment.
After editting the dc there is a new deploy triggered but my pod is going in a 
recreation loop.

2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld (mysqld 
5.6.26) starting as process 18 ...2016-07-27 08:17:01 18 [Warning] Can't create 
test file /var/lib/mysql/data/mysql-2-edp7q.lower-test2016-07-27 08:17:01 18 
[Warning] Can't create test file 
/var/lib/mysql/data/mysql-2-edp7q.lower-test[10:17] 2016-07-27 08:17:01 
7fd2befc3840  InnoDB: Operating system error number 13 in a file 
operation.InnoDB: The error means mysqld does not have the access rights 
toInnoDB: the directory.2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or 
opening ./ibdata1 failed!
Does someone know what could be the issue?
When I create a directory /mnt on my node-host of OS I'm able to mount to my 
NFS storage server. So why isn't this working for my mysql container?

  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Every user can authenticate on docker registry on openshift

[Den Cowboy]

Is it normal that every user can authenticate on the docker-registry of 
openshift?
I was always using the same user as my cluster-admin in my openshift.
But now I tried something else:

docker login -u userdoesnotexist \
> -p u89cSfZVXBBxw1cYsIlGKcHHYM_ycxxxlI 172.30.xx.xx:5000
Email (a...@mail.com):
WARNING: login credentials saved in /home/centos/.docker/config.json
Login Succeeded
  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

RE: Persistent Storage MYSQL

[Den Cowboy]

Yeah, that's something which is different. On my master I was working with 
exportfs -a etc.
But now it doesn't matter. The permissions are IP based. (we hadded the range 
in which are cluster is running)
[3:09] 

From: bpar...@redhat.com
Date: Wed, 27 Jul 2016 09:04:12 -0400
Subject: Re: Persistent Storage MYSQL
To: dencow...@hotmail.com
CC: users@lists.openshift.redhat.com

what are the permissions of the NFS exported volume?  and what is in the export 
definition?


On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy  wrote:



I try to make my MySQL pod persistent.
I always did this on training-environmnents where my DNS-server was on my 
master and I had never issues.
Now my NFS is on another server.

My pv looks like this
{
  "apiVersion": "v1",
  "kind": "PersistentVolume",
  "metadata": {
"name": "mysql-data"
  },
  "spec": {
"capacity": {
"storage": "20Gi"
},
"accessModes": [ "ReadWriteMany" ],
"nfs": {
"path": "/path/mysql",
"server": "server-IP"
}
  }
}

I also created a pvc and edited the dc of my mysql to use it. Just like I 
always did on my training environment.
After editting the dc there is a new deploy triggered but my pod is going in a 
recreation loop.


2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld (mysqld 
5.6.26) starting as process 18 ...
2016-07-27 08:17:01 18 [Warning] Can't create test file 
/var/lib/mysql/data/mysql-2-edp7q.lower-test
2016-07-27 08:17:01 18 [Warning] Can't create test file 
/var/lib/mysql/data/mysql-2-edp7q.lower-test
[10:17] 2016-07-27 08:17:01 7fd2befc3840  InnoDB: Operating system error number 
13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or opening ./ibdata1 failed!
Does someone know what could be the issue?
When I create a directory /mnt on my node-host of OS I'm able to mount to my 
NFS storage server. So why isn't this working for my mysql container?

  

___

users mailing list

users@lists.openshift.redhat.com

http://lists.openshift.redhat.com/openshiftmm/listinfo/users




-- 
Ben Parees | OpenShift


  ___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Persistent Storage MYSQL

[Ben Parees]

what about the permissions of the actual host directory you are exporting?

On Wed, Jul 27, 2016 at 9:11 AM, Den Cowboy  wrote:

> Yeah, that's something which is different. On my master I was working with
> exportfs -a etc.
> But now it doesn't matter. The permissions are IP based. (we hadded the
> range in which are cluster is running)
>
> *[*3:09*]*
> 
>
>
> --
> From: bpar...@redhat.com
> Date: Wed, 27 Jul 2016 09:04:12 -0400
> Subject: Re: Persistent Storage MYSQL
> To: dencow...@hotmail.com
> CC: users@lists.openshift.redhat.com
>
>
> what are the permissions of the NFS exported volume?  and what is in the
> export definition?
>
>
> On Wed, Jul 27, 2016 at 8:35 AM, Den Cowboy  wrote:
>
> I try to make my MySQL pod persistent.
> I always did this on training-environmnents where my DNS-server was on my
> master and I had never issues.
> Now my NFS is on another server.
>
> My pv looks like this
> {
>   "apiVersion": "v1",
>   "kind": "PersistentVolume",
>   "metadata": {
> "name": "mysql-data"
>   },
>   "spec": {
> "capacity": {
> "storage": "20Gi"
> },
> "accessModes": [ "ReadWriteMany" ],
> "nfs": {
> "path": "/path/mysql",
> "server": "server-IP"
> }
>   }
> }
>
> I also created a pvc and edited the dc of my mysql to use it. Just like I
> always did on my training environment.
> After editting the dc there is a new deploy triggered but my pod is going
> in a recreation loop.
>
>
> 2016-07-27 08:17:01 0 [Note] /opt/rh/rh-mysql56/root/usr/libexec/mysqld
> (mysqld 5.6.26) starting as process 18 ...
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> 2016-07-27 08:17:01 18 [Warning] Can't create test file
> /var/lib/mysql/data/mysql-2-edp7q.lower-test
> *[*10:17*]*
> 
> 2016-07-27 08:17:01 7fd2befc3840  InnoDB: Operating system error number 13
> in a file operation.
> InnoDB: The error means mysqld does not have the access rights to
> InnoDB: the directory.
> 2016-07-27 08:17:01 18 [ERROR] InnoDB: Creating or opening ./ibdata1
> failed!
>
> Does someone know what could be the issue?
> When I create a directory /mnt on my node-host of OS I'm able to mount to
> my NFS storage server. So why isn't this working for my mysql container?
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
>
> --
> Ben Parees | OpenShift
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users