[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 25 Feb 2020 at 23:22, Nathanaël Blanchet  wrote:

>
>
> Le 25 févr. 2020 15:11, Roy Golan  a écrit :
>
>
>
> On Fri, 21 Feb 2020 at 14:52, Nathanaël Blanchet  wrote:
>
> Hello,
>
> It seems that the work for including ovirt as a provider in the master
> branch of openshift installer has been done. I compiled the master code and
> ovirt does appear in the survey.
> I don't have much time to test it for now but is it operationnal? If yes,
> I will prior to have a look to it.
>
>
> It is operational, yes - which OS are you going to use?
>
> You must pick a release image - you can use this I think
registry.svc.ci.openshift.org/origin/release:4.4.0-0.okd-2020-02-25-003044
Do note that the images may be deleted by CI every 4-5 days. I'll ask for a
permanent release.

The choice seems to be done between RHCOS ans FCOS doesn't it? I would
> prefer FCOS. Do I have to preset a template or the installer downloads the
> template by its own?
> Okd 4.4 is still in alpha preview, is it stable enough, what does it still
> miss?
>

Will work with RHCOS, I'm not sure about FCOS. +Nisim Simsolo
 did you try FCOS and ignition yet?

If you want to join the discussion or to get updated with OKD I recommend
joining at #openshift-dev on slack.k8s.io

Thanks.
> Le 06/01/2020 à 21:30, Roy Golan a écrit :
>
>
>
> The merge window is now open for the masters branches of the various
> origin components.
> Post merge there should be an OKD release - this is not under my control,
> but when it will be available I'll let you know.
>
> On Mon, 6 Jan 2020 at 20:54, Nathanaël Blanchet  wrote:
>
> Hello Roy
> Le 21/11/2019 à 13:57, Roy Golan a écrit :
>
>
>
> On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:
>
>
>
> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet  wrote:
>
>
> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>
>
> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>
>
>
> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet  wrote:
>
> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>
> oc get -o json clusterversion
>
> This is the output of the previous failed deployment, I'll give a try to a
> newer one when I'll have a minute to test
>
> Without changing nothing with template,  I gave a new try and... nothing
> works anymore now, none of provided IPs can be pingued : dial tcp
> 10.34.212.51:6443: connect: no route to host", so none of masters can be
> provisonned by bootstrap.
>
> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
> Obviously something changed since my first attempt 12 days ago... is your
> docker image for openshift-installer up to date?
>
> Are you still able to your side to deploy a valid cluster ?
>
> I investigated looking at bootstrap logs (attached) and it seems that
> every containers die immediately after been started.
>
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571 +
> UTC m=+0.794838407 container init
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
> + UTC m=+0.816959853 container start
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
> + UTC m=+0.817576965 container attach
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:34 localhost systemd[1]:
> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
> Consumed 814ms CPU time
> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
> + UTC m=+1.294332779 container died
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
> + UTC m=+2.332285844 container remove
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>
> and this:
>
> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
> remote_runtime.go:200] CreateContainer in sandbox
> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
> runtime service failed: rpc error: code = Unknown desc = container create
> failed: container_linux.go:345: starting container process caused "exec:
> \"runtimecfg\": executable file not found in $PATH"
> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
> kuberuntime_manager.go:783] init container start failed:
> CreateContainerError: container create failed: container_linux.go:345:
> starting container process caused "exec: \"runtimecfg\": executable file
> not found in $PATH"
>
> What do you think about t

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 25 févr. 2020 15:11, Roy Golan  a écrit :On Fri, 21 Feb 2020 at 14:52, Nathanaël Blanchet  wrote:
  

  
  
Hello,
It seems that the work for including ovirt as a provider in the
  master branch of openshift installer has been done. I compiled the
  master code and ovirt does appear in the survey.
  I don't have much time to test it for now but is it operationnal?
  If yes, I will prior to have a look to it.It is operational, yes - which OS are you going to use? The choice seems to be done between RHCOS ans FCOS doesn't it? I would prefer FCOS. Do I have to preset a template or the installer downloads the template by its own? Okd 4.4 is still in alpha preview, is it stable enough, what does it still miss?
Thanks.

Le 06/01/2020 à 21:30, Roy Golan a
  écrit :


  
  



The merge window is now open for the masters branches of
  the various origin components.
Post merge there should be an OKD release - this is not
  under my control, but when it will be available I'll let you
  know.



  On Mon, 6 Jan 2020 at 20:54,
Nathanaël Blanchet  wrote:
  
  

  Hello Roy
  
  Le 21/11/2019 à 13:57, Roy Golan a écrit :
  
  

  
  
  
  
On Thu, 21 Nov
  2019 at 08:48, Roy Golan 
  wrote:


  




  On Wed, 20
Nov 2019 at 09:49, Nathanaël Blanchet 
wrote:
  
  

  
  
  Le 19/11/2019 à 19:23, Nathanaël
Blanchet a écrit :
  
  


Le 19/11/2019 à 13:43, Roy Golan a
  écrit :


  




  On
Tue, 19 Nov 2019 at 14:34,
Nathanaël Blanchet 
wrote:
  
  

  Le 19/11/2019 à 08:55,
Roy Golan a écrit :
  
  
oc get -o json clusterversion 
  
  This is the output of the
previous failed deployment,
I'll give a try to a newer
one when I'll have a minute
to test 
  

  

  

Without changing nothing with
  template,  I gave a new try and...
  nothing works anymore now, none of
  provided IPs can be pingued : dial tcp
  10.34.212.51:6443:
  connect: no route to host", so none of
  masters can be provisonned by
  bootstrap.

I tried with the latest rhcos and
  latest ovirt 4.3.7, it is the same.
  Obviously something changed since my
  first attempt 12 days ago... is your
  docker image for openshift-installer
  up to date?
Are you still able to your side to
  

[ovirt-users] Re: terraform integration

[Roy Golan]

On Fri, 21 Feb 2020 at 14:52, Nathanaël Blanchet  wrote:

> Hello,
>
> It seems that the work for including ovirt as a provider in the master
> branch of openshift installer has been done. I compiled the master code and
> ovirt does appear in the survey.
> I don't have much time to test it for now but is it operationnal? If yes,
> I will prior to have a look to it.
>

It is operational, yes - which OS are you going to use?

> Thanks.
> Le 06/01/2020 à 21:30, Roy Golan a écrit :
>
>
>
> The merge window is now open for the masters branches of the various
> origin components.
> Post merge there should be an OKD release - this is not under my control,
> but when it will be available I'll let you know.
>
> On Mon, 6 Jan 2020 at 20:54, Nathanaël Blanchet  wrote:
>
>> Hello Roy
>> Le 21/11/2019 à 13:57, Roy Golan a écrit :
>>
>>
>>
>> On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:
>>
>>>
>>>
>>> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet 
>>> wrote:
>>>

 Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :


 Le 19/11/2019 à 13:43, Roy Golan a écrit :



 On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet 
 wrote:

> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>
> oc get -o json clusterversion
>
> This is the output of the previous failed deployment, I'll give a try
> to a newer one when I'll have a minute to test
>
 Without changing nothing with template,  I gave a new try and...
 nothing works anymore now, none of provided IPs can be pingued : dial tcp
 10.34.212.51:6443: connect: no route to host", so none of masters can
 be provisonned by bootstrap.

 I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
 Obviously something changed since my first attempt 12 days ago... is your
 docker image for openshift-installer up to date?

 Are you still able to your side to deploy a valid cluster ?

 I investigated looking at bootstrap logs (attached) and it seems that
 every containers die immediately after been started.

 Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571
 + UTC m=+0.794838407 container init
 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
 registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
 Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
 + UTC m=+0.816959853 container start
 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
 registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
 Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
 + UTC m=+0.817576965 container attach
 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
 registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
 Nov 20 07:02:34 localhost systemd[1]:
 libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
 Consumed 814ms CPU time
 Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
 + UTC m=+1.294332779 container died
 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
 registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
 Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
 + UTC m=+2.332285844 container remove
 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
 registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)

 and this:

 Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.489527
 1909 remote_runtime.go:200] CreateContainer in sandbox
 "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
 runtime service failed: rpc error: code = Unknown desc = container create
 failed: container_linux.go:345: starting container process caused "exec:
 \"runtimecfg\": executable file not found in $PATH"
 Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.489714
 1909 kuberuntime_manager.go:783] init container start failed:
 CreateContainerError: container create failed: container_linux.go:345:
 starting container process caused "exec: \"runtimecfg\": executable file
 not found in $PATH"

 What do you think about this?

>>>
>>> I'm seeing the same now, checking...
>>>
>>>
>> Because of the move upstream to release OKD the release-image that comes
>> with the installer I gave you are no longer valid.
>>
>> I need to prepare an installer version with the preview of OKD, you can
>> find the details here
>> https://mobile.twitter.com/smarterclayton/status/1196477646885965824
>>
>> I tested your last openshift-installer container on quay.io, but the
>> ovirt provider is not available anymore. Will ovirt be supported as an OKD
>> 4.2 iaas provider ?
>>
>>
>>
>>
>> (do I need to use the terraform

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Hello,

It seems that the work for including ovirt as a provider in the master 
branch of openshift installer has been done. I compiled the master code 
and ovirt does appear in the survey.
I don't have much time to test it for now but is it operationnal? If 
yes, I will prior to have a look to it.


Thanks.

Le 06/01/2020 à 21:30, Roy Golan a écrit :



The merge window is now open for the masters branches of the various 
origin components.
Post merge there should be an OKD release - this is not under my 
control, but when it will be available I'll let you know.


On Mon, 6 Jan 2020 at 20:54, Nathanaël Blanchet > wrote:


Hello Roy

Le 21/11/2019 à 13:57, Roy Golan a écrit :



On Thu, 21 Nov 2019 at 08:48, Roy Golan mailto:rgo...@redhat.com>> wrote:



On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :



Le 19/11/2019 à 13:43, Roy Golan a écrit :



On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed
deployment, I'll give a try to a newer one when
I'll have a minute to test


Without changing nothing with template,  I gave a new
try and... nothing works anymore now, none of provided
IPs can be pingued : dial tcp 10.34.212.51:6443
: connect: no route to host",
so none of masters can be provisonned by bootstrap.

I tried with the latest rhcos and latest ovirt 4.3.7, it
is the same. Obviously something changed since my first
attempt 12 days ago... is your docker image for
openshift-installer up to date?

Are you still able to your side to deploy a valid cluster ?


I investigated looking at bootstrap logs (attached) and
it seems that every containers die immediately after been
started.

Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.60107571 + UTC m=+0.794838407 container init
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623197173 + UTC m=+0.816959853 container
start
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623814258 + UTC m=+0.817576965 container
attach
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:34 localhost systemd[1]:

libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
Consumed 814ms CPU time
Nov 20 07:02:34 localhost podman[2024]: 2019-11-20
07:02:34.100569998 + UTC m=+1.294332779 container
died
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:35 localhost podman[2024]: 2019-11-20
07:02:35.138523102 + UTC m=+2.332285844 container
remove
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)

and this:

Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489527    1909 remote_runtime.go:200]
CreateContainer in sandbox
"58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5"
from runtime service failed: rpc error: code = Unknown
desc = container create failed: container_linux.go:345:
starting container process caused "exec: \"runtimecfg\":
executable file not found in $PATH"
Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489714    1909 kuberuntime_manager.go:783] init

