Re: connection to CRC from CRS

[Gerard Braad]

Hi,

>> You are however able to login from the console/dashboard?
> The console, for me, isn't at the hostname you mentioned.

The question was about resolving addresses and if the console login works
at all.
As it seems `oc` works when connecting to the API endpoint, right?

> able to login <...> as kubeadmin.

Have you tried using the developer/developer combination?

So far, this does not look like an issue with CRC. Do file an issue at our
repo http://github.com/code-ready/crc/issues
... although this likely seems to be something with the connector.

Also, as it seems to mention CDK/Minishift (which are OpenShift 3.x-based),
I would wonder if the version you use understands OpenShift 4.x-based
clusters. Can you verify this?

regards,


Gerard

On Mon, Nov 18, 2019 at 12:36 PM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:

> Gerard,
>
> The console, for me, isn't at the hostname you mentioned. What you've
> specified is my api server hostname.
>
> [zaphod@oc6010654212 ~]$ oc get route --all-namespaces | grep console
> openshift-console  console
> console-openshift-console.apps-crc.testing   console
>   https  reencrypt/Redirect None
> openshift-console  downloads
> downloads-openshift-console.apps-crc.testing downloads
>   http   edge/Redirect  None
>
> I _am_ able to login at console-openshift-console.apps-crc.testing as
> kubeadmin.
>
> Regards,
> Marvin
>
> On Sun, Nov 17, 2019 at 9:08 PM Gerard Braad  wrote:
>
>> Hi,
>>
>> not sure why this wouldn't work. You are however able to login from the
>> console/dashboard?
>> (To make sure the hostname gets resolved; api.crc.testing)
>>
>> Since CRC is a full OpenShift 4.x installation without specific
>> configuration, it would behave the same as any other OpenShift 4.x install.
>> Have you been able to verify if the connector works with a OpenShift
>> installer deployed cluster, like on AWS or other cloud provider?
>>
>> regards,
>>
>>
>> Gerard
>>
>> On Mon, Nov 18, 2019 at 9:18 AM Just Marvin <
>> marvin.the.cynical.ro...@gmail.com> wrote:
>>
>>> Any takers on this question?
>>>
>>> On Sun, Nov 10, 2019 at 11:52 AM Just Marvin <
>>> marvin.the.cynical.ro...@gmail.com> wrote:
>>>
>>>
>>Gerard Braad | http://gbraad.nl
>>[ Doing Open Source Matters ]
>>
>

-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: connection to CRC from CRS

[Gerard Braad]

Hi,

not sure why this wouldn't work. You are however able to login from the
console/dashboard?
(To make sure the hostname gets resolved; api.crc.testing)

Since CRC is a full OpenShift 4.x installation without specific
configuration, it would behave the same as any other OpenShift 4.x install.
Have you been able to verify if the connector works with a OpenShift
installer deployed cluster, like on AWS or other cloud provider?

regards,


Gerard

On Mon, Nov 18, 2019 at 9:18 AM Just Marvin <
marvin.the.cynical.ro...@gmail.com> wrote:

> Any takers on this question?
>
> On Sun, Nov 10, 2019 at 11:52 AM Just Marvin <
> marvin.the.cynical.ro...@gmail.com> wrote:
>
>
   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: DNS resolution performance woeful while CRC is running in Windows

[Gerard Braad]

We add the VM's IP address to the vEthernet (Default Switch) to allow DNS
to work for the crc.testing domain.
Not sure why the IPv6 addresses get enabled for you, but this might be a
side-effect? However, we do not explicitly set those, so it must be what
Windows infers?
We do perform lookups from the VM, but perhaps this might be blocked in
your case and this causes timeouts? From the described behaviour it seems
like this is happening (since stopping CRC restores this).

Setting entries in the hosts-file might be a possible fallback, as it also
helps those who can not add nameservers to the interface. IIRC this is
described in the documentation for VirtualBox use... in that case you can
cancel the UAC popup that follows near the end of the start to prevent
changing/adding the nameserver.

Can you file an issue on the tracker so we can prioritize this, but also
add more information about the setup and discuss a possible solution?


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

Re: [crc] expired certs

[Gerard Braad]

t;>
>>> > - Original Message -
>>> > > Hi,
>>> > >
>>> > > Getting this, this morning:
>>> > >
>>> > > INFO Checking if CRC bundle is cached in '$HOME/.crc'
>>> > > INFO Starting stopped VM ...
>>> > > INFO Verifying validity of the cluster certificates ...
>>> > > ERRO Error occurred: Certs have expired, they were valid till: 09 Oct 19
>>> > > 12:47 +
>>> > > [zaphod@oc6010654212 ~]$
>>> > >
>>> > > How do I fix this?
>>> > >
>>> > > Regards,
>>> > > Marvin
>>> > >
>>> > > ___
>>> > > 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
>>> >
>>>
>>> --
>>> Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
>>> veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
>>> http://veillard.com/ | virtualization library  http://libvirt.org/
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users