[ovirt-users] Re: terraform integration

[Roy Golan]

The merge window is now open for the masters branches of the various origin
components.
Post merge there should be an OKD release - this is not under my control,
but when it will be available I'll let you know.

On Mon, 6 Jan 2020 at 20:54, Nathanaël Blanchet  wrote:

> Hello Roy
> Le 21/11/2019 à 13:57, Roy Golan a écrit :
>
>
>
> On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:
>
>>
>>
>> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet 
>> wrote:
>>
>>>
>>> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>>>
>>>
>>> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet 
>>> wrote:
>>>
 Le 19/11/2019 à 08:55, Roy Golan a écrit :

 oc get -o json clusterversion

 This is the output of the previous failed deployment, I'll give a try
 to a newer one when I'll have a minute to test

>>> Without changing nothing with template,  I gave a new try and... nothing
>>> works anymore now, none of provided IPs can be pingued : dial tcp
>>> 10.34.212.51:6443: connect: no route to host", so none of masters can
>>> be provisonned by bootstrap.
>>>
>>> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
>>> Obviously something changed since my first attempt 12 days ago... is your
>>> docker image for openshift-installer up to date?
>>>
>>> Are you still able to your side to deploy a valid cluster ?
>>>
>>> I investigated looking at bootstrap logs (attached) and it seems that
>>> every containers die immediately after been started.
>>>
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571
>>> + UTC m=+0.794838407 container init
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
>>> + UTC m=+0.816959853 container start
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
>>> + UTC m=+0.817576965 container attach
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:34 localhost systemd[1]:
>>> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
>>> Consumed 814ms CPU time
>>> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
>>> + UTC m=+1.294332779 container died
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
>>> + UTC m=+2.332285844 container remove
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>>
>>> and this:
>>>
>>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
>>> remote_runtime.go:200] CreateContainer in sandbox
>>> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
>>> runtime service failed: rpc error: code = Unknown desc = container create
>>> failed: container_linux.go:345: starting container process caused "exec:
>>> \"runtimecfg\": executable file not found in $PATH"
>>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
>>> kuberuntime_manager.go:783] init container start failed:
>>> CreateContainerError: container create failed: container_linux.go:345:
>>> starting container process caused "exec: \"runtimecfg\": executable file
>>> not found in $PATH"
>>>
>>> What do you think about this?
>>>
>>
>> I'm seeing the same now, checking...
>>
>>
> Because of the move upstream to release OKD the release-image that comes
> with the installer I gave you are no longer valid.
>
> I need to prepare an installer version with the preview of OKD, you can
> find the details here
> https://mobile.twitter.com/smarterclayton/status/1196477646885965824
>
> I tested your last openshift-installer container on quay.io, but the
> ovirt provider is not available anymore. Will ovirt be supported as an OKD
> 4.2 iaas provider ?
>
>
>
>
> (do I need to use the terraform-workers tag instead of latest?)

 docker pull quay.io/rgolangh/openshift-installer:terraform-workers


 [root@openshift-installer
 openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
 json clusterversion
 {
 "apiVersion": "v1",
 "items": [
 {
 "apiVersion": "config.openshift.io/v1",
 "kind": "ClusterVersion",
 "metadata": {
 "creationTimestamp": "2019-11-07T12:23:06Z",
 "generation": 1,
 "name": "version",

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Hello Roy

Le 21/11/2019 à 13:57, Roy Golan a écrit :



On Thu, 21 Nov 2019 at 08:48, Roy Golan > wrote:




On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:


Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :



Le 19/11/2019 à 13:43, Roy Golan a écrit :



On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed deployment,
I'll give a try to a newer one when I'll have a minute
to test


Without changing nothing with template,  I gave a new try
and... nothing works anymore now, none of provided IPs can be
pingued : dial tcp 10.34.212.51:6443
: connect: no route to host", so
none of masters can be provisonned by bootstrap.

I tried with the latest rhcos and latest ovirt 4.3.7, it is
the same. Obviously something changed since my first attempt
12 days ago... is your docker image for openshift-installer
up to date?

Are you still able to your side to deploy a valid cluster ?


I investigated looking at bootstrap logs (attached) and it
seems that every containers die immediately after been started.

Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.60107571 + UTC m=+0.794838407 container init
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623197173 + UTC m=+0.816959853 container start
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623814258 + UTC m=+0.817576965 container attach
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:34 localhost systemd[1]:

libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
Consumed 814ms CPU time
Nov 20 07:02:34 localhost podman[2024]: 2019-11-20
07:02:34.100569998 + UTC m=+1.294332779 container died
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:35 localhost podman[2024]: 2019-11-20
07:02:35.138523102 + UTC m=+2.332285844 container remove
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)

and this:

Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489527    1909 remote_runtime.go:200] CreateContainer
in sandbox
"58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5"
from runtime service failed: rpc error: code = Unknown desc =
container create failed: container_linux.go:345: starting
container process caused "exec: \"runtimecfg\": executable
file not found in $PATH"
Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489714    1909 kuberuntime_manager.go:783] init
container start failed: CreateContainerError: container create
failed: container_linux.go:345: starting container process
caused "exec: \"runtimecfg\": executable file not found in $PATH"

What do you think about this?


I'm seeing the same now, checking...


Because of the move upstream to release OKD the release-image that 
comes with the installer I gave you are no longer valid.


I need to prepare an installer version with the preview of OKD, you 
can find the details here 
https://mobile.twitter.com/smarterclayton/status/1196477646885965824
I tested your last openshift-installer container on quay.io, but the 
ovirt provider is not available anymore. Will ovirt be supported as an 
OKD 4.2 iaas provider ?





(do I need to use the terraform-workers tag instead of
latest?)

docker pullquay.io/rgolangh/openshift-installer:terraform-workers  

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 21 Nov 2019 at 16:42, Nathanaël Blanchet  wrote:

>
> Le 21/11/2019 à 13:57, Roy Golan a écrit :
>
>
>
> On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:
>
>>
>>
>> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet 
>> wrote:
>>
>>>
>>> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>>>
>>>
>>> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet 
>>> wrote:
>>>
 Le 19/11/2019 à 08:55, Roy Golan a écrit :

 oc get -o json clusterversion

 This is the output of the previous failed deployment, I'll give a try
 to a newer one when I'll have a minute to test

>>> Without changing nothing with template,  I gave a new try and... nothing
>>> works anymore now, none of provided IPs can be pingued : dial tcp
>>> 10.34.212.51:6443: connect: no route to host", so none of masters can
>>> be provisonned by bootstrap.
>>>
>>> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
>>> Obviously something changed since my first attempt 12 days ago... is your
>>> docker image for openshift-installer up to date?
>>>
>>> Are you still able to your side to deploy a valid cluster ?
>>>
>>> I investigated looking at bootstrap logs (attached) and it seems that
>>> every containers die immediately after been started.
>>>
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571
>>> + UTC m=+0.794838407 container init
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
>>> + UTC m=+0.816959853 container start
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
>>> + UTC m=+0.817576965 container attach
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:34 localhost systemd[1]:
>>> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
>>> Consumed 814ms CPU time
>>> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
>>> + UTC m=+1.294332779 container died
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
>>> + UTC m=+2.332285844 container remove
>>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>>
>>> and this:
>>>
>>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
>>> remote_runtime.go:200] CreateContainer in sandbox
>>> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
>>> runtime service failed: rpc error: code = Unknown desc = container create
>>> failed: container_linux.go:345: starting container process caused "exec:
>>> \"runtimecfg\": executable file not found in $PATH"
>>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
>>> kuberuntime_manager.go:783] init container start failed:
>>> CreateContainerError: container create failed: container_linux.go:345:
>>> starting container process caused "exec: \"runtimecfg\": executable file
>>> not found in $PATH"
>>>
>>> What do you think about this?
>>>
>>
>> I'm seeing the same now, checking...
>>
>>
> Because of the move upstream to release OKD the release-image that comes
> with the installer I gave you are no longer valid.
>
> I need to prepare an installer version with the preview of OKD, you can
> find the details here
> https://mobile.twitter.com/smarterclayton/status/1196477646885965824
>
> Seems that okd4
> https://github.com/openshift/okd/releases/download/4.3.0-0.okd-2019-11-15-182656/openshift-install-linux-4.3.0-0.okd-2019-11-15-182656.tar.gz
> is a compiled binary without the ovirt installer. Can you tell where are
> sources so as to include ovirt extensions into the installer build?
>

Soon the CI will help us in building okd images from pull requests. I'll
update you when this will become available.


>
>
> (do I need to use the terraform-workers tag instead of latest?)

 docker pull quay.io/rgolangh/openshift-installer:terraform-workers


 [root@openshift-installer
 openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
 json clusterversion
 {
 "apiVersion": "v1",
 "items": [
 {
 "apiVersion": "config.openshift.io/v1",
 "kind": "ClusterVersion",
 "metadata": {
 "creationTimestamp": "2019-11-07T12:23:06Z",
 "generation": 1,
 

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 21/11/2019 à 13:57, Roy Golan a écrit :



On Thu, 21 Nov 2019 at 08:48, Roy Golan > wrote:




On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:


Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :



Le 19/11/2019 à 13:43, Roy Golan a écrit :



On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed deployment,
I'll give a try to a newer one when I'll have a minute
to test


Without changing nothing with template,  I gave a new try
and... nothing works anymore now, none of provided IPs can be
pingued : dial tcp 10.34.212.51:6443
: connect: no route to host", so
none of masters can be provisonned by bootstrap.

I tried with the latest rhcos and latest ovirt 4.3.7, it is
the same. Obviously something changed since my first attempt
12 days ago... is your docker image for openshift-installer
up to date?

Are you still able to your side to deploy a valid cluster ?


I investigated looking at bootstrap logs (attached) and it
seems that every containers die immediately after been started.

Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.60107571 + UTC m=+0.794838407 container init
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623197173 + UTC m=+0.816959853 container start
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623814258 + UTC m=+0.817576965 container attach
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:34 localhost systemd[1]:

libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
Consumed 814ms CPU time
Nov 20 07:02:34 localhost podman[2024]: 2019-11-20
07:02:34.100569998 + UTC m=+1.294332779 container died
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:35 localhost podman[2024]: 2019-11-20
07:02:35.138523102 + UTC m=+2.332285844 container remove
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)

and this:

Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489527    1909 remote_runtime.go:200] CreateContainer
in sandbox
"58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5"
from runtime service failed: rpc error: code = Unknown desc =
container create failed: container_linux.go:345: starting
container process caused "exec: \"runtimecfg\": executable
file not found in $PATH"
Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489714    1909 kuberuntime_manager.go:783] init
container start failed: CreateContainerError: container create
failed: container_linux.go:345: starting container process
caused "exec: \"runtimecfg\": executable file not found in $PATH"

What do you think about this?


I'm seeing the same now, checking...


Because of the move upstream to release OKD the release-image that 
comes with the installer I gave you are no longer valid.


I need to prepare an installer version with the preview of OKD, you 
can find the details here 
https://mobile.twitter.com/smarterclayton/status/1196477646885965824
Seems that okd4 
https://github.com/openshift/okd/releases/download/4.3.0-0.okd-2019-11-15-182656/openshift-install-linux-4.3.0-0.okd-2019-11-15-182656.tar.gz 
is a compiled binary without the ovirt installer. Can you tell where are 
sources so as to include ovirt extensions into the installer build?





(do I need to use the terraform-workers tag instead of
latest?)

docker pullquay.io/r

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:

>
>
> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet  wrote:
>
>>
>> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>>
>>
>> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet 
>> wrote:
>>
>>> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>>>
>>> oc get -o json clusterversion
>>>
>>> This is the output of the previous failed deployment, I'll give a try to
>>> a newer one when I'll have a minute to test
>>>
>> Without changing nothing with template,  I gave a new try and... nothing
>> works anymore now, none of provided IPs can be pingued : dial tcp
>> 10.34.212.51:6443: connect: no route to host", so none of masters can be
>> provisonned by bootstrap.
>>
>> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
>> Obviously something changed since my first attempt 12 days ago... is your
>> docker image for openshift-installer up to date?
>>
>> Are you still able to your side to deploy a valid cluster ?
>>
>> I investigated looking at bootstrap logs (attached) and it seems that
>> every containers die immediately after been started.
>>
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571
>> + UTC m=+0.794838407 container init
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
>> + UTC m=+0.816959853 container start
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
>> + UTC m=+0.817576965 container attach
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:34 localhost systemd[1]:
>> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
>> Consumed 814ms CPU time
>> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
>> + UTC m=+1.294332779 container died
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
>> + UTC m=+2.332285844 container remove
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>
>> and this:
>>
>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
>> remote_runtime.go:200] CreateContainer in sandbox
>> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
>> runtime service failed: rpc error: code = Unknown desc = container create
>> failed: container_linux.go:345: starting container process caused "exec:
>> \"runtimecfg\": executable file not found in $PATH"
>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
>> kuberuntime_manager.go:783] init container start failed:
>> CreateContainerError: container create failed: container_linux.go:345:
>> starting container process caused "exec: \"runtimecfg\": executable file
>> not found in $PATH"
>>
>> What do you think about this?
>>
>
> I'm seeing the same now, checking...
>
>
Because of the move upstream to release OKD the release-image that comes
with the installer I gave you are no longer valid.

I need to prepare an installer version with the preview of OKD, you can
find the details here
https://mobile.twitter.com/smarterclayton/status/1196477646885965824



(do I need to use the terraform-workers tag instead of latest?)
>>>
>>> docker pull quay.io/rgolangh/openshift-installer:terraform-workers
>>>
>>>
>>> [root@openshift-installer
>>> openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
>>> json clusterversion
>>> {
>>> "apiVersion": "v1",
>>> "items": [
>>> {
>>> "apiVersion": "config.openshift.io/v1",
>>> "kind": "ClusterVersion",
>>> "metadata": {
>>> "creationTimestamp": "2019-11-07T12:23:06Z",
>>> "generation": 1,
>>> "name": "version",
>>> "namespace": "",
>>> "resourceVersion": "3770202",
>>> "selfLink": "/apis/
>>> config.openshift.io/v1/clusterversions/version",
>>> "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
>>> },
>>> "spec": {
>>> "channel": "stable-4.3",
>>> "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
>>> "upstream":
>>> "https://api.openshift.com/api/upgrades_info/v1/graph";
>>> 
>>> },
>>> "status": {
>>>  

[ovirt-users] Re: terraform integration

[Roy Golan]

On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet  wrote:

>
> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>
>
> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>
>
>
> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet  wrote:
>
>> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>>
>> oc get -o json clusterversion
>>
>> This is the output of the previous failed deployment, I'll give a try to
>> a newer one when I'll have a minute to test
>>
> Without changing nothing with template,  I gave a new try and... nothing
> works anymore now, none of provided IPs can be pingued : dial tcp
> 10.34.212.51:6443: connect: no route to host", so none of masters can be
> provisonned by bootstrap.
>
> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
> Obviously something changed since my first attempt 12 days ago... is your
> docker image for openshift-installer up to date?
>
> Are you still able to your side to deploy a valid cluster ?
>
> I investigated looking at bootstrap logs (attached) and it seems that
> every containers die immediately after been started.
>
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571 +
> UTC m=+0.794838407 container init
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
> + UTC m=+0.816959853 container start
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
> + UTC m=+0.817576965 container attach
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:34 localhost systemd[1]:
> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
> Consumed 814ms CPU time
> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
> + UTC m=+1.294332779 container died
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
> + UTC m=+2.332285844 container remove
> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>
> and this:
>
> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
> remote_runtime.go:200] CreateContainer in sandbox
> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
> runtime service failed: rpc error: code = Unknown desc = container create
> failed: container_linux.go:345: starting container process caused "exec:
> \"runtimecfg\": executable file not found in $PATH"
> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
> kuberuntime_manager.go:783] init container start failed:
> CreateContainerError: container create failed: container_linux.go:345:
> starting container process caused "exec: \"runtimecfg\": executable file
> not found in $PATH"
>
> What do you think about this?
>

I'm seeing the same now, checking...

(do I need to use the terraform-workers tag instead of latest?)
>>
>> docker pull quay.io/rgolangh/openshift-installer:terraform-workers
>>
>>
>> [root@openshift-installer
>> openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
>> json clusterversion
>> {
>> "apiVersion": "v1",
>> "items": [
>> {
>> "apiVersion": "config.openshift.io/v1",
>> "kind": "ClusterVersion",
>> "metadata": {
>> "creationTimestamp": "2019-11-07T12:23:06Z",
>> "generation": 1,
>> "name": "version",
>> "namespace": "",
>> "resourceVersion": "3770202",
>> "selfLink": "/apis/
>> config.openshift.io/v1/clusterversions/version",
>> "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
>> },
>> "spec": {
>> "channel": "stable-4.3",
>> "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
>> "upstream":
>> "https://api.openshift.com/api/upgrades_info/v1/graph";
>> 
>> },
>> "status": {
>> "availableUpdates": null,
>> "conditions": [
>> {
>> "lastTransitionTime": "2019-11-07T12:23:12Z",
>> "status": "False",
>> "type": "Available"
>> },
>> {script
>> "lastTransitionTime": "2019-11-07T12:56:15Z",
>> "message": "Cluster operator image-registry is

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 19/11/2019 à 13:43, Roy Golan a écrit :



On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet > wrote:


Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed deployment, I'll give a
try to a newer one when I'll have a minute to test

Without changing nothing with template,  I gave a new try and... nothing 
works anymore now, none of provided IPs can be pingued : dial tcp 
10.34.212.51:6443: connect: no route to host", so none of masters can be 
provisonned by bootstrap.


I tried with the latest rhcos and latest ovirt 4.3.7, it is the same. 
Obviously something changed since my first attempt 12 days ago... is 
your docker image for openshift-installer up to date?


Are you still able to your side to deploy a valid cluster ?


(do I need to use the terraform-workers tag instead of latest?)

docker pullquay.io/rgolangh/openshift-installer:terraform-workers  



[root@openshift-installer
openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc
get -o json clusterversion
{
    "apiVersion": "v1",
    "items": [
    {
    "apiVersion": "config.openshift.io/v1
",
    "kind": "ClusterVersion",
    "metadata": {
    "creationTimestamp": "2019-11-07T12:23:06Z",
    "generation": 1,
    "name": "version",
    "namespace": "",
    "resourceVersion": "3770202",
    "selfLink":
"/apis/config.openshift.io/v1/clusterversions/version
",
    "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
    },
    "spec": {
    "channel": "stable-4.3",
    "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
    "upstream":
"https://api.openshift.com/api/upgrades_info/v1/graph";

    },
    "status": {
    "availableUpdates": null,
    "conditions": [
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "status": "False",
    "type": "Available"
    },
    {script
    "lastTransitionTime": "2019-11-07T12:56:15Z",
    "message": "Cluster operator
image-registry is still updating",
    "reason": "ClusterOperatorNotAvailable",
    "status": "True",
    "type": "Failing"
    },
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "message": "Unable to apply
4.3.0-0.okd-2019-10-29-180250: the cluster operator image-registry
has not yet successfully rolled out",
    "reason": "ClusterOperatorNotAvailable",
    "status": "True",
    "type": "Progressing"
    },
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "message": "Unable to retrieve available
updates: currently installed version 4.3.0-0.okd-2019-10-29-180250
not found in the \"stable-4.3\" channel",
    "reason": "RemoteFailed",
    "status": "False",
    "type": "RetrievedUpdates"
    }
    ],
    "desired": {
    "force": false,
    "image":

"registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9

",
    "version": "4.3.0-0.okd-2019-10-29-180250"


Indeed this version is not the latest and is missing the 
aforementioned fix for the registry.


    },
    "history": [
    {
    "completionTime": null,
    "image":

"registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9

",
    "startedTime": "2019-11-07T12:23:12Z",
    "state": "Partial",
    "verified": false,

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet  wrote:

> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>
> oc get -o json clusterversion
>
> This is the output of the previous failed deployment, I'll give a try to a
> newer one when I'll have a minute to test
>
> (do I need to use the terraform-workers tag instead of latest?)
>
> docker pull quay.io/rgolangh/openshift-installer:terraform-workers
>
>
> [root@openshift-installer
> openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
> json clusterversion
> {
> "apiVersion": "v1",
> "items": [
> {
> "apiVersion": "config.openshift.io/v1",
> "kind": "ClusterVersion",
> "metadata": {
> "creationTimestamp": "2019-11-07T12:23:06Z",
> "generation": 1,
> "name": "version",
> "namespace": "",
> "resourceVersion": "3770202",
> "selfLink": "/apis/
> config.openshift.io/v1/clusterversions/version",
> "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
> },
> "spec": {
> "channel": "stable-4.3",
> "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
> "upstream":
> "https://api.openshift.com/api/upgrades_info/v1/graph";
> 
> },
> "status": {
> "availableUpdates": null,
> "conditions": [
> {
> "lastTransitionTime": "2019-11-07T12:23:12Z",
> "status": "False",
> "type": "Available"
> },
> {script
> "lastTransitionTime": "2019-11-07T12:56:15Z",
> "message": "Cluster operator image-registry is
> still updating",
> "reason": "ClusterOperatorNotAvailable",
> "status": "True",
> "type": "Failing"
> },
> {
> "lastTransitionTime": "2019-11-07T12:23:12Z",
> "message": "Unable to apply
> 4.3.0-0.okd-2019-10-29-180250: the cluster operator image-registry has not
> yet successfully rolled out",
> "reason": "ClusterOperatorNotAvailable",
> "status": "True",
> "type": "Progressing"
> },
> {
> "lastTransitionTime": "2019-11-07T12:23:12Z",
> "message": "Unable to retrieve available updates:
> currently installed version 4.3.0-0.okd-2019-10-29-180250 not found in the
> \"stable-4.3\" channel",
> "reason": "RemoteFailed",
> "status": "False",
> "type": "RetrievedUpdates"
> }
> ],
> "desired": {
> "force": false,
> "image": "
> registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9
> ",
> "version": "4.3.0-0.okd-2019-10-29-180250"
>

Indeed this version is not the latest and is missing the aforementioned fix
for the registry.

},
> "history": [
> {
> "completionTime": null,
> "image": "
> registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9
> ",
> "startedTime": "2019-11-07T12:23:12Z",
> "state": "Partial",
> "verified": false,
> "version": "4.3.0-0.okd-2019-10-29-180250"
> }
> ],
> "observedGeneration": 1,
> "versionHash": "-3onP9QpPTg="
> }
> }
> ],
> "kind": "List",
> "metadata": {
> "resourceVersion": "",
> "selfLink": ""
> }
>
> }
>
>
> Can you answer to these few questions please?
>
>- The latest stable OKD version is 4.2.4. Is it possible to chose the
>version of okd when deploying (seems to use 4.3) or does the installer
>always download the latest OKD?
>
>

>
>- Can we use FCOS instead of RHCOS?
>
>

>- About the pull secret, do we absolutely need a redhat login to get
>this file to deploy an upstream OKD cluster and not downstream openshift?
>
>
> To answer the 3 of those, this specific build is not really OKD, and will
use 4.3 and Red Hat artifact and must use RHCOs, hence the pull secret
thing.
I frankly don't know when OKD 4.3 is going to be released, I guess it will
be on top FCOS.
I'll update the list once we have the oVirt installer for OKD ready for
testing (on FCOS)



-- 
> Nathanaël Blanche

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed deployment, I'll give a try to 
a newer one when I'll have a minute to test


(do I need to use the terraform-workers tag instead of latest?)

docker pull quay.io/rgolangh/openshift-installer:terraform-workers


[root@openshift-installer 
openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o 
json clusterversion

{
    "apiVersion": "v1",
    "items": [
    {
    "apiVersion": "config.openshift.io/v1",
    "kind": "ClusterVersion",
    "metadata": {
    "creationTimestamp": "2019-11-07T12:23:06Z",
    "generation": 1,
    "name": "version",
    "namespace": "",
    "resourceVersion": "3770202",
    "selfLink": 
"/apis/config.openshift.io/v1/clusterversions/version",

    "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
    },
    "spec": {
    "channel": "stable-4.3",
    "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
    "upstream": 
"https://api.openshift.com/api/upgrades_info/v1/graph";

    },
    "status": {
    "availableUpdates": null,
    "conditions": [
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "status": "False",
    "type": "Available"
    },
    {
    "lastTransitionTime": "2019-11-07T12:56:15Z",
    "message": "Cluster operator image-registry is 
still updating",

    "reason": "ClusterOperatorNotAvailable",
    "status": "True",
    "type": "Failing"
    },
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "message": "Unable to apply 
4.3.0-0.okd-2019-10-29-180250: the cluster operator image-registry has 
not yet successfully rolled out",

    "reason": "ClusterOperatorNotAvailable",
    "status": "True",
    "type": "Progressing"
    },
    {
    "lastTransitionTime": "2019-11-07T12:23:12Z",
    "message": "Unable to retrieve available 
updates: currently installed version 4.3.0-0.okd-2019-10-29-180250 not 
found in the \"stable-4.3\" channel",

    "reason": "RemoteFailed",
    "status": "False",
    "type": "RetrievedUpdates"
    }
    ],
    "desired": {
    "force": false,
    "image": 
"registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9",

    "version": "4.3.0-0.okd-2019-10-29-180250"
    },
    "history": [
    {
    "completionTime": null,
    "image": 
"registry.svc.ci.openshift.org/origin/release@sha256:68286e07f7d68ebc8a067389aabf38dee9f9b810c5520d6ee4593c38eb48ddc9",

    "startedTime": "2019-11-07T12:23:12Z",
    "state": "Partial",
    "verified": false,
    "version": "4.3.0-0.okd-2019-10-29-180250"
    }
    ],
    "observedGeneration": 1,
    "versionHash": "-3onP9QpPTg="
    }
    }
    ],
    "kind": "List",
    "metadata": {
    "resourceVersion": "",
    "selfLink": ""
    }

}


Can you answer to these few questions please?

 * The latest stable OKD version is 4.2.4. Is it possible to chose the
   version of okd when deploying (seems to use 4.3) or does the
   installer always download the latest OKD?
 * Can we use FCOS instead of RHCOS?
 * About the pull secret, do we absolutely need a redhat login to get
   this file to deploy an upstream OKD cluster and not downstream
   openshift?


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GN6N42RLIAW6T5KQVBILE5FWMMV4IDGJ/

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 12 Nov 2019 at 10:22, Nathanaël Blanchet  wrote:

> Le 08/11/2019 à 11:20, Nathanaël Blanchet a écrit :
>
>
>> That should have been solved by
>> https://github.com/openshift/cluster-image-registry-operator/pull/406
>>
>> nothing helped me, what am I supposed to do now for getting a working
> cluster?
>
> thank you
>

This exact image is passing CI. Anyhow some more changes are coming, that
will have
a good impact on resource (essentially spinning the worker later in the
process and not imediatly)

Can you try to run the install again?
What is the output of:

oc get -o json clusterversion


Is it merged? What should I do now, waiting for new release? I can't test
> installation further until this is not fixed.
>
> It seems to be a storage backend issue for the registry container.
>
> I noticed the openshift version is 4.3, is it possible to install a
> previous stable one?
>
> Does it mean all other openshift-installer providers are concerned by this
> bug?
>
>
>> Can you share `oc describe co/image-registry` ?
>>
>> I finally manged to connect to the cluster:
>
> ./oc describe co/image-registry
> Name: image-registry
> Namespace:
> Labels:   
> Annotations:  
> API Version:  config.openshift.io/v1
> Kind: ClusterOperator
> Metadata:
>   Creation Timestamp:  2019-11-07T12:33:15Z
>   Generation:  1
>   Resource Version:10637
>   Self Link:   /apis/
> config.openshift.io/v1/clusteroperators/image-registry
>   UID: 28c491ad-7e89-4269-a6e3-8751085e7653
> Spec:
> Status:
>   Conditions:
> Last Transition Time:  2019-11-07T12:31:52Z
> Message:   storage backend not configured
> Reason:StorageNotConfigured
> Status:False
> Type:  Available
> Last Transition Time:  2019-11-07T12:31:52Z
> Message:   Unable to apply resources: storage backend not
> configured
> Reason:Error
> Status:False
> Type:  Progressing
> Last Transition Time:  2019-11-07T12:31:52Z
> Message:   storage backend not configured
> Reason:StorageNotConfigured
> Status:True
> Type:  Degraded
>   Extension:   
>   Related Objects:
> Group: imageregistry.operator.openshift.io
> Name:  cluster
> Resource:  configs
> Group:
> Name:  openshift-image-registry
> Resource:  namespaces
> Events:
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XF2VSFIGWHELBE6OBCWUOCST4EJNGCO7/

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 08/11/2019 à 11:20, Nathanaël Blanchet a écrit :




That should have been solved by
https://github.com/openshift/cluster-image-registry-operator/pull/406


nothing helped me, what am I supposed to do now for getting a working 
cluster?


thank you

Is it merged? What should I do now, waiting for new release? I can't 
test installation further until this is not fixed.


It seems to be a storage backend issue for the registry container.

I noticed the openshift version is 4.3, is it possible to install a 
previous stable one?


Does it mean all other openshift-installer providers are concerned by 
this bug?




Can you share `oc describe co/image-registry` ?



I finally manged to connect to the cluster:

./oc describe co/image-registry

Name: image-registry
Namespace:
Labels:   
Annotations:  
API Version:  config.openshift.io/v1
Kind: ClusterOperator
Metadata:
  Creation Timestamp:  2019-11-07T12:33:15Z
  Generation:  1
  Resource Version:    10637
  Self Link: /apis/config.openshift.io/v1/clusteroperators/image-registry
  UID: 28c491ad-7e89-4269-a6e3-8751085e7653
Spec:
Status:
  Conditions:
    Last Transition Time:  2019-11-07T12:31:52Z
    Message:   storage backend not configured
    Reason:    StorageNotConfigured
    Status:    False
    Type:  Available
    Last Transition Time:  2019-11-07T12:31:52Z
    Message:   Unable to apply resources: storage backend 
not configured

    Reason:    Error
    Status:    False
    Type:  Progressing
    Last Transition Time:  2019-11-07T12:31:52Z
    Message:   storage backend not configured
    Reason:    StorageNotConfigured
    Status:    True
    Type:  Degraded
  Extension:   
  Related Objects:
    Group: imageregistry.operator.openshift.io
    Name:  cluster
    Resource:  configs
    Group:
    Name:  openshift-image-registry
    Resource:  namespaces
Events:    


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/44PY6O4RY364BRFYHBQD7QXJBD6Q3MQV/

[ovirt-users] Re: terraform integration

[Yedidyah Bar David]

On Thu, Nov 7, 2019 at 12:57 PM Roy Golan  wrote:

>
>
> On Thu, 7 Nov 2019 at 12:28, Nathanaël Blanchet  wrote:
>
>>
>> Le 07/11/2019 à 11:16, Roy Golan a écrit :
>>
>>
>>
>> On Thu, 7 Nov 2019 at 11:23, Nathanaël Blanchet  wrote:
>>
>>>
>>> Le 07/11/2019 à 07:18, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet 
>>> wrote:
>>>

 Le 05/11/2019 à 21:50, Roy Golan a écrit :



 On Tue, 5 Nov 2019 at 22:46, Roy Golan  wrote:

>
>
> On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet 
> wrote:
>
>>
>> Le 05/11/2019 à 18:22, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet 
>> wrote:
>>
>>>
>>> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet 
>>> wrote:
>>>
 I tried openshift-install after compiling but no ovirt provider is
 available... So waht do you mean when you say "give a try"? Maybe only
 provisionning ovirt with the terraform module?

 [root@vm5 installer]# bin/openshift-install create cluster
 ? Platform  [Use arrows to move, space to select, type to filter, ?
 for more help]
 > aws
   azure
   gcp
   openstack



>>> Its not merged yet. Please pull this image and work with it as a
>>> container
>>> quay.io/rgolangh/openshift-installer
>>>
>>> A little feedback as you asked:
>>>
>>> [root@openshift-installer ~]# docker run -it 56e5b667100f create
>>> cluster
>>> ? Platform ovirt
>>> ? Enter oVirt's api endpoint URL
>>> https://air-dev.v100.abes.fr/ovirt-engine/api
>>> ? Enter ovirt-engine username admin@internal
>>> ? Enter password **
>>> ? Pick the oVirt cluster Default
>>> ? Pick a VM template centos7.x
>>> ? Enter the internal API Virtual IP 10.34.212.200
>>> ? Enter the internal DNS Virtual IP 10.34.212.100
>>> ? Enter the ingress IP  10.34.212.50
>>> ? Base Domain oc4.localdomain
>>> ? Cluster Name test
>>> ? Pull Secret [? for help] *
>>> INFO Creating infrastructure resources...
>>> INFO Waiting up to 30m0s for the Kubernetes API at
>>> https://api.test.oc4.localdomain:6443...
>>> ERROR Attempted to gather ClusterOperator status after installation
>>> failure: listing ClusterOperator objects: Get
>>> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
>>> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no
>>> such host
>>> INFO Pulling debug logs from the bootstrap machine
>>> ERROR Attempted to gather debug logs after installation failure:
>>> failed to create SSH client, ensure the proper ssh key is in your 
>>> keyring
>>> or specify with --key: failed to initialize the SSH agent: failed to 
>>> read
>>> directory "/output/.ssh": open /output/.ssh: no such file or directory
>>> FATAL Bootstrap failed to complete: waiting for Kubernetes API:
>>> context deadline exceeded
>>>
>>>- 6 vms are successfully created thin dependent from the template
>>>
>>>
>>>- each vm is provisionned by cloud-init
>>>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>>>https://api.test.oc4.localdomain:6443..."; fails. It seems that
>>>the DNS pod is not up at this time.
>>>- Right this moment, there is no more visibility on what is
>>>done, what goes wrong... what's happening there? supposing a kind of
>>>playbook downloading a kind of images...
>>>- The" pull secret step" is not clear: we must have a redhat
>>>account to https://cloud.redhat.com/openshift/install/ to get a
>>>key like
>>>-
>>>{"auths":{"cloud.openshift.com
>>>
>>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>>"expl...@abes.fr" },"quay.io
>>>
>>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>>"expl...@abes.fr" },"registry.connect.redhat.com
>>>
>>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>>"expl...@abes.fr" },"registry.redhat.io
>>>
>>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>>"expl...@abes.fr" }}}
>>>
>

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 7 Nov 2019 at 12:28, Nathanaël Blanchet  wrote:

>
> Le 07/11/2019 à 11:16, Roy Golan a écrit :
>
>
>
> On Thu, 7 Nov 2019 at 11:23, Nathanaël Blanchet  wrote:
>
>>
>> Le 07/11/2019 à 07:18, Roy Golan a écrit :
>>
>>
>>
>> On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet  wrote:
>>
>>>
>>> Le 05/11/2019 à 21:50, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 22:46, Roy Golan  wrote:
>>>


 On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet 
 wrote:

>
> Le 05/11/2019 à 18:22, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet 
> wrote:
>
>>
>> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet 
>> wrote:
>>
>>> I tried openshift-install after compiling but no ovirt provider is
>>> available... So waht do you mean when you say "give a try"? Maybe only
>>> provisionning ovirt with the terraform module?
>>>
>>> [root@vm5 installer]# bin/openshift-install create cluster
>>> ? Platform  [Use arrows to move, space to select, type to filter, ?
>>> for more help]
>>> > aws
>>>   azure
>>>   gcp
>>>   openstack
>>>
>>>
>>>
>> Its not merged yet. Please pull this image and work with it as a
>> container
>> quay.io/rgolangh/openshift-installer
>>
>> A little feedback as you asked:
>>
>> [root@openshift-installer ~]# docker run -it 56e5b667100f create
>> cluster
>> ? Platform ovirt
>> ? Enter oVirt's api endpoint URL
>> https://air-dev.v100.abes.fr/ovirt-engine/api
>> ? Enter ovirt-engine username admin@internal
>> ? Enter password **
>> ? Pick the oVirt cluster Default
>> ? Pick a VM template centos7.x
>> ? Enter the internal API Virtual IP 10.34.212.200
>> ? Enter the internal DNS Virtual IP 10.34.212.100
>> ? Enter the ingress IP  10.34.212.50
>> ? Base Domain oc4.localdomain
>> ? Cluster Name test
>> ? Pull Secret [? for help] *
>> INFO Creating infrastructure resources...
>> INFO Waiting up to 30m0s for the Kubernetes API at
>> https://api.test.oc4.localdomain:6443...
>> ERROR Attempted to gather ClusterOperator status after installation
>> failure: listing ClusterOperator objects: Get
>> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
>> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no
>> such host
>> INFO Pulling debug logs from the bootstrap machine
>> ERROR Attempted to gather debug logs after installation failure:
>> failed to create SSH client, ensure the proper ssh key is in your keyring
>> or specify with --key: failed to initialize the SSH agent: failed to read
>> directory "/output/.ssh": open /output/.ssh: no such file or directory
>> FATAL Bootstrap failed to complete: waiting for Kubernetes API:
>> context deadline exceeded
>>
>>- 6 vms are successfully created thin dependent from the template
>>
>>
>>- each vm is provisionned by cloud-init
>>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>>https://api.test.oc4.localdomain:6443..."; fails. It seems that
>>the DNS pod is not up at this time.
>>- Right this moment, there is no more visibility on what is done,
>>what goes wrong... what's happening there? supposing a kind of 
>> playbook
>>downloading a kind of images...
>>- The" pull secret step" is not clear: we must have a redhat
>>account to https://cloud.redhat.com/openshift/install/ to get a
>>key like
>>-
>>{"auths":{"cloud.openshift.com
>>
>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>"expl...@abes.fr" },"quay.io
>>
>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>"expl...@abes.fr" },"registry.connect.redhat.com
>>
>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>"expl...@abes.fr" },"registry.redhat.io
>>
>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>"expl...@abes.fr" }}}
>>
>>
>> Can you tell me if I'm doing wrong?
>>
>
> What is the template you are using? I don't think its RHCOS(Red Hat
> CoreOs) template, it looks like Centos?
>
> Use

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 07/11/2019 à 11:16, Roy Golan a écrit :



On Thu, 7 Nov 2019 at 11:23, Nathanaël Blanchet > wrote:



Le 07/11/2019 à 07:18, Roy Golan a écrit :



On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 21:50, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 22:46, Roy Golan mailto:rgo...@redhat.com>> wrote:



On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 18:22, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 13:54, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 14:52, Nathanaël
Blanchet mailto:blanc...@abes.fr>> wrote:

I tried openshift-install after compiling
but no ovirt provider is available... So
waht do you mean when you say "give a
try"? Maybe only provisionning ovirt with
the terraform module?

[root@vm5 installer]#
bin/openshift-install create cluster
? Platform [Use arrows to move, space to
select, type to filter, ? for more help]
> aws
  azure
  gcp
  openstack


Its not merged yet. Please pull this image and
work with it as a container
quay.io/rgolangh/openshift-installer



A little feedback as you asked:

[root@openshift-installer ~]# docker run -it
56e5b667100f create cluster
? Platform ovirt
? Enter oVirt's api endpoint URL
https://air-dev.v100.abes.fr/ovirt-engine/api
? Enter ovirt-engine username admin@internal
? Enter password **
? Pick the oVirt cluster Default
? Pick a VM template centos7.x
? Enter the internal API Virtual IP 10.34.212.200
? Enter the internal DNS Virtual IP 10.34.212.100
? Enter the ingress IP  10.34.212.50
? Base Domain oc4.localdomain
? Cluster Name test
? Pull Secret [? for help]
*
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API
at https://api.test.oc4.localdomain:6443...
ERROR Attempted to gather ClusterOperator
status after installation failure: listing
ClusterOperator objects: Get

https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
dial tcp: lookup api.test.oc4.localdomain on
10.34.212.100:53 : no
such host
INFO Pulling debug logs from the bootstrap machine
ERROR Attempted to gather debug logs after
installation failure: failed to create SSH
client, ensure the proper ssh key is in your
keyring or specify with --key: failed to
initialize the SSH agent: failed to read
directory "/output/.ssh": open /output/.ssh: no
such file or directory
FATAL Bootstrap failed to complete: waiting for
Kubernetes API: context deadline exceeded

  * 6 vms are successfully created thin
dependent from the template

  * each vm is provisionned by cloud-init
  * the step "INFO Waiting up to 30m0s for the
Kubernetes API at
https://api.test.oc4.localdomain:6443...";
fails. It seems that the DNS pod is not up
at this time.
  * Right this moment, there is no more
visibility on what is done, what goes
wrong... what's happening there? supposing
a kind of playbook downloading a kind of
images...
  * The" pull secret step" is not clear: we
must have a redhat account to
https://cloud.redhat.com/openshift/install/
to get a key like
 *

  

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 7 Nov 2019 at 11:23, Nathanaël Blanchet  wrote:

>
> Le 07/11/2019 à 07:18, Roy Golan a écrit :
>
>
>
> On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet  wrote:
>
>>
>> Le 05/11/2019 à 21:50, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 22:46, Roy Golan  wrote:
>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet 
>>> wrote:
>>>

 Le 05/11/2019 à 18:22, Roy Golan a écrit :



 On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet 
 wrote:

>
> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet 
> wrote:
>
>> I tried openshift-install after compiling but no ovirt provider is
>> available... So waht do you mean when you say "give a try"? Maybe only
>> provisionning ovirt with the terraform module?
>>
>> [root@vm5 installer]# bin/openshift-install create cluster
>> ? Platform  [Use arrows to move, space to select, type to filter, ?
>> for more help]
>> > aws
>>   azure
>>   gcp
>>   openstack
>>
>>
>>
> Its not merged yet. Please pull this image and work with it as a
> container
> quay.io/rgolangh/openshift-installer
>
> A little feedback as you asked:
>
> [root@openshift-installer ~]# docker run -it 56e5b667100f create
> cluster
> ? Platform ovirt
> ? Enter oVirt's api endpoint URL
> https://air-dev.v100.abes.fr/ovirt-engine/api
> ? Enter ovirt-engine username admin@internal
> ? Enter password **
> ? Pick the oVirt cluster Default
> ? Pick a VM template centos7.x
> ? Enter the internal API Virtual IP 10.34.212.200
> ? Enter the internal DNS Virtual IP 10.34.212.100
> ? Enter the ingress IP  10.34.212.50
> ? Base Domain oc4.localdomain
> ? Cluster Name test
> ? Pull Secret [? for help] *
> INFO Creating infrastructure resources...
> INFO Waiting up to 30m0s for the Kubernetes API at
> https://api.test.oc4.localdomain:6443...
> ERROR Attempted to gather ClusterOperator status after installation
> failure: listing ClusterOperator objects: Get
> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no
> such host
> INFO Pulling debug logs from the bootstrap machine
> ERROR Attempted to gather debug logs after installation failure:
> failed to create SSH client, ensure the proper ssh key is in your keyring
> or specify with --key: failed to initialize the SSH agent: failed to read
> directory "/output/.ssh": open /output/.ssh: no such file or directory
> FATAL Bootstrap failed to complete: waiting for Kubernetes API:
> context deadline exceeded
>
>- 6 vms are successfully created thin dependent from the template
>
>
>- each vm is provisionned by cloud-init
>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>https://api.test.oc4.localdomain:6443..."; fails. It seems that the
>DNS pod is not up at this time.
>- Right this moment, there is no more visibility on what is done,
>what goes wrong... what's happening there? supposing a kind of playbook
>downloading a kind of images...
>- The" pull secret step" is not clear: we must have a redhat
>account to https://cloud.redhat.com/openshift/install/ to get a
>key like
>-
>{"auths":{"cloud.openshift.com
>
> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>"expl...@abes.fr" },"quay.io
>
> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>"expl...@abes.fr" },"registry.connect.redhat.com
>
> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>"expl...@abes.fr" },"registry.redhat.io
>
> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>"expl...@abes.fr" }}}
>
>
> Can you tell me if I'm doing wrong?
>

 What is the template you are using? I don't think its RHCOS(Red Hat
 CoreOs) template, it looks like Centos?

 Use this gist to import the template
 https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b

 Unfortunately, the result is the same with the RHCOS template...