-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

Re: okd4

[Gerard Braad]

Hi,

A single-node might be possible using the same method as CRC,
github.com/code-ready/snc in which the node operates as a converged
master/worker.

Note: the `oc cluster up` equivalent will likely be CRC.


Gerard

On Tue, Oct 8, 2019 at 9:34 PM Clayton Coleman  wrote:

> OKD is being worked.  There is a roadmap in the OKD community group and
> it’s primarily an issue of getting FCoS inside.
>
> There won’t be a cluster up equivalent, by there may be a single node
> option eventually.
>
> On Oct 8, 2019, at 5:10 AM, Charles Moulliard  wrote:
>
> So, No plans exist to release okd4 ?
>
> On Thu, Oct 3, 2019 at 2:15 PM John Mazzitelli  wrote:
>
>> oc cluster up is gone in 4.x - replaced with CRC:
>> https://github.com/code-ready/crc
>>
>> - Original Message -
>> > Hi
>> >
>> > Is is planned to release okd4 - https://www.okd.io/ and that we still
>> have a
>> > nice way to start a cluster -> `oc cluster up` ?
>> >
>> > Best regards
>> >
>> > Charles
>>
>> ___
>> 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
>


-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Ruby-ex deployment times out

[Gerard Braad]

Same is reproducible on Atomic after an rpm-ostree upgrade

[fedora@atomic 
openshift-origin-client-tools-v1.3.0-3ab7af3d097b57f933eccef684a714f2368804e7-linux-64bit]$
docker version
Client:
 Version: 1.10.3
 API version: 1.22
 Package version: docker-1.10.3-52.git8b7fa4a.fc24.x86_64
 Go version:  go1.6.3
 Git commit:  8b7fa4a/1.10.3
 Built:
 OS/Arch: linux/amd64

Server:
 Version: 1.10.3
 API version: 1.22
 Package version: docker-1.10.3-52.git8b7fa4a.fc24.x86_64
 Go version:  go1.6.3
 Git commit:  8b7fa4a/1.10.3
 Built:
 OS/Arch: linux/amd64

On Fri, Sep 30, 2016 at 9:13 AM, Gerard Braad <m...@gbraad.nl> wrote:
> On Fri, Sep 30, 2016 at 1:16 AM, Seth Jennings <sjenn...@redhat.com> wrote:
>> You can go to koji and downgrade to an old version (this is the one I used):
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=796377
>
> Currently on C7, and waiting for a fix instead
>
>> I've opened a bug to track this:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1380474
>
> Will follow-up and watch this issue...
>
>
> Slightly off-topic
> I have noticed that Docker in general on F24 has not been as stable to
> this version.
> I run:
>
>Git commit:  8b7fa4a/1.10.3
>
> Experienced several crashes on issuing an `oc` command that brought
> down docker and the OpenShift test cluster.
> This happened on two instances of F24 with this Docker version.
>
> --
>
>Gerard Braad | http://gbraad.nl
>[ Doing Open Source Matters ]



-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

Re: Ruby-ex deployment times out

[Gerard Braad]

On Fri, Sep 30, 2016 at 1:16 AM, Seth Jennings <sjenn...@redhat.com> wrote:
> You can go to koji and downgrade to an old version (this is the one I used):
> http://koji.fedoraproject.org/koji/buildinfo?buildID=796377

Currently on C7, and waiting for a fix instead

> I've opened a bug to track this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1380474

Will follow-up and watch this issue...


Slightly off-topic
I have noticed that Docker in general on F24 has not been as stable to
this version.
I run:

   Git commit:  8b7fa4a/1.10.3

Experienced several crashes on issuing an `oc` command that brought
down docker and the OpenShift test cluster.
This happened on two instances of F24 with this Docker version.

-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

Re: Ruby-ex deployment times out

[Gerard Braad]

On Wed, Sep 28, 2016 at 10:56 PM, Michail Kargakis  wrote:
> I just updated from docker 1.9 to docker 1.10 and can reproduce this issue.
> I managed to deploy by using the RepoTags instead of the RepoDigest. Is this
> a known issue in the sense that there is a fix to it or we can only pull by
> tags?

I just did a clean install of F24 on a new instance

$ dnf update -y
$ dnf install -y curl docker git
$ vi /etc/sysconfig/docker # add --insecure-regsitry
$ systemctl start docker
$ curl -sSL 
https://github.com/openshift/origin/releases/download/v1.3.0/openshift-origin-client-tools-v1.3.0-3ab7af3d097b57f933eccef684a714f2368804e7-linux-64bit.tar.gz
-o oc-client.tar.gz
$ tar -zxvf oc-client.tar.gz
$ mkdir -p /opt/openshift/client
$ cp 
./openshift-origin-client-tools-v1.3.0-3ab7af3d097b57f933eccef684a714f2368804e7-linux-64bit/oc
/opt/openshift/client/oc
$ export PATH=$PATH:/opt/openshift/client/
$ oc cluster up
$ oc new-app openshift/ruby-20-centos7~https://github.com/openshift/ruby-ex