>>>
>>> Make sure that:
>>> - the IPs supplied are taken, 

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 07/11/2019 à 07:18, Roy Golan a écrit :



On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet > wrote:



Le 05/11/2019 à 21:50, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 22:46, Roy Golan mailto:rgo...@redhat.com>> wrote:



On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 18:22, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 13:54, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

I tried openshift-install after compiling but
no ovirt provider is available... So waht do
you mean when you say "give a try"? Maybe only
provisionning ovirt with the terraform module?

[root@vm5 installer]# bin/openshift-install
create cluster
? Platform  [Use arrows to move, space to
select, type to filter, ? for more help]
> aws
  azure
  gcp
  openstack


Its not merged yet. Please pull this image and work
with it as a container
quay.io/rgolangh/openshift-installer



A little feedback as you asked:

[root@openshift-installer ~]# docker run -it
56e5b667100f create cluster
? Platform ovirt
? Enter oVirt's api endpoint URL
https://air-dev.v100.abes.fr/ovirt-engine/api
? Enter ovirt-engine username admin@internal
? Enter password **
? Pick the oVirt cluster Default
? Pick a VM template centos7.x
? Enter the internal API Virtual IP 10.34.212.200
? Enter the internal DNS Virtual IP 10.34.212.100
? Enter the ingress IP 10.34.212.50
? Base Domain oc4.localdomain
? Cluster Name test
? Pull Secret [? for help]
*
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at
https://api.test.oc4.localdomain:6443...
ERROR Attempted to gather ClusterOperator status
after installation failure: listing ClusterOperator
objects: Get

https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
dial tcp: lookup api.test.oc4.localdomain on
10.34.212.100:53 : no such
host
INFO Pulling debug logs from the bootstrap machine
ERROR Attempted to gather debug logs after
installation failure: failed to create SSH client,
ensure the proper ssh key is in your keyring or
specify with --key: failed to initialize the SSH
agent: failed to read directory "/output/.ssh": open
/output/.ssh: no such file or directory
FATAL Bootstrap failed to complete: waiting for
Kubernetes API: context deadline exceeded

  * 6 vms are successfully created thin dependent
from the template

  * each vm is provisionned by cloud-init
  * the step "INFO Waiting up to 30m0s for the
Kubernetes API at
https://api.test.oc4.localdomain:6443..."; fails.
It seems that the DNS pod is not up at this time.
  * Right this moment, there is no more visibility
on what is done, what goes wrong... what's
happening there? supposing a kind of playbook
downloading a kind of images...
  * The" pull secret step" is not clear: we must
have a redhat account to
https://cloud.redhat.com/openshift/install/ to
get a key like
 *

{"auths":{"cloud.openshift.com

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"
},"quay.io

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH***

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 7 Nov 2019 at 00:10, Nathanaël Blanchet  wrote:

>
> Le 05/11/2019 à 21:50, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 22:46, Roy Golan  wrote:
>
>>
>>
>> On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet  wrote:
>>
>>>
>>> Le 05/11/2019 à 18:22, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet 
>>> wrote:
>>>

 Le 05/11/2019 à 13:54, Roy Golan a écrit :



 On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet 
 wrote:

> I tried openshift-install after compiling but no ovirt provider is
> available... So waht do you mean when you say "give a try"? Maybe only
> provisionning ovirt with the terraform module?
>
> [root@vm5 installer]# bin/openshift-install create cluster
> ? Platform  [Use arrows to move, space to select, type to filter, ?
> for more help]
> > aws
>   azure
>   gcp
>   openstack
>
>
>
 Its not merged yet. Please pull this image and work with it as a
 container
 quay.io/rgolangh/openshift-installer

 A little feedback as you asked:

 [root@openshift-installer ~]# docker run -it 56e5b667100f create
 cluster
 ? Platform ovirt
 ? Enter oVirt's api endpoint URL
 https://air-dev.v100.abes.fr/ovirt-engine/api
 ? Enter ovirt-engine username admin@internal
 ? Enter password **
 ? Pick the oVirt cluster Default
 ? Pick a VM template centos7.x
 ? Enter the internal API Virtual IP 10.34.212.200
 ? Enter the internal DNS Virtual IP 10.34.212.100
 ? Enter the ingress IP  10.34.212.50
 ? Base Domain oc4.localdomain
 ? Cluster Name test
 ? Pull Secret [? for help] *
 INFO Creating infrastructure resources...
 INFO Waiting up to 30m0s for the Kubernetes API at
 https://api.test.oc4.localdomain:6443...
 ERROR Attempted to gather ClusterOperator status after installation
 failure: listing ClusterOperator objects: Get
 https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
 dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no such
 host
 INFO Pulling debug logs from the bootstrap machine
 ERROR Attempted to gather debug logs after installation failure: failed
 to create SSH client, ensure the proper ssh key is in your keyring or
 specify with --key: failed to initialize the SSH agent: failed to read
 directory "/output/.ssh": open /output/.ssh: no such file or directory
 FATAL Bootstrap failed to complete: waiting for Kubernetes API: context
 deadline exceeded

- 6 vms are successfully created thin dependent from the template


- each vm is provisionned by cloud-init
- the step "INFO Waiting up to 30m0s for the Kubernetes API at
https://api.test.oc4.localdomain:6443..."; fails. It seems that the
DNS pod is not up at this time.
- Right this moment, there is no more visibility on what is done,
what goes wrong... what's happening there? supposing a kind of playbook
downloading a kind of images...
- The" pull secret step" is not clear: we must have a redhat
account to https://cloud.redhat.com/openshift/install/ to get a key
like
-
{"auths":{"cloud.openshift.com

 ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
"expl...@abes.fr" },"quay.io

 ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
"expl...@abes.fr" },"registry.connect.redhat.com

 ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
"expl...@abes.fr" },"registry.redhat.io

 ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