Same problem reported...

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

Re: Ruby-ex deployment times out

[Gerard Braad]

On Wed, Sep 28, 2016 at 10:26 PM, Andy Goldstein  wrote:
> sudo cat /var/lib/docker/image/devicemapper/repositories.json | python
> -mjson.tool

https://gist.github.com/gbraad/e82edffb671a5dd154a939491514f7f8#file-to-andy-goldstein-md

Currently recreating another environment. If you need access to debug,
just let me know and I can add you as an authorized key.

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

Re: Ruby-ex deployment times out

[Gerard Braad]

On Wed, Sep 28, 2016 at 6:50 PM, Andy Goldstein  wrote:
> Gerard, were you on docker 1.8 and did you then upgrade to 1.9 or 1.10? I
> recall a bug we had that sounds similar to what you're seeing here.

I had not done an upgrade at all.
a clean cloud image install:

$ dnf install -y curl docker
$ docker -v
Docker version 1.10.3, build 8b7fa4a/1.10.3

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

Re: Ruby-ex deployment times out

[Gerard Braad]

Hi,

On Wed, Sep 28, 2016 at 9:00 AM, Gerard Braad <m...@gbraad.nl> wrote:
> Full output I posted here:
> https://gist.github.com/gbraad/e82edffb671a5dd154a939491514f7f8

Created an almost similar environment (using CentOS 7 1602 instead of
Fedora 24) and the same steps yield a working situation. It is most
likely something with the versions of Docker? Anyways, I will see what
more information I can find, but the output for C7 I posted in the
same Gist.

regards,


Gerard


-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

Re: Ruby-ex deployment times out

[Gerard Braad]

Hi,


although the image was pushed during the build, it says: Failed to
pull image "172.30.165.95:5000/myproject/ruby-ex


Manually pulling gives:

$ docker pull 172.30.165.95:5000/myproject/ruby-ex:latest
Trying to pull repository 172.30.165.95:5000/myproject/ruby-ex ...
Pulling repository 172.30.165.95:5000/myproject/ruby-ex
Error: image myproject/ruby-ex not found


On Wed, Sep 28, 2016 at 12:27 AM, Clayton Coleman <ccole...@redhat.com> wrote:
> You can run "oc get events" to see the message about pulling,

$ oc get events
LASTSEEN   FIRSTSEEN   COUNT NAME   KIND
SUBOBJECT TYPE  REASON   SOURCE
9s 22s 2 ruby-ex-3-dtdy0Pod
spec.containers{ruby-ex}  Warning   Failed   {kubelet
10.5.0.27}Failed to pull image
"172.30.165.95:5000/myproject/ruby-ex@sha256:df71f696941a9daa5daaea808cfcaaf72071d7ad206833c1b95a5060dd95ca92":
Cannot overwrite digest
sha256:df71f696941a9daa5daaea808cfcaaf72071d7ad206833c1b95a5060dd95ca92
9s 22s 2 ruby-ex-3-dtdy0Pod
 Warning   FailedSync   {kubelet 10.5.0.27}
Error syncing pod, skipping: failed to "StartContainer" for "ruby-ex"
with ErrImagePull: "Cannot overwrite digest
sha256:df71f696941a9daa5daaea808cfcaaf72071d7ad206833c1b95a5060dd95ca92"

21s   21s   1 ruby-ex-3-dtdy0   Pod
spec.containers{ruby-ex}   NormalBackOff  {kubelet 10.5.0.27}
 Back-off pulling image
"172.30.165.95:5000/myproject/ruby-ex@sha256:df71f696941a9daa5daaea808cfcaaf72071d7ad206833c1b95a5060dd95ca92"


> image to the internal registry, docker has to have --insecure-registry set.

Docker is configured with:

OPTIONS='--selinux-enabled --log-driver=journald --insecure-registry
172.30.0.0/16'


Full output I posted here:
https://gist.github.com/gbraad/e82edffb671a5dd154a939491514f7f8

regards,


Gerard

-- 

   Gerard Braad | http://gbraad.nl
   [ Doing Open Source Matters ]

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

Re: Ruby-ex deployment times out

[Gerard Braad]

On Tue, Sep 27, 2016 at 11:17 PM, Clayton Coleman  wrote:
> oc logs POD_NAME

$ oc log ruby-ex-2-7ywo7
W0927 15:20:50.019027   17417 cmd.go:269] log is DEPRECATED and will
be removed in a future version. Use logs instead.
Error from server: container "ruby-ex" in pod "ruby-ex-2-7ywo7" is
waiting to start: trying and failing to pull image

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