"expl...@abes.fr" }}}


 Can you tell me if I'm doing wrong?

>>>
>>> What is the template you are using? I don't think its RHCOS(Red Hat
>>> CoreOs) template, it looks like Centos?
>>>
>>> Use this gist to import the template
>>> https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b
>>>
>>> Unfortunately, the result is the same with the RHCOS template...
>>>
>>
>> Make sure that:
>> - the IPs supplied are taken, and belong to the VM network of those
>> master VMs
>> - localdomain or local domain suffix shouldn't be used
>> - your ovirt-engine is version 4.3.7 or master
>>
>> I didn't mention that you can provide any domain name, even non-existing

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 05/11/2019 à 21:50, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 22:46, Roy Golan > wrote:




On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 18:22, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:


Le 05/11/2019 à 13:54, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

I tried openshift-install after compiling but no
ovirt provider is available... So waht do you mean
when you say "give a try"? Maybe only provisionning
ovirt with the terraform module?

[root@vm5 installer]# bin/openshift-install create
cluster
? Platform  [Use arrows to move, space to select,
type to filter, ? for more help]
> aws
  azure
  gcp
  openstack


Its not merged yet. Please pull this image and work with
it as a container
quay.io/rgolangh/openshift-installer



A little feedback as you asked:

[root@openshift-installer ~]# docker run -it 56e5b667100f
create cluster
? Platform ovirt
? Enter oVirt's api endpoint URL
https://air-dev.v100.abes.fr/ovirt-engine/api
? Enter ovirt-engine username admin@internal
? Enter password **
? Pick the oVirt cluster Default
? Pick a VM template centos7.x
? Enter the internal API Virtual IP 10.34.212.200
? Enter the internal DNS Virtual IP 10.34.212.100
? Enter the ingress IP  10.34.212.50
? Base Domain oc4.localdomain
? Cluster Name test
? Pull Secret [? for help]
*
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at
https://api.test.oc4.localdomain:6443...
ERROR Attempted to gather ClusterOperator status after
installation failure: listing ClusterOperator objects:
Get

https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
dial tcp: lookup api.test.oc4.localdomain on
10.34.212.100:53 : no such host
INFO Pulling debug logs from the bootstrap machine
ERROR Attempted to gather debug logs after installation
failure: failed to create SSH client, ensure the proper
ssh key is in your keyring or specify with --key: failed
to initialize the SSH agent: failed to read directory
"/output/.ssh": open /output/.ssh: no such file or directory
FATAL Bootstrap failed to complete: waiting for
Kubernetes API: context deadline exceeded

  * 6 vms are successfully created thin dependent from
the template

  * each vm is provisionned by cloud-init
  * the step "INFO Waiting up to 30m0s for the Kubernetes
API at https://api.test.oc4.localdomain:6443...";
fails. It seems that the DNS pod is not up at this time.
  * Right this moment, there is no more visibility on
what is done, what goes wrong... what's happening
there? supposing a kind of playbook downloading a
kind of images...
  * The" pull secret step" is not clear: we must have a
redhat account to
https://cloud.redhat.com/openshift/install/ to get a
key like
 *

{"auths":{"cloud.openshift.com

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"
},"quay.io

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"
},"registry.connect.redhat.com

":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":"expl...@abes.fr"
},"registry.redhat.io

":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZ

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 22:46, Roy Golan  wrote:

>
>
> On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet  wrote:
>
>>
>> Le 05/11/2019 à 18:22, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet  wrote:
>>
>>>
>>> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet 
>>> wrote:
>>>
 I tried openshift-install after compiling but no ovirt provider is
 available... So waht do you mean when you say "give a try"? Maybe only
 provisionning ovirt with the terraform module?

 [root@vm5 installer]# bin/openshift-install create cluster
 ? Platform  [Use arrows to move, space to select, type to filter, ? for
 more help]
 > aws
   azure
   gcp
   openstack



>>> Its not merged yet. Please pull this image and work with it as a
>>> container
>>> quay.io/rgolangh/openshift-installer
>>>
>>> A little feedback as you asked:
>>>
>>> [root@openshift-installer ~]# docker run -it 56e5b667100f create cluster
>>> ? Platform ovirt
>>> ? Enter oVirt's api endpoint URL
>>> https://air-dev.v100.abes.fr/ovirt-engine/api
>>> ? Enter ovirt-engine username admin@internal
>>> ? Enter password **
>>> ? Pick the oVirt cluster Default
>>> ? Pick a VM template centos7.x
>>> ? Enter the internal API Virtual IP 10.34.212.200
>>> ? Enter the internal DNS Virtual IP 10.34.212.100
>>> ? Enter the ingress IP  10.34.212.50
>>> ? Base Domain oc4.localdomain
>>> ? Cluster Name test
>>> ? Pull Secret [? for help] *
>>> INFO Creating infrastructure resources...
>>> INFO Waiting up to 30m0s for the Kubernetes API at
>>> https://api.test.oc4.localdomain:6443...
>>> ERROR Attempted to gather ClusterOperator status after installation
>>> failure: listing ClusterOperator objects: Get
>>> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
>>> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no such
>>> host
>>> INFO Pulling debug logs from the bootstrap machine
>>> ERROR Attempted to gather debug logs after installation failure: failed
>>> to create SSH client, ensure the proper ssh key is in your keyring or
>>> specify with --key: failed to initialize the SSH agent: failed to read
>>> directory "/output/.ssh": open /output/.ssh: no such file or directory
>>> FATAL Bootstrap failed to complete: waiting for Kubernetes API: context
>>> deadline exceeded
>>>
>>>- 6 vms are successfully created thin dependent from the template
>>>
>>>
>>>- each vm is provisionned by cloud-init
>>>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>>>https://api.test.oc4.localdomain:6443..."; fails. It seems that the
>>>DNS pod is not up at this time.
>>>- Right this moment, there is no more visibility on what is done,
>>>what goes wrong... what's happening there? supposing a kind of playbook
>>>downloading a kind of images...
>>>- The" pull secret step" is not clear: we must have a redhat account
>>>to https://cloud.redhat.com/openshift/install/ to get a key like
>>>-
>>>{"auths":{"cloud.openshift.com
>>>
>>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>>"expl...@abes.fr" },"quay.io
>>>
>>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>>"expl...@abes.fr" },"registry.connect.redhat.com
>>>
>>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>>"expl...@abes.fr" },"registry.redhat.io
>>>
>>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>>"expl...@abes.fr" }}}
>>>
>>>
>>> Can you tell me if I'm doing wrong?
>>>
>>
>> What is the template you are using? I don't think its RHCOS(Red Hat
>> CoreOs) template, it looks like Centos?
>>
>> Use this gist to import the template
>> https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b
>>
>> Unfortunately, the result is the same with the RHCOS template...
>>
>
> Make sure that:
> - the IPs supplied are taken, and belong to the VM network of those master
> VMs
> - localdomain or local domain suffix shouldn't be used
> - your ovirt-engine is version 4.3.7 or master
>
> I didn't mention that you can provide any domain name, even non-existing.
When the bootstrap phase will be done, the instllation will teardown the
bootsrap mahchine.
At this stage if you are using a non-existing domain you would need to add
the DNS Virtual IP
you provided to your resolv.conf so the installation could

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 20:28, Nathanaël Blanchet  wrote:

>
> Le 05/11/2019 à 18:22, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet  wrote:
>
>>
>> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet  wrote:
>>
>>> I tried openshift-install after compiling but no ovirt provider is
>>> available... So waht do you mean when you say "give a try"? Maybe only
>>> provisionning ovirt with the terraform module?
>>>
>>> [root@vm5 installer]# bin/openshift-install create cluster
>>> ? Platform  [Use arrows to move, space to select, type to filter, ? for
>>> more help]
>>> > aws
>>>   azure
>>>   gcp
>>>   openstack
>>>
>>>
>>>
>> Its not merged yet. Please pull this image and work with it as a container
>> quay.io/rgolangh/openshift-installer
>>
>> A little feedback as you asked:
>>
>> [root@openshift-installer ~]# docker run -it 56e5b667100f create cluster
>> ? Platform ovirt
>> ? Enter oVirt's api endpoint URL
>> https://air-dev.v100.abes.fr/ovirt-engine/api
>> ? Enter ovirt-engine username admin@internal
>> ? Enter password **
>> ? Pick the oVirt cluster Default
>> ? Pick a VM template centos7.x
>> ? Enter the internal API Virtual IP 10.34.212.200
>> ? Enter the internal DNS Virtual IP 10.34.212.100
>> ? Enter the ingress IP  10.34.212.50
>> ? Base Domain oc4.localdomain
>> ? Cluster Name test
>> ? Pull Secret [? for help] *
>> INFO Creating infrastructure resources...
>> INFO Waiting up to 30m0s for the Kubernetes API at
>> https://api.test.oc4.localdomain:6443...
>> ERROR Attempted to gather ClusterOperator status after installation
>> failure: listing ClusterOperator objects: Get
>> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
>> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no such
>> host
>> INFO Pulling debug logs from the bootstrap machine
>> ERROR Attempted to gather debug logs after installation failure: failed
>> to create SSH client, ensure the proper ssh key is in your keyring or
>> specify with --key: failed to initialize the SSH agent: failed to read
>> directory "/output/.ssh": open /output/.ssh: no such file or directory
>> FATAL Bootstrap failed to complete: waiting for Kubernetes API: context
>> deadline exceeded
>>
>>- 6 vms are successfully created thin dependent from the template
>>
>>
>>- each vm is provisionned by cloud-init
>>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>>https://api.test.oc4.localdomain:6443..."; fails. It seems that the
>>DNS pod is not up at this time.
>>- Right this moment, there is no more visibility on what is done,
>>what goes wrong... what's happening there? supposing a kind of playbook
>>downloading a kind of images...
>>- The" pull secret step" is not clear: we must have a redhat account
>>to https://cloud.redhat.com/openshift/install/ to get a key like
>>-
>>{"auths":{"cloud.openshift.com
>>
>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>"expl...@abes.fr" },"quay.io
>>
>> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>>"expl...@abes.fr" },"registry.connect.redhat.com
>>
>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>"expl...@abes.fr" },"registry.redhat.io
>>
>> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>>"expl...@abes.fr" }}}
>>
>>
>> Can you tell me if I'm doing wrong?
>>
>
> What is the template you are using? I don't think its RHCOS(Red Hat
> CoreOs) template, it looks like Centos?
>
> Use this gist to import the template
> https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b
>
> Unfortunately, the result is the same with the RHCOS template...
>

Make sure that:
- the IPs supplied are taken, and belong to the VM network of those master
VMs
- localdomain or local domain suffix shouldn't be used
- your ovirt-engine is version 4.3.7 or master



>
>
> Le 05/11/2019 à 12:24, Roy Golan a écrit :
>>>
>>>
>>>
>>> On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet 
>>> wrote:
>>>
 Hello,

 I'm interested by installing okd on ovirt with the official openshift
 installer (https://github.com/openshift/installer), but ovirt is not
 yet
 supported.


>>> If you want to give a try and supply feedback I'll be glad.
>>>
>>>
 Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and

 https://list

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 05/11/2019 à 18:22, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet > wrote:



Le 05/11/2019 à 13:54, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:

I tried openshift-install after compiling but no ovirt
provider is available... So waht do you mean when you say
"give a try"? Maybe only provisionning ovirt with the
terraform module?

[root@vm5 installer]# bin/openshift-install create cluster
? Platform  [Use arrows to move, space to select, type to
filter, ? for more help]
> aws
  azure
  gcp
  openstack


Its not merged yet. Please pull this image and work with it as a
container
quay.io/rgolangh/openshift-installer



A little feedback as you asked:

[root@openshift-installer ~]# docker run -it 56e5b667100f create
cluster
? Platform ovirt
? Enter oVirt's api endpoint URL
https://air-dev.v100.abes.fr/ovirt-engine/api
? Enter ovirt-engine username admin@internal
? Enter password **
? Pick the oVirt cluster Default
? Pick a VM template centos7.x
? Enter the internal API Virtual IP 10.34.212.200
? Enter the internal DNS Virtual IP 10.34.212.100
? Enter the ingress IP  10.34.212.50
? Base Domain oc4.localdomain
? Cluster Name test
? Pull Secret [? for help] *
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at
https://api.test.oc4.localdomain:6443...
ERROR Attempted to gather ClusterOperator status after
installation failure: listing ClusterOperator objects: Get

https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53
: no such host
INFO Pulling debug logs from the bootstrap machine
ERROR Attempted to gather debug logs after installation failure:
failed to create SSH client, ensure the proper ssh key is in your
keyring or specify with --key: failed to initialize the SSH agent:
failed to read directory "/output/.ssh": open /output/.ssh: no
such file or directory
FATAL Bootstrap failed to complete: waiting for Kubernetes API:
context deadline exceeded

  * 6 vms are successfully created thin dependent from the template

  * each vm is provisionned by cloud-init
  * the step "INFO Waiting up to 30m0s for the Kubernetes API at
https://api.test.oc4.localdomain:6443..."; fails. It seems that
the DNS pod is not up at this time.
  * Right this moment, there is no more visibility on what is
done, what goes wrong... what's happening there? supposing a
kind of playbook downloading a kind of images...
  * The" pull secret step" is not clear: we must have a redhat
account to https://cloud.redhat.com/openshift/install/ to get
a key like
 *

{"auths":{"cloud.openshift.com

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"
},"quay.io

":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"
},"registry.connect.redhat.com

":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":"expl...@abes.fr"
},"registry.redhat.io

":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":"expl...@abes.fr"
}}}

Can you tell me if I'm doing wrong?


What is the template you are using? I don't think its RHCOS(Red Hat 
CoreOs) template, it looks like Centos?


Use this gist to import the template 
https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b

Unfortunately, the result is the same with the RHCOS template...





Le 05/11/2019 à 12:24, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

Hello,

I'm interested by installing okd on ovirt with the
official openshift
installer (https://github.com/openshift/installer), but
ovirt is not ye

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 19:12, Nathanaël Blanchet  wrote:

>
> Le 05/11/2019 à 13:54, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet  wrote:
>
>> I tried openshift-install after compiling but no ovirt provider is
>> available... So waht do you mean when you say "give a try"? Maybe only
>> provisionning ovirt with the terraform module?
>>
>> [root@vm5 installer]# bin/openshift-install create cluster
>> ? Platform  [Use arrows to move, space to select, type to filter, ? for
>> more help]
>> > aws
>>   azure
>>   gcp
>>   openstack
>>
>>
>>
> Its not merged yet. Please pull this image and work with it as a container
> quay.io/rgolangh/openshift-installer
>
> A little feedback as you asked:
>
> [root@openshift-installer ~]# docker run -it 56e5b667100f create cluster
> ? Platform ovirt
> ? Enter oVirt's api endpoint URL
> https://air-dev.v100.abes.fr/ovirt-engine/api
> ? Enter ovirt-engine username admin@internal
> ? Enter password **
> ? Pick the oVirt cluster Default
> ? Pick a VM template centos7.x
> ? Enter the internal API Virtual IP 10.34.212.200
> ? Enter the internal DNS Virtual IP 10.34.212.100
> ? Enter the ingress IP  10.34.212.50
> ? Base Domain oc4.localdomain
> ? Cluster Name test
> ? Pull Secret [? for help] *
> INFO Creating infrastructure resources...
> INFO Waiting up to 30m0s for the Kubernetes API at
> https://api.test.oc4.localdomain:6443...
> ERROR Attempted to gather ClusterOperator status after installation
> failure: listing ClusterOperator objects: Get
> https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators:
> dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no such
> host
> INFO Pulling debug logs from the bootstrap machine
> ERROR Attempted to gather debug logs after installation failure: failed to
> create SSH client, ensure the proper ssh key is in your keyring or specify
> with --key: failed to initialize the SSH agent: failed to read directory
> "/output/.ssh": open /output/.ssh: no such file or directory
> FATAL Bootstrap failed to complete: waiting for Kubernetes API: context
> deadline exceeded
>
>- 6 vms are successfully created thin dependent from the template
>
>
>- each vm is provisionned by cloud-init
>- the step "INFO Waiting up to 30m0s for the Kubernetes API at
>https://api.test.oc4.localdomain:6443..."; fails. It seems that the DNS
>pod is not up at this time.
>- Right this moment, there is no more visibility on what is done, what
>goes wrong... what's happening there? supposing a kind of playbook
>downloading a kind of images...
>- The" pull secret step" is not clear: we must have a redhat account
>to https://cloud.redhat.com/openshift/install/ to get a key like
>-
>{"auths":{"cloud.openshift.com
>
> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>"expl...@abes.fr" },"quay.io
>
> ":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":
>"expl...@abes.fr" },"registry.connect.redhat.com
>
> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>"expl...@abes.fr" },"registry.redhat.io
>
> ":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":
>"expl...@abes.fr" }}}
>
>
> Can you tell me if I'm doing wrong?
>

What is the template you are using? I don't think its RHCOS(Red Hat CoreOs)
template, it looks like Centos?

Use this gist to import the template
https://gist.github.com/rgolangh/adccf6d6b5eaecaebe0b0aeba9d3331b



Le 05/11/2019 à 12:24, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet  wrote:
>>
>>> Hello,
>>>
>>> I'm interested by installing okd on ovirt with the official openshift
>>> installer (https://github.com/openshift/installer), but ovirt is not
>>> yet
>>> supported.
>>>
>>>
>> If you want to give a try and supply feedback I'll be glad.
>>
>>
>>> Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
>>>
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/
>>> , how ovirt 4.3.7 should integrate openshift installer integration with
>>> terraform?
>>>
>>>
>> Terraform is part of it, yes, It is what we use to spin the first 3
>> masters, plus a bootstraping machine.
>>
>> --
>>> Nathanaël Blanchet
>>>
>>> Supervision réseau
>>> Pôle Infrastrutures Informatiques
>>> 227 avenue Professeur-Jean-Louis-Viala
>>> 34193 MONTPELLIER CEDEX 5
>>> Tél. 33 (0)4 67 54 84 55
>>> Fax  33 (0

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 05/11/2019 à 13:54, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet > wrote:


I tried openshift-install after compiling but no ovirt provider is
available... So waht do you mean when you say "give a try"? Maybe
only provisionning ovirt with the terraform module?

[root@vm5 installer]# bin/openshift-install create cluster
? Platform  [Use arrows to move, space to select, type to filter,
? for more help]
> aws
  azure
  gcp
  openstack


Its not merged yet. Please pull this image and work with it as a container
quay.io/rgolangh/openshift-installer 



A little feedback as you asked:

[root@openshift-installer ~]# docker run -it 56e5b667100f create cluster
? Platform ovirt
? Enter oVirt's api endpoint URL 
https://air-dev.v100.abes.fr/ovirt-engine/api

? Enter ovirt-engine username admin@internal
? Enter password **
? Pick the oVirt cluster Default
? Pick a VM template centos7.x
? Enter the internal API Virtual IP 10.34.212.200
? Enter the internal DNS Virtual IP 10.34.212.100
? Enter the ingress IP  10.34.212.50
? Base Domain oc4.localdomain
? Cluster Name test
? Pull Secret [? for help] *
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at 
https://api.test.oc4.localdomain:6443...
ERROR Attempted to gather ClusterOperator status after installation 
failure: listing ClusterOperator objects: Get 
https://api.test.oc4.localdomain:6443/apis/config.openshift.io/v1/clusteroperators: 
dial tcp: lookup api.test.oc4.localdomain on 10.34.212.100:53: no such host

INFO Pulling debug logs from the bootstrap machine
ERROR Attempted to gather debug logs after installation failure: failed 
to create SSH client, ensure the proper ssh key is in your keyring or 
specify with --key: failed to initialize the SSH agent: failed to read 
directory "/output/.ssh": open /output/.ssh: no such file or directory
FATAL Bootstrap failed to complete: waiting for Kubernetes API: context 
deadline exceeded


 * 6 vms are successfully created thin dependent from the template

 * each vm is provisionned by cloud-init
 * the step "INFO Waiting up to 30m0s for the Kubernetes API at
   https://api.test.oc4.localdomain:6443..."; fails. It seems that the
   DNS pod is not up at this time.
 * Right this moment, there is no more visibility on what is done, what
   goes wrong... what's happening there? supposing a kind of playbook
   downloading a kind of images...
 * The" pull secret step" is not clear: we must have a redhat account
   to https://cloud.redhat.com/openshift/install/ to get a key like
 *

   
{"auths":{"cloud.openshift.com":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"},"quay.io":{"auth":"b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2V4cGxvaXRhYmVzZnIxdGN0ZnR0dmFnMHpuazMxd2IwMnIwenV1MDg6TE9XVzFQODM1NzNJWlI4MlZDSUEyTFdEVlJJS0U5VTVWM0NTSUdOWjJH==","email":"expl...@abes.fr"},"registry.connect.redhat.com":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":"expl...@abes.fr"},"registry.redhat.io":{"auth":"NTI0MjkwMnx1aGMtMVRDVEZUVFZBRzBaTkszMXdCMDJSMFp1VTA4OmV5SmhiR2NpT2lKU1V6VXhNaUo5LmV5SnpkV0lpT2lJMk4ySTJNREV3WXpObE1HSTBNbVE0T1RGbVpUZGxa**","email":"expl...@abes.fr"}}}

Can you tell me if I'm doing wrong?


Le 05/11/2019 à 12:24, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:

Hello,

I'm interested by installing okd on ovirt with the official
openshift
installer (https://github.com/openshift/installer), but ovirt
is not yet
supported.


If you want to give a try and supply feedback I'll be glad.

Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255
and

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/

, how ovirt 4.3.7 should integrate openshift installer
integration with
terraform?


Terraform is part of it, yes, It is what we use to spin the first
3 masters, plus a bootstraping machine.

-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr 

-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 14:50, Sandro Bonazzola  wrote:

>
>
> Il giorno mar 5 nov 2019 alle ore 12:24 Roy Golan  ha
> scritto:
>
>>
>>
>> On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet  wrote:
>>
>>> Hello,
>>>
>>> I'm interested by installing okd on ovirt with the official openshift
>>> installer (https://github.com/openshift/installer), but ovirt is not
>>> yet
>>> supported.
>>>
>>>
>> If you want to give a try and supply feedback I'll be glad.
>>
>
> +Gal Zaidman  +Evgeny Slutsky  +Roy
> Golan  +Douglas Landgraf  , maybe
> you can prepare a "quick setup guide" for this case on ovirt.org?
>
>
>
There is an install doc as part of the PR, lets keep work on single one -
if needs additions, let me know by direct feedback on the PR
https://github.com/openshift/installer/pull/1948/commits/1f1c4c2b4c9e1fff64c3e2570b3023708e708a56#diff-7ce61be732b65757aca7b9e384793ef4


>>
>>> Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
>>>
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/
>>> , how ovirt 4.3.7 should integrate openshift installer integration with
>>> terraform?
>>>
>>>
>> Terraform is part of it, yes, It is what we use to spin the first 3
>> masters, plus a bootstraping machine.
>>
>> --
>>> Nathanaël Blanchet
>>>
>>> Supervision réseau
>>> Pôle Infrastrutures Informatiques
>>> 227 avenue Professeur-Jean-Louis-Viala
>>> 34193 MONTPELLIER CEDEX 5
>>> Tél. 33 (0)4 67 54 84 55
>>> Fax  33 (0)4 67 54 84 14
>>> blanc...@abes.fr
>>>
>>>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *Red Hat respects your work life balance.
> Therefore there is no need to answer this email out of your office hours.
> *
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HHHMZIDW26PR62QVEVN5YHKHRZAMPSIL/

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 14:52, Nathanaël Blanchet  wrote:

> I tried openshift-install after compiling but no ovirt provider is
> available... So waht do you mean when you say "give a try"? Maybe only
> provisionning ovirt with the terraform module?
>
> [root@vm5 installer]# bin/openshift-install create cluster
> ? Platform  [Use arrows to move, space to select, type to filter, ? for
> more help]
> > aws
>   azure
>   gcp
>   openstack
>
>
>
Its not merged yet. Please pull this image and work with it as a container
quay.io/rgolangh/openshift-installer

> Le 05/11/2019 à 12:24, Roy Golan a écrit :
>
>
>
> On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet  wrote:
>
>> Hello,
>>
>> I'm interested by installing okd on ovirt with the official openshift
>> installer (https://github.com/openshift/installer), but ovirt is not yet
>> supported.
>>
>>
> If you want to give a try and supply feedback I'll be glad.
>
>
>> Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
>>
>> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/
>> , how ovirt 4.3.7 should integrate openshift installer integration with
>> terraform?
>>
>>
> Terraform is part of it, yes, It is what we use to spin the first 3
> masters, plus a bootstraping machine.
>
> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>>
>> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JDZJSZ4M4EGSCD6P426RXWNHRK3JXR5R/

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

I tried openshift-install after compiling but no ovirt provider is 
available... So waht do you mean when you say "give a try"? Maybe only 
provisionning ovirt with the terraform module?


[root@vm5 installer]# bin/openshift-install create cluster
? Platform  [Use arrows to move, space to select, type to filter, ? for 
more help]

> aws
  azure
  gcp
  openstack

Le 05/11/2019 à 12:24, Roy Golan a écrit :



On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet > wrote:


Hello,

I'm interested by installing okd on ovirt with the official openshift
installer (https://github.com/openshift/installer), but ovirt is
not yet
supported.


If you want to give a try and supply feedback I'll be glad.

Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/

, how ovirt 4.3.7 should integrate openshift installer integration
with
terraform?


Terraform is part of it, yes, It is what we use to spin the first 3 
masters, plus a bootstraping machine.


-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr 


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GEKVJ2Z3V72IOOBXBZO7WQM4AODUGRRE/

[ovirt-users] Re: terraform integration

[Sandro Bonazzola]

Il giorno mar 5 nov 2019 alle ore 12:24 Roy Golan  ha
scritto:

>
>
> On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet  wrote:
>
>> Hello,
>>
>> I'm interested by installing okd on ovirt with the official openshift
>> installer (https://github.com/openshift/installer), but ovirt is not yet
>> supported.
>>
>>
> If you want to give a try and supply feedback I'll be glad.
>

+Gal Zaidman  +Evgeny Slutsky  +Roy
Golan  +Douglas Landgraf  , maybe
you can prepare a "quick setup guide" for this case on ovirt.org?



>
>
>> Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
>>
>> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/
>> , how ovirt 4.3.7 should integrate openshift installer integration with
>> terraform?
>>
>>
> Terraform is part of it, yes, It is what we use to spin the first 3
> masters, plus a bootstraping machine.
>
> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>>
>>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DBJSPMHW2MXD4LG5AHI7ZFYHCMT4ZSYW/

[ovirt-users] Re: terraform integration

[Roy Golan]

On Tue, 5 Nov 2019 at 13:22, Nathanaël Blanchet  wrote:

> Hello,
>
> I'm interested by installing okd on ovirt with the official openshift
> installer (https://github.com/openshift/installer), but ovirt is not yet
> supported.
>
>
If you want to give a try and supply feedback I'll be glad.


> Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
>
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3A7NVQVUT7UCUYKK5CH/
> , how ovirt 4.3.7 should integrate openshift installer integration with
> terraform?
>
>
Terraform is part of it, yes, It is what we use to spin the first 3
masters, plus a bootstraping machine.

-- 
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N6JITIMSCPUZPSCQBOMSAQYTZR7E3KLI/