subject:"Re\: \[ovirt\-users\] Engine reports"

Re: [ovirt-users] Engine reports

2018-04-13 Thread Rich Megginson


On 04/13/2018 05:12 AM, Peter Hudec wrote:

thanks, problem was with the selinux. I applied the permission on the
/var/lib/elasticsearch once again.

Deployment is done ;)


Excellent



Right now mi browser is complaining about certificate on SSO.
When I try to reach https://kibana.
I'm redirected to SSO

https:// :8443/oauth/authorize?...

An error occurred during a connection to metrics.ovirt.cnc.sk:8443. You
have received an invalid certificate. Please contact the server
administrator or email correspondent and give them the following
information: Your certificate contains the same serial number as another
certificate issued by the certificate authority. Please get a new
certificate containing a unique serial number. Error code:
SEC_ERROR_REUSED_ISSUER_AND_SERIAL


Uh oh.  That looks like a bug. 
https://github.com/openshift/origin/pull/18713/commits/95e262011438642410959914c3db9868c57739ff
I thought that had been fixed in 3.9, but perhaps the origin 3.9 rpms do 
not yet contain this fix.





Peter

On 12/04/2018 19:47, Rich Megginson wrote:

sudo ls -alrtF -Z /var/lib/elasticsearch

oc logs logging-es-data-master-z6zbv4v2-2-deploy

oc describe pod logging-es-data-master-z6zbv4v2-2-deploy

sudo grep type=AVC /var/log/audit/audit.log | tail

On 04/12/2018 02:32 AM, Peter Hudec wrote:

back to this issue.

something went wrong ;( The status command got error. I'm not familiar
with openshift, so the log processing will took me a while.

[PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
Already on project "logging" on server
"https://metrics.ovirt.cnc.sk:8443;.
[PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
hostmount-anyuid \

    system:serviceaccount:logging:aggregated-logging-elasticsearch

scc "hostmount-anyuid" added to:
["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
logging dc -l component=es -o name )
No rollout is in progress (latest rollout #2 failed 3 days ago)
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
logging dc -l component=es -o name )
deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
[PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
logging dc -l component=es -o name )
Waiting for rollout to finish: 0 of 1 updated replicas are available...
error: replication controller "logging-es-data-master-z6zbv4v2-3" has
failed progressing


[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUS    RESTARTS
   AGE
logging-curator-1-c894f    1/1   Running
904    5d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
0  3d
logging-fluentd-x9vzs  1/1   Running
1  5d
logging-kibana-1-6bvvw 2/2   Running
2  5d
logging-mux-1-xxmdj    1/1   Running
1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
NAME    TYPE    CLUSTER-IP   EXTERNAL-IP
PORT(S) AGE
logging-es  ClusterIP   172.30.249.174   
9200/TCP    5d
logging-es-cluster  ClusterIP   172.30.114.201   
9300/TCP    5d
logging-es-prometheus   ClusterIP   172.30.203.113   
443/TCP 5d
logging-kibana  ClusterIP   172.30.29.192    
443/TCP 5d
logging-mux ClusterIP   172.30.170.158   192.168.16.17
24284/TCP   5d


On 07/04/2018 01:09, Rich Megginson wrote:

Great!

On 04/06/2018 04:43 PM, Peter Hudec wrote:

Ansible playbook finished OK. The next step after weekend.

  thanks
  Peter

On 06/04/2018 23:34, Rich Megginson wrote:

On 04/06/2018 03:08 PM, Peter Hudec wrote:

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM
package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible

I

Re: [ovirt-users] Engine reports

2018-04-13 Thread Peter Hudec

thanks, problem was with the selinux. I applied the permission on the
/var/lib/elasticsearch once again.

Deployment is done ;)

Right now mi browser is complaining about certificate on SSO.
When I try to reach https://kibana.
I'm redirected to SSO

https:// :8443/oauth/authorize?...

An error occurred during a connection to metrics.ovirt.cnc.sk:8443. You
have received an invalid certificate. Please contact the server
administrator or email correspondent and give them the following
information: Your certificate contains the same serial number as another
certificate issued by the certificate authority. Please get a new
certificate containing a unique serial number. Error code:
SEC_ERROR_REUSED_ISSUER_AND_SERIAL


Peter

On 12/04/2018 19:47, Rich Megginson wrote:
> sudo ls -alrtF -Z /var/lib/elasticsearch
> 
> oc logs logging-es-data-master-z6zbv4v2-2-deploy
> 
> oc describe pod logging-es-data-master-z6zbv4v2-2-deploy
> 
> sudo grep type=AVC /var/log/audit/audit.log | tail
> 
> On 04/12/2018 02:32 AM, Peter Hudec wrote:
>> back to this issue.
>>
>> something went wrong ;( The status command got error. I'm not familiar
>> with openshift, so the log processing will took me a while.
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
>> Already on project "logging" on server
>> "https://metrics.ovirt.cnc.sk:8443;.
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
>> hostmount-anyuid \
>>>    system:serviceaccount:logging:aggregated-logging-elasticsearch
>> scc "hostmount-anyuid" added to:
>> ["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
>> logging dc -l component=es -o name )
>> No rollout is in progress (latest rollout #2 failed 3 days ago)
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
>> logging dc -l component=es -o name )
>> deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
>> [PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
>> logging dc -l component=es -o name )
>> Waiting for rollout to finish: 0 of 1 updated replicas are available...
>> error: replication controller "logging-es-data-master-z6zbv4v2-3" has
>> failed progressing
>>
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
>> NAME   READY STATUS    RESTARTS
>>   AGE
>> logging-curator-1-c894f    1/1   Running  
>> 904    5d
>> logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error
>> 0  3d
>> logging-fluentd-x9vzs  1/1   Running  
>> 1  5d
>> logging-kibana-1-6bvvw 2/2   Running  
>> 2  5d
>> logging-mux-1-xxmdj    1/1   Running  
>> 1  5d
>> [PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
>> NAME    TYPE    CLUSTER-IP   EXTERNAL-IP
>> PORT(S) AGE
>> logging-es  ClusterIP   172.30.249.174   
>> 9200/TCP    5d
>> logging-es-cluster  ClusterIP   172.30.114.201   
>> 9300/TCP    5d
>> logging-es-prometheus   ClusterIP   172.30.203.113   
>> 443/TCP 5d
>> logging-kibana  ClusterIP   172.30.29.192    
>> 443/TCP 5d
>> logging-mux ClusterIP   172.30.170.158   192.168.16.17
>> 24284/TCP   5d
>>
>>
>> On 07/04/2018 01:09, Rich Megginson wrote:
>>> Great!
>>>
>>> On 04/06/2018 04:43 PM, Peter Hudec wrote:
 Ansible playbook finished OK. The next step after weekend.

  thanks
  Peter

 On 06/04/2018 23:34, Rich Megginson wrote:
> On 04/06/2018 03:08 PM, Peter Hudec wrote:
>> Hi,
>>
>> https://tools.apps.hudecof.net/paste/view/1d493d52
>>
>> The difference is
>> - I used latest ansible 2.5 from PIPY source, since the RPM
>> package do
>> not fit requirements
>> - I used GIT repo

Re: [ovirt-users] Engine reports

2018-04-12 Thread Rich Megginson


sudo ls -alrtF -Z /var/lib/elasticsearch

oc logs logging-es-data-master-z6zbv4v2-2-deploy

oc describe pod logging-es-data-master-z6zbv4v2-2-deploy

sudo grep type=AVC /var/log/audit/audit.log | tail

On 04/12/2018 02:32 AM, Peter Hudec wrote:

back to this issue.

something went wrong ;( The status command got error. I'm not familiar
with openshift, so the log processing will took me a while.

[PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
Already on project "logging" on server "https://metrics.ovirt.cnc.sk:8443;.
[PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
hostmount-anyuid \

   system:serviceaccount:logging:aggregated-logging-elasticsearch

scc "hostmount-anyuid" added to:
["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
logging dc -l component=es -o name )
No rollout is in progress (latest rollout #2 failed 3 days ago)
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
logging dc -l component=es -o name )
deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
[PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
logging dc -l component=es -o name )
Waiting for rollout to finish: 0 of 1 updated replicas are available...
error: replication controller "logging-es-data-master-z6zbv4v2-3" has
failed progressing


[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
  AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
  AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
  AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
NAMETYPECLUSTER-IP   EXTERNAL-IP
PORT(S) AGE
logging-es  ClusterIP   172.30.249.174   
9200/TCP5d
logging-es-cluster  ClusterIP   172.30.114.201   
9300/TCP5d
logging-es-prometheus   ClusterIP   172.30.203.113   
443/TCP 5d
logging-kibana  ClusterIP   172.30.29.192
443/TCP 5d
logging-mux ClusterIP   172.30.170.158   192.168.16.17
24284/TCP   5d


On 07/04/2018 01:09, Rich Megginson wrote:

Great!

On 04/06/2018 04:43 PM, Peter Hudec wrote:

Ansible playbook finished OK. The next step after weekend.

 thanks
     Peter

On 06/04/2018 23:34, Rich Megginson wrote:

On 04/06/2018 03:08 PM, Peter Hudec wrote:

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible

I recommend that you start over with the RPM based openshift-ansible,
which is what the instructions say, which is what I have tested

alternately - if you want to go the more experimental route, you could
enable the epel-testing yum repo - ansible-2.5 is in epel-testing which
I've been told by the openshift-ansible guys should work


  Peter

On 06/04/2018 20:23, Rich Megginson wrote:

I'm assuming you are running on a CentOS7 machine, recently updated to
the latest base packages. Please confirm.

Please provide the output of the following commands:

sudo yum repolist

sudo rpm -q ansible

sudo yum repoquery -i ansible

sudo rpm -q openshift-ansible

sudo yum repoquery -i openshift-ansible

sudo rpm -q origin

sudo yum repoquery -i origin

sudo cat
/usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py




sudo ls -alrtF /etc/origin/logging

Please confirm that you followed the steps listed in the link below,
including the use of the ansible inventory, vars.yaml.template, and
repo
files:

Re: [ovirt-users] Engine reports

2018-04-12 Thread Peter Hudec

back to this issue.

something went wrong ;( The status command got error. I'm not familiar
with openshift, so the log processing will took me a while.

[PROD] r...@dipostat01.cnc.sk: ~ # oc project logging
Already on project "logging" on server "https://metrics.ovirt.cnc.sk:8443;.
[PROD] r...@dipostat01.cnc.sk: ~ # oc adm policy add-scc-to-user
hostmount-anyuid \
>   system:serviceaccount:logging:aggregated-logging-elasticsearch
scc "hostmount-anyuid" added to:
["system:serviceaccount:logging:aggregated-logging-elasticsearch"]
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout cancel $( oc get -n
logging dc -l component=es -o name )
No rollout is in progress (latest rollout #2 failed 3 days ago)
[PROD] r...@dipostat01.cnc.sk: ~ # oc rollout latest $( oc get -n
logging dc -l component=es -o name )
deploymentconfig "logging-es-data-master-z6zbv4v2" rolled out
[PROD] r...@dipostat01.cnc.sk: ~ #  oc rollout status -w $( oc get -n
logging dc -l component=es -o name )
Waiting for rollout to finish: 0 of 1 updated replicas are available...
error: replication controller "logging-es-data-master-z6zbv4v2-3" has
failed progressing


[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
 AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
 AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get pods
NAME   READY STATUSRESTARTS
 AGE
logging-curator-1-c894f1/1   Running   9045d
logging-es-data-master-z6zbv4v2-2-deploy   0/1   Error 0  3d
logging-fluentd-x9vzs  1/1   Running   1  5d
logging-kibana-1-6bvvw 2/2   Running   2  5d
logging-mux-1-xxmdj1/1   Running   1  5d
[PROD] r...@dipostat01.cnc.sk: ~ # oc get svc
NAMETYPECLUSTER-IP   EXTERNAL-IP
PORT(S) AGE
logging-es  ClusterIP   172.30.249.174   
9200/TCP5d
logging-es-cluster  ClusterIP   172.30.114.201   
9300/TCP5d
logging-es-prometheus   ClusterIP   172.30.203.113   
443/TCP 5d
logging-kibana  ClusterIP   172.30.29.192
443/TCP 5d
logging-mux ClusterIP   172.30.170.158   192.168.16.17
24284/TCP   5d


On 07/04/2018 01:09, Rich Megginson wrote:
> Great!
> 
> On 04/06/2018 04:43 PM, Peter Hudec wrote:
>> Ansible playbook finished OK. The next step after weekend.
>>
>> thanks
>>     Peter
>>
>> On 06/04/2018 23:34, Rich Megginson wrote:
>>> On 04/06/2018 03:08 PM, Peter Hudec wrote:
 Hi,

 https://tools.apps.hudecof.net/paste/view/1d493d52

 The difference is
 - I used latest ansible 2.5 from PIPY source, since the RPM package do
 not fit requirements
 - I used GIT repo for openshift-ansible.

 I could start it over with the RPM based openshift-ansible
>>> I recommend that you start over with the RPM based openshift-ansible,
>>> which is what the instructions say, which is what I have tested
>>>
>>> alternately - if you want to go the more experimental route, you could
>>> enable the epel-testing yum repo - ansible-2.5 is in epel-testing which
>>> I've been told by the openshift-ansible guys should work
>>>
  Peter

 On 06/04/2018 20:23, Rich Megginson wrote:
> I'm assuming you are running on a CentOS7 machine, recently updated to
> the latest base packages. Please confirm.
>
> Please provide the output of the following commands:
>
> sudo yum repolist
>
> sudo rpm -q ansible
>
> sudo yum repoquery -i ansible
>
> sudo rpm -q openshift-ansible
>
> sudo yum repoquery -i openshift-ansible
>
> sudo rpm -q origin
>
> sudo yum repoquery -i origin
>
> sudo cat
> /usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py
>
>
>
>
> sudo ls -alrtF /etc/origin/logging
>
> Please confirm that you followed the steps listed in the link below,
> including the use of the ansible inventory, vars.yaml.template, and

Re: [ovirt-users] Engine reports

2018-04-06 Thread Rich Megginson


Great!

On 04/06/2018 04:43 PM, Peter Hudec wrote:

Ansible playbook finished OK. The next step after weekend.

thanks
Peter

On 06/04/2018 23:34, Rich Megginson wrote:

On 04/06/2018 03:08 PM, Peter Hudec wrote:

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible

I recommend that you start over with the RPM based openshift-ansible,
which is what the instructions say, which is what I have tested

alternately - if you want to go the more experimental route, you could
enable the epel-testing yum repo - ansible-2.5 is in epel-testing which
I've been told by the openshift-ansible guys should work


 Peter

On 06/04/2018 20:23, Rich Megginson wrote:

I'm assuming you are running on a CentOS7 machine, recently updated to
the latest base packages. Please confirm.

Please provide the output of the following commands:

sudo yum repolist

sudo rpm -q ansible

sudo yum repoquery -i ansible

sudo rpm -q openshift-ansible

sudo yum repoquery -i openshift-ansible

sudo rpm -q origin

sudo yum repoquery -i origin

sudo cat
/usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py



sudo ls -alrtF /etc/origin/logging

Please confirm that you followed the steps listed in the link below,
including the use of the ansible inventory, vars.yaml.template, and repo
files:
https://github.com/richm/Main/blob/7e663351dc371b7895564072c7656ebfda45068d/README-install.md



On 04/06/2018 03:19 AM, Peter Hudec wrote:

first issue is ansible version, could be solved by virtual env

FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
versions: 2.4.3.0 or newer

yum install -y python-virtualenv
virtualenv ansible
. ./ansible/bin/activate
pip install -U pip setuptolls
pip install -U pip setuptools
pip install ansible


Second issue is a little bit strange for me

2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:


     1. Hosts:    localhost
    Play: OpenShift Aggregated Logging
    Task: pulling down signing items from host
    Message:  ESC[0;31mAll items completedESC[0m

I have found in logs

2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
(item=ca.crl.srl) => {
   "changed": false,
   "invocation": {
   "module_args": {
   "src": "/etc/origin/logging/ca.crl.srl"
   }
   },
   "item": "ca.crl.srl",
   "msg": "file not found: /etc/origin/logging/ca.crl.srl"


Is this good or bad ?

  Peter

On 05/04/2018 16:11, Rich Megginson wrote:

Is it possible that you could start over from scratch, using the
latest
instructions/files at
https://github.com/ViaQ/Main/pull/37/files?

On 04/05/2018 07:19 AM, Peter Hudec wrote:

The version is from

/usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version




[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
/usr/bin/openshift version
openshift v3.10.0-alpha.0+f0186dd-401
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64
package

[PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
origin-3.7.2-1.el7.git.0.f0186dd.x86_64

Hmm, why the version do not match ?

   Peter

On 04/04/2018 17:41, Shirly Radco wrote:

Hi,


I have a updated the installation instructions for installing
OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of
OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md




It should be merged soon, but you can use it to install.


Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.


Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 


TRIED. TESTED. TRUSTED. 


On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson > wrote:

    I'm sorry.  I misunderstood the request.

    We are in the process of updating the instructions for
installing
    viaq logging based on upstream origin 3.9 -
    https://github.com/ViaQ/Main/pull/37
    

    In the meantime, you can follow along on that PR, and we will
have
    instructions very soon.


    On 04/04/2018 08:26 AM, Rich Megginson wrote:

    On 04/04/2018 08:22 AM, Shirly Radco wrote:



    --

    SHIRLY RADCO

    BI

Re: [ovirt-users] Engine reports

2018-04-06 Thread Peter Hudec

Ansible playbook finished OK. The next step after weekend.

thanks
Peter

On 06/04/2018 23:34, Rich Megginson wrote:
> On 04/06/2018 03:08 PM, Peter Hudec wrote:
>> Hi,
>>
>> https://tools.apps.hudecof.net/paste/view/1d493d52
>>
>> The difference is
>> - I used latest ansible 2.5 from PIPY source, since the RPM package do
>> not fit requirements
>> - I used GIT repo for openshift-ansible.
>>
>> I could start it over with the RPM based openshift-ansible
> 
> I recommend that you start over with the RPM based openshift-ansible,
> which is what the instructions say, which is what I have tested
> 
> alternately - if you want to go the more experimental route, you could
> enable the epel-testing yum repo - ansible-2.5 is in epel-testing which
> I've been told by the openshift-ansible guys should work
> 
>>
>> Peter
>>
>> On 06/04/2018 20:23, Rich Megginson wrote:
>>> I'm assuming you are running on a CentOS7 machine, recently updated to
>>> the latest base packages. Please confirm.
>>>
>>> Please provide the output of the following commands:
>>>
>>> sudo yum repolist
>>>
>>> sudo rpm -q ansible
>>>
>>> sudo yum repoquery -i ansible
>>>
>>> sudo rpm -q openshift-ansible
>>>
>>> sudo yum repoquery -i openshift-ansible
>>>
>>> sudo rpm -q origin
>>>
>>> sudo yum repoquery -i origin
>>>
>>> sudo cat
>>> /usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py
>>>
>>>
>>>
>>> sudo ls -alrtF /etc/origin/logging
>>>
>>> Please confirm that you followed the steps listed in the link below,
>>> including the use of the ansible inventory, vars.yaml.template, and repo
>>> files:
>>> https://github.com/richm/Main/blob/7e663351dc371b7895564072c7656ebfda45068d/README-install.md
>>>
>>>
>>>
>>> On 04/06/2018 03:19 AM, Peter Hudec wrote:
 first issue is ansible version, could be solved by virtual env

 FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
 versions: 2.4.3.0 or newer

 yum install -y python-virtualenv
 virtualenv ansible
 . ./ansible/bin/activate
 pip install -U pip setuptolls
 pip install -U pip setuptools
 pip install ansible


 Second issue is a little bit strange for me

 2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:


     1. Hosts:    localhost
    Play: OpenShift Aggregated Logging
    Task: pulling down signing items from host
    Message:  ESC[0;31mAll items completedESC[0m

 I have found in logs

 2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
 (item=ca.crl.srl) => {
   "changed": false,
   "invocation": {
   "module_args": {
   "src": "/etc/origin/logging/ca.crl.srl"
   }
   },
   "item": "ca.crl.srl",
   "msg": "file not found: /etc/origin/logging/ca.crl.srl"


 Is this good or bad ?

  Peter

 On 05/04/2018 16:11, Rich Megginson wrote:
> Is it possible that you could start over from scratch, using the
> latest
> instructions/files at
> https://github.com/ViaQ/Main/pull/37/files?
>
> On 04/05/2018 07:19 AM, Peter Hudec wrote:
>> The version is from
>>
>> /usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version
>>
>>
>>
>>
>> [PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
>> /usr/bin/openshift version
>> openshift v3.10.0-alpha.0+f0186dd-401
>> kubernetes v1.9.1+a0ce1bc657
>> etcd 3.2.16
>>
>> this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64
>> package
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
>> origin-3.7.2-1.el7.git.0.f0186dd.x86_64
>>
>> Hmm, why the version do not match ?
>>
>>   Peter
>>
>> On 04/04/2018 17:41, Shirly Radco wrote:
>>> Hi,
>>>
>>>
>>> I have a updated the installation instructions for installing
>>> OpenShift
>>> 3.9, based on Rich's work , for the oVirt use case.
>>>
>>> Please make sure where you get the 3.10 rpm and disable that repo.
>>>
>>> This is the PR that includes the metrics store installation of
>>> OpenShift 3.9
>>>
>>> https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md
>>>
>>>
>>>
>>>
>>> It should be merged soon, but you can use it to install.
>>>
>>>
>>> Please make sure to add the ansible-inventory-origin-39-aio file as
>>> described below.
>>> These are required parameters for the ansible playbook.
>>>
>>>
>>> Best regards,
>>>
>>> -- 
>>>
>>> SHIRLY RADCO
>>>
>>> BI SeNIOR SOFTWARE ENGINEER
>>>
>>> Red Hat Israel

Re: [ovirt-users] Engine reports

2018-04-06 Thread Rich Megginson


On 04/06/2018 03:08 PM, Peter Hudec wrote:

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible


I recommend that you start over with the RPM based openshift-ansible, 
which is what the instructions say, which is what I have tested


alternately - if you want to go the more experimental route, you could 
enable the epel-testing yum repo - ansible-2.5 is in epel-testing which 
I've been told by the openshift-ansible guys should work




Peter

On 06/04/2018 20:23, Rich Megginson wrote:

I'm assuming you are running on a CentOS7 machine, recently updated to
the latest base packages. Please confirm.

Please provide the output of the following commands:

sudo yum repolist

sudo rpm -q ansible

sudo yum repoquery -i ansible

sudo rpm -q openshift-ansible

sudo yum repoquery -i openshift-ansible

sudo rpm -q origin

sudo yum repoquery -i origin

sudo cat
/usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py


sudo ls -alrtF /etc/origin/logging

Please confirm that you followed the steps listed in the link below,
including the use of the ansible inventory, vars.yaml.template, and repo
files:
https://github.com/richm/Main/blob/7e663351dc371b7895564072c7656ebfda45068d/README-install.md


On 04/06/2018 03:19 AM, Peter Hudec wrote:

first issue is ansible version, could be solved by virtual env

FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
versions: 2.4.3.0 or newer

yum install -y python-virtualenv
virtualenv ansible
. ./ansible/bin/activate
pip install -U pip setuptolls
pip install -U pip setuptools
pip install ansible


Second issue is a little bit strange for me

2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:


    1. Hosts:    localhost
   Play: OpenShift Aggregated Logging
   Task: pulling down signing items from host
   Message:  ESC[0;31mAll items completedESC[0m

I have found in logs

2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
(item=ca.crl.srl) => {
  "changed": false,
  "invocation": {
  "module_args": {
  "src": "/etc/origin/logging/ca.crl.srl"
  }
  },
  "item": "ca.crl.srl",
  "msg": "file not found: /etc/origin/logging/ca.crl.srl"


Is this good or bad ?

 Peter

On 05/04/2018 16:11, Rich Megginson wrote:

Is it possible that you could start over from scratch, using the latest
instructions/files at
https://github.com/ViaQ/Main/pull/37/files?

On 04/05/2018 07:19 AM, Peter Hudec wrote:

The version is from

/usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version



[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
/usr/bin/openshift version
openshift v3.10.0-alpha.0+f0186dd-401
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package

[PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
origin-3.7.2-1.el7.git.0.f0186dd.x86_64

Hmm, why the version do not match ?

  Peter

On 04/04/2018 17:41, Shirly Radco wrote:

Hi,


I have a updated the installation instructions for installing
OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of
OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md



It should be merged soon, but you can use it to install.


Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.


Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 


TRIED. TESTED. TRUSTED. 


On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson > wrote:

   I'm sorry.  I misunderstood the request.

   We are in the process of updating the instructions for
installing
   viaq logging based on upstream origin 3.9 -
   https://github.com/ViaQ/Main/pull/37
   

   In the meantime, you can follow along on that PR, and we will
have
   instructions very soon.


   On 04/04/2018 08:26 AM, Rich Megginson wrote:

   On 04/04/2018 08:22 AM, Shirly Radco wrote:



   --

   SHIRLY RADCO

   BI SeNIOR SOFTWARE ENGINEER

   Red Hat Israel 

   
   TRIED. TESTED. TRUSTED. 


   On Wed,

Re: [ovirt-users] Engine reports

2018-04-06 Thread Peter Hudec

Hi,

https://tools.apps.hudecof.net/paste/view/1d493d52

The difference is
- I used latest ansible 2.5 from PIPY source, since the RPM package do
not fit requirements
- I used GIT repo for openshift-ansible.

I could start it over with the RPM based openshift-ansible

Peter

On 06/04/2018 20:23, Rich Megginson wrote:
> I'm assuming you are running on a CentOS7 machine, recently updated to
> the latest base packages. Please confirm.
> 
> Please provide the output of the following commands:
> 
> sudo yum repolist
> 
> sudo rpm -q ansible
> 
> sudo yum repoquery -i ansible
> 
> sudo rpm -q openshift-ansible
> 
> sudo yum repoquery -i openshift-ansible
> 
> sudo rpm -q origin
> 
> sudo yum repoquery -i origin
> 
> sudo cat
> /usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py
> 
> 
> sudo ls -alrtF /etc/origin/logging
> 
> Please confirm that you followed the steps listed in the link below,
> including the use of the ansible inventory, vars.yaml.template, and repo
> files:
> https://github.com/richm/Main/blob/7e663351dc371b7895564072c7656ebfda45068d/README-install.md
> 
> 
> On 04/06/2018 03:19 AM, Peter Hudec wrote:
>> first issue is ansible version, could be solved by virtual env
>>
>> FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
>> versions: 2.4.3.0 or newer
>>
>> yum install -y python-virtualenv
>> virtualenv ansible
>> . ./ansible/bin/activate
>> pip install -U pip setuptolls
>> pip install -U pip setuptools
>> pip install ansible
>>
>>
>> Second issue is a little bit strange for me
>>
>> 2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:
>>
>>
>>    1. Hosts:    localhost
>>   Play: OpenShift Aggregated Logging
>>   Task: pulling down signing items from host
>>   Message:  ESC[0;31mAll items completedESC[0m
>>
>> I have found in logs
>>
>> 2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
>> (item=ca.crl.srl) => {
>>  "changed": false,
>>  "invocation": {
>>  "module_args": {
>>  "src": "/etc/origin/logging/ca.crl.srl"
>>  }
>>  },
>>  "item": "ca.crl.srl",
>>  "msg": "file not found: /etc/origin/logging/ca.crl.srl"
>>
>>
>> Is this good or bad ?
>>
>> Peter
>>
>> On 05/04/2018 16:11, Rich Megginson wrote:
>>> Is it possible that you could start over from scratch, using the latest
>>> instructions/files at
>>> https://github.com/ViaQ/Main/pull/37/files?
>>>
>>> On 04/05/2018 07:19 AM, Peter Hudec wrote:
 The version is from

 /usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version



 [PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
 /usr/bin/openshift version
 openshift v3.10.0-alpha.0+f0186dd-401
 kubernetes v1.9.1+a0ce1bc657
 etcd 3.2.16

 this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package

 [PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
 origin-3.7.2-1.el7.git.0.f0186dd.x86_64

 Hmm, why the version do not match ?

  Peter

 On 04/04/2018 17:41, Shirly Radco wrote:
> Hi,
>
>
> I have a updated the installation instructions for installing
> OpenShift
> 3.9, based on Rich's work , for the oVirt use case.
>
> Please make sure where you get the 3.10 rpm and disable that repo.
>
> This is the PR that includes the metrics store installation of
> OpenShift 3.9
>
> https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md
>
>
>
> It should be merged soon, but you can use it to install.
>
>
> Please make sure to add the ansible-inventory-origin-39-aio file as
> described below.
> These are required parameters for the ansible playbook.
>
>
> Best regards,
>
> -- 
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
>
> 
> TRIED. TESTED. TRUSTED. 
>
>
> On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson  > wrote:
>
>   I'm sorry.  I misunderstood the request.
>
>   We are in the process of updating the instructions for
> installing
>   viaq logging based on upstream origin 3.9 -
>   https://github.com/ViaQ/Main/pull/37
>   
>
>   In the meantime, you can follow along on that PR, and we will
> have
>   instructions very soon.
>
>
>   On 04/04/2018 08:26 AM, Rich Megginson wrote:
>
>   On 04/04/2018 08:22 AM, Shirly Radco wrote:
>
>
>
>   --
>
>   SHIRLY RADCO

Re: [ovirt-users] Engine reports

2018-04-06 Thread Rich Megginson

I'm assuming you are running on a CentOS7 machine, recently updated to 
the latest base packages. Please confirm.


Please provide the output of the following commands:

sudo yum repolist

sudo rpm -q ansible

sudo yum repoquery -i ansible

sudo rpm -q openshift-ansible

sudo yum repoquery -i openshift-ansible

sudo rpm -q origin

sudo yum repoquery -i origin

sudo cat 
/usr/share/ansible/openshift-ansible/roles/lib_utils/callback_plugins/aa_version_requirement.py


sudo ls -alrtF /etc/origin/logging

Please confirm that you followed the steps listed in the link below, 
including the use of the ansible inventory, vars.yaml.template, and repo 
files:

https://github.com/richm/Main/blob/7e663351dc371b7895564072c7656ebfda45068d/README-install.md

On 04/06/2018 03:19 AM, Peter Hudec wrote:

first issue is ansible version, could be solved by virtual env

FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
versions: 2.4.3.0 or newer

yum install -y python-virtualenv
virtualenv ansible
. ./ansible/bin/activate
pip install -U pip setuptolls
pip install -U pip setuptools
pip install ansible


Second issue is a little bit strange for me

2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:


   1. Hosts:localhost
  Play: OpenShift Aggregated Logging
  Task: pulling down signing items from host
  Message:  ESC[0;31mAll items completedESC[0m

I have found in logs

2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
(item=ca.crl.srl) => {
 "changed": false,
 "invocation": {
 "module_args": {
 "src": "/etc/origin/logging/ca.crl.srl"
 }
 },
 "item": "ca.crl.srl",
 "msg": "file not found: /etc/origin/logging/ca.crl.srl"


Is this good or bad ?

Peter

On 05/04/2018 16:11, Rich Megginson wrote:

Is it possible that you could start over from scratch, using the latest
instructions/files at
https://github.com/ViaQ/Main/pull/37/files?

On 04/05/2018 07:19 AM, Peter Hudec wrote:

The version is from

/usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version


[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
/usr/bin/openshift version
openshift v3.10.0-alpha.0+f0186dd-401
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package

[PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
origin-3.7.2-1.el7.git.0.f0186dd.x86_64

Hmm, why the version do not match ?

 Peter

On 04/04/2018 17:41, Shirly Radco wrote:

Hi,


I have a updated the installation instructions for installing OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of
OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md


It should be merged soon, but you can use it to install.


Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.


Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 


TRIED. TESTED. TRUSTED. 


On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson > wrote:

  I'm sorry.  I misunderstood the request.

  We are in the process of updating the instructions for installing
  viaq logging based on upstream origin 3.9 -
  https://github.com/ViaQ/Main/pull/37
  

  In the meantime, you can follow along on that PR, and we will have
  instructions very soon.


  On 04/04/2018 08:26 AM, Rich Megginson wrote:

  On 04/04/2018 08:22 AM, Shirly Radco wrote:



  --

  SHIRLY RADCO

  BI SeNIOR SOFTWARE ENGINEER

  Red Hat Israel 

  
  TRIED. TESTED. TRUSTED. 


  On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec  >> wrote:

      almost the same issue, the versio for openshoft release
  changed to 3.9

      Failure summary:


        1. Hosts:    localhost
           Play:     Determine openshift_version to configure
  on first
      master
           Task:     For an RPM install, abort when the
release
      requested does
      not match the available version.
           Message:  You requested openshift_release 3.9,
  which is not

Re: [ovirt-users] Engine reports

2018-04-06 Thread Peter Hudec

first issue is ansible version, could be solved by virtual env

FATAL: Current Ansible version (2.4.2.0) is not supported. Supported
versions: 2.4.3.0 or newer

yum install -y python-virtualenv
virtualenv ansible
. ./ansible/bin/activate
pip install -U pip setuptolls
pip install -U pip setuptools
pip install ansible


Second issue is a little bit strange for me

2018-04-06 10:00:30,264 p=68226 u=root |  Failure summary:


  1. Hosts:localhost
 Play: OpenShift Aggregated Logging
 Task: pulling down signing items from host
 Message:  ESC[0;31mAll items completedESC[0m

I have found in logs

2018-04-06 10:00:28,356 p=68226 u=root |  failed: [localhost]
(item=ca.crl.srl) => {
"changed": false,
"invocation": {
"module_args": {
"src": "/etc/origin/logging/ca.crl.srl"
}
},
"item": "ca.crl.srl",
"msg": "file not found: /etc/origin/logging/ca.crl.srl"


Is this good or bad ?

Peter

On 05/04/2018 16:11, Rich Megginson wrote:
> Is it possible that you could start over from scratch, using the latest
> instructions/files at
> https://github.com/ViaQ/Main/pull/37/files?
> 
> On 04/05/2018 07:19 AM, Peter Hudec wrote:
>> The version is from
>>
>> /usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version
>>
>>
>> [PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
>> /usr/bin/openshift version
>> openshift v3.10.0-alpha.0+f0186dd-401
>> kubernetes v1.9.1+a0ce1bc657
>> etcd 3.2.16
>>
>> this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
>> origin-3.7.2-1.el7.git.0.f0186dd.x86_64
>>
>> Hmm, why the version do not match ?
>>
>> Peter
>>
>> On 04/04/2018 17:41, Shirly Radco wrote:
>>> Hi,
>>>
>>>
>>> I have a updated the installation instructions for installing OpenShift
>>> 3.9, based on Rich's work , for the oVirt use case.
>>>
>>> Please make sure where you get the 3.10 rpm and disable that repo.
>>>
>>> This is the PR that includes the metrics store installation of
>>> OpenShift 3.9
>>>
>>> https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md
>>>
>>>
>>> It should be merged soon, but you can use it to install.
>>>
>>>
>>> Please make sure to add the ansible-inventory-origin-39-aio file as
>>> described below.
>>> These are required parameters for the ansible playbook.
>>>
>>>
>>> Best regards,
>>>
>>> -- 
>>>
>>> SHIRLY RADCO
>>>
>>> BI SeNIOR SOFTWARE ENGINEER
>>>
>>> Red Hat Israel 
>>>
>>>    
>>> TRIED. TESTED. TRUSTED. 
>>>
>>>
>>> On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson >> > wrote:
>>>
>>>  I'm sorry.  I misunderstood the request.
>>>
>>>  We are in the process of updating the instructions for installing
>>>  viaq logging based on upstream origin 3.9 -
>>>  https://github.com/ViaQ/Main/pull/37
>>>  
>>>
>>>  In the meantime, you can follow along on that PR, and we will have
>>>  instructions very soon.
>>>
>>>
>>>  On 04/04/2018 08:26 AM, Rich Megginson wrote:
>>>
>>>  On 04/04/2018 08:22 AM, Shirly Radco wrote:
>>>
>>>
>>>
>>>  --
>>>
>>>  SHIRLY RADCO
>>>
>>>  BI SeNIOR SOFTWARE ENGINEER
>>>
>>>  Red Hat Israel 
>>>
>>>  
>>>  TRIED. TESTED. TRUSTED. 
>>>
>>>
>>>  On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec >>   >>  >> wrote:
>>>
>>>      almost the same issue, the versio for openshoft release
>>>  changed to 3.9
>>>
>>>      Failure summary:
>>>
>>>
>>>        1. Hosts:    localhost
>>>           Play:     Determine openshift_version to configure
>>>  on first
>>>      master
>>>           Task:     For an RPM install, abort when the
>>> release
>>>      requested does
>>>      not match the available version.
>>>           Message:  You requested openshift_release 3.9,
>>>  which is not
>>>      matched by
>>>                     the latest OpenShift RPM we detected as
>>>  origin-3.10.0
>>>                     on host localhost.
>>>                     We will only install the latest RPMs, so
>>>  please ensure
>>>      you are getting the release
>>>                     you expect. You may need to adjust your
>>>  Ansible
>>>

Re: [ovirt-users] Engine reports

2018-04-05 Thread Peter Hudec

Since it's still not installed, yes ;)

On 05/04/2018 16:11, Rich Megginson wrote:
> Is it possible that you could start over from scratch, using the latest
> instructions/files at
> https://github.com/ViaQ/Main/pull/37/files?
> 
> On 04/05/2018 07:19 AM, Peter Hudec wrote:
>> The version is from
>>
>> /usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version
>>
>>
>> [PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
>> /usr/bin/openshift version
>> openshift v3.10.0-alpha.0+f0186dd-401
>> kubernetes v1.9.1+a0ce1bc657
>> etcd 3.2.16
>>
>> this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package
>>
>> [PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
>> origin-3.7.2-1.el7.git.0.f0186dd.x86_64
>>
>> Hmm, why the version do not match ?
>>
>> Peter
>>
>> On 04/04/2018 17:41, Shirly Radco wrote:
>>> Hi,
>>>
>>>
>>> I have a updated the installation instructions for installing OpenShift
>>> 3.9, based on Rich's work , for the oVirt use case.
>>>
>>> Please make sure where you get the 3.10 rpm and disable that repo.
>>>
>>> This is the PR that includes the metrics store installation of
>>> OpenShift 3.9
>>>
>>> https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md
>>>
>>>
>>> It should be merged soon, but you can use it to install.
>>>
>>>
>>> Please make sure to add the ansible-inventory-origin-39-aio file as
>>> described below.
>>> These are required parameters for the ansible playbook.
>>>
>>>
>>> Best regards,
>>>
>>> -- 
>>>
>>> SHIRLY RADCO
>>>
>>> BI SeNIOR SOFTWARE ENGINEER
>>>
>>> Red Hat Israel 
>>>
>>>    
>>> TRIED. TESTED. TRUSTED. 
>>>
>>>
>>> On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson >> > wrote:
>>>
>>>  I'm sorry.  I misunderstood the request.
>>>
>>>  We are in the process of updating the instructions for installing
>>>  viaq logging based on upstream origin 3.9 -
>>>  https://github.com/ViaQ/Main/pull/37
>>>  
>>>
>>>  In the meantime, you can follow along on that PR, and we will have
>>>  instructions very soon.
>>>
>>>
>>>  On 04/04/2018 08:26 AM, Rich Megginson wrote:
>>>
>>>  On 04/04/2018 08:22 AM, Shirly Radco wrote:
>>>
>>>
>>>
>>>  --
>>>
>>>  SHIRLY RADCO
>>>
>>>  BI SeNIOR SOFTWARE ENGINEER
>>>
>>>  Red Hat Israel 
>>>
>>>  
>>>  TRIED. TESTED. TRUSTED. 
>>>
>>>
>>>  On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec >>   >>  >> wrote:
>>>
>>>      almost the same issue, the versio for openshoft release
>>>  changed to 3.9
>>>
>>>      Failure summary:
>>>
>>>
>>>        1. Hosts:    localhost
>>>           Play:     Determine openshift_version to configure
>>>  on first
>>>      master
>>>           Task:     For an RPM install, abort when the
>>> release
>>>      requested does
>>>      not match the available version.
>>>           Message:  You requested openshift_release 3.9,
>>>  which is not
>>>      matched by
>>>                     the latest OpenShift RPM we detected as
>>>  origin-3.10.0
>>>                     on host localhost.
>>>                     We will only install the latest RPMs, so
>>>  please ensure
>>>      you are getting the release
>>>                     you expect. You may need to adjust your
>>>  Ansible
>>>      inventory, modify the repositories
>>>                     available on the host, or run the
>>>  appropriate OpenShift
>>>      upgrade playbook.
>>>
>>>
>>>  What is the rpm version installed of OpenShift origin?
>>>  Do you perhaps have another repo that includes the
>>> OpenShift
>>>  origin-3.10.0?
>>>
>>>
>>>  origin is the upstream version of OpenShift, which is
>>> unsupported.
>>>
>>>  sudo repoquery -i origin
>>>
>>>  This will tell you which repo it came from
>>>
>>>  You will need to disable that repo and uninstall any packages
>>>  which came from that repo
>>>
>>>  Another mystery is why it is trying to install origin in the
>>>  first place.  openshift-ansible with
>>>  openshift_deployment_type=openshift-enterprise should not
>>> try to
>>>  install origin, it

Re: [ovirt-users] Engine reports

2018-04-05 Thread Rich Megginson

Is it possible that you could start over from scratch, using the latest
instructions/files at

https://github.com/ViaQ/Main/pull/37/files?

On 04/05/2018 07:19 AM, Peter Hudec wrote:

The version is from

/usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version

[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
/usr/bin/openshift version
openshift v3.10.0-alpha.0+f0186dd-401
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package

[PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
origin-3.7.2-1.el7.git.0.f0186dd.x86_64

Hmm, why the version do not match ?

Peter

On 04/04/2018 17:41, Shirly Radco wrote:

Hi,

I have a updated the installation instructions for installing OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md

It should be merged soon, but you can use it to install.

Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.

Best regards,

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel

TRIED. TESTED. TRUSTED.

On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson > wrote:

I'm sorry. I misunderstood the request.

We are in the process of updating the instructions for installing
viaq logging based on upstream origin 3.9 -
https://github.com/ViaQ/Main/pull/37

In the meantime, you can follow along on that PR, and we will have
instructions very soon.

On 04/04/2018 08:26 AM, Rich Megginson wrote:

On 04/04/2018 08:22 AM, Shirly Radco wrote:

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel

TRIED. TESTED. TRUSTED.

On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec >> wrote:

almost the same issue, the versio for openshoft release
changed to 3.9

Failure summary:

1. Hosts: localhost
Play: Determine openshift_version to configure
on first
master
Task: For an RPM install, abort when the release
requested does
not match the available version.
Message: You requested openshift_release 3.9,
which is not
matched by
the latest OpenShift RPM we detected as
origin-3.10.0
on host localhost.
We will only install the latest RPMs, so
please ensure
you are getting the release
you expect. You may need to adjust your
Ansible
inventory, modify the repositories
available on the host, or run the
appropriate OpenShift
upgrade playbook.

What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift
origin-3.10.0?

origin is the upstream version of OpenShift, which is unsupported.

sudo repoquery -i origin

This will tell you which repo it came from

You will need to disable that repo and uninstall any packages
which came from that repo

Another mystery is why it is trying to install origin in the
first place. openshift-ansible with
openshift_deployment_type=openshift-enterprise should not try to
install origin, it should install packages with names like
atomic-openshift-master, atomic-openshift-node, etc.

On 04/04/2018 14:18, Shirly Radco wrote:
> Adding Nicolas since he hit the same issue.
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel
>
>
> TRIED. TESTED. TRUSTED.

Re: [ovirt-users] Engine reports

2018-04-05 Thread Peter Hudec

The version is from

/usr/share/ansible/openshift-ansible/roles/openshift_facts/library/openshift_facts.py:get_openshift_version

[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
/usr/bin/openshift version
openshift v3.10.0-alpha.0+f0186dd-401
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

this binary is from the origin-3.7.2-1.el7.git.0.f0186dd.x86_64 package

[PROD] r...@dipostat01.cnc.sk: ~ # rpm -qf /usr/bin/openshift
origin-3.7.2-1.el7.git.0.f0186dd.x86_64

Hmm, why the version do not match ?

Peter

On 04/04/2018 17:41, Shirly Radco wrote:
> Hi,
> 
> 
> I have a updated the installation instructions for installing OpenShift
> 3.9, based on Rich's work , for the oVirt use case.
> 
> Please make sure where you get the 3.10 rpm and disable that repo.
> 
> This is the PR that includes the metrics store installation of OpenShift 3.9
> 
> https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md
> 
> It should be merged soon, but you can use it to install.
> 
> 
> Please make sure to add the ansible-inventory-origin-39-aio file as
> described below.
> These are required parameters for the ansible playbook.
> 
> 
> Best regards,
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson  > wrote:
> 
> I'm sorry.  I misunderstood the request.
> 
> We are in the process of updating the instructions for installing
> viaq logging based on upstream origin 3.9 -
> https://github.com/ViaQ/Main/pull/37
> 
> 
> In the meantime, you can follow along on that PR, and we will have
> instructions very soon.
> 
> 
> On 04/04/2018 08:26 AM, Rich Megginson wrote:
> 
> On 04/04/2018 08:22 AM, Shirly Radco wrote:
> 
> 
> 
> -- 
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
> 
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec    >> wrote:
> 
>     almost the same issue, the versio for openshoft release
> changed to 3.9
> 
>     Failure summary:
> 
> 
>       1. Hosts:    localhost
>          Play:     Determine openshift_version to configure
> on first
>     master
>          Task:     For an RPM install, abort when the release
>     requested does
>     not match the available version.
>          Message:  You requested openshift_release 3.9,
> which is not
>     matched by
>                    the latest OpenShift RPM we detected as
> origin-3.10.0
>                    on host localhost.
>                    We will only install the latest RPMs, so
> please ensure
>     you are getting the release
>                    you expect. You may need to adjust your
> Ansible
>     inventory, modify the repositories
>                    available on the host, or run the
> appropriate OpenShift
>     upgrade playbook.
> 
> 
> What is the rpm version installed of OpenShift origin?
> Do you perhaps have another repo that includes the OpenShift
> origin-3.10.0?
> 
> 
> origin is the upstream version of OpenShift, which is unsupported.
> 
> sudo repoquery -i origin
> 
> This will tell you which repo it came from
> 
> You will need to disable that repo and uninstall any packages
> which came from that repo
> 
> Another mystery is why it is trying to install origin in the
> first place.  openshift-ansible with
> openshift_deployment_type=openshift-enterprise should not try to
> install origin, it should install packages with names like
> atomic-openshift-master, atomic-openshift-node, etc.
> 
> 
> 
> 
>     On 04/04/2018 14:18, Shirly Radco wrote:
>     > Adding Nicolas since he hit the same issue.
>     >
>     > --
>     >
>     > SHIRLY RADCO
>     >
>     > BI SeNIOR SOFTWARE ENGINEER
>     >
>     > Red Hat Israel 
>     >
>     > 
>     > TRIED. TESTED. TRUSTED.

Re: [ovirt-users] Engine reports

2018-04-04 Thread Shirly Radco

Hi,


I have a updated the installation instructions for installing OpenShift
3.9, based on Rich's work , for the oVirt use case.

Please make sure where you get the 3.10 rpm and disable that repo.

This is the PR that includes the metrics store installation of OpenShift 3.9

https://github.com/sradco/ovirt-site/blob/74f1e772c8ca75d4b9e57a3c02cce49c5030f7f7/source/develop/release-management/features/metrics/setting-up-viaq-logging.html.md

It should be merged soon, but you can use it to install.


Please make sure to add the ansible-inventory-origin-39-aio file as
described below.
These are required parameters for the ansible playbook.


Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:41 PM, Rich Megginson  wrote:

> I'm sorry.  I misunderstood the request.
>
> We are in the process of updating the instructions for installing viaq
> logging based on upstream origin 3.9 - https://github.com/ViaQ/Main/p
> ull/37
>
> In the meantime, you can follow along on that PR, and we will have
> instructions very soon.
>
>
> On 04/04/2018 08:26 AM, Rich Megginson wrote:
>
>> On 04/04/2018 08:22 AM, Shirly Radco wrote:
>>
>>>
>>>
>>> --
>>>
>>> SHIRLY RADCO
>>>
>>> BI SeNIOR SOFTWARE ENGINEER
>>>
>>> Red Hat Israel 
>>>
>>> 
>>> TRIED. TESTED. TRUSTED. 
>>>
>>>
>>> On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > phu...@cnc.sk>> wrote:
>>>
>>> almost the same issue, the versio for openshoft release changed to
>>> 3.9
>>>
>>> Failure summary:
>>>
>>>
>>>   1. Hosts:localhost
>>>  Play: Determine openshift_version to configure on first
>>> master
>>>  Task: For an RPM install, abort when the release
>>> requested does
>>> not match the available version.
>>>  Message:  You requested openshift_release 3.9, which is not
>>> matched by
>>>the latest OpenShift RPM we detected as origin-3.10.0
>>>on host localhost.
>>>We will only install the latest RPMs, so please ensure
>>> you are getting the release
>>>you expect. You may need to adjust your Ansible
>>> inventory, modify the repositories
>>>available on the host, or run the appropriate
>>> OpenShift
>>> upgrade playbook.
>>>
>>>
>>> What is the rpm version installed of OpenShift origin?
>>> Do you perhaps have another repo that includes the OpenShift
>>> origin-3.10.0?
>>>
>>
>> origin is the upstream version of OpenShift, which is unsupported.
>>
>> sudo repoquery -i origin
>>
>> This will tell you which repo it came from
>>
>> You will need to disable that repo and uninstall any packages which came
>> from that repo
>>
>> Another mystery is why it is trying to install origin in the first
>> place.  openshift-ansible with openshift_deployment_type=openshift-enterprise
>> should not try to install origin, it should install packages with names
>> like atomic-openshift-master, atomic-openshift-node, etc.
>>
>>
>>>
>>>
>>> On 04/04/2018 14:18, Shirly Radco wrote:
>>> > Adding Nicolas since he hit the same issue.
>>> >
>>> > --
>>> >
>>> > SHIRLY RADCO
>>> >
>>> > BI SeNIOR SOFTWARE ENGINEER
>>> >
>>> > Red Hat Israel 
>>> >
>>> > 
>>> > TRIED. TESTED. TRUSTED. 
>>> >
>>> >
>>> > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco >> 
>>> > >> wrote:
>>> >
>>> > Hi Peter,
>>> >
>>> > The installation instructions currently support OpenShift 3.6.
>>> >
>>> > I'm now working on updating them to support 3.9.
>>> >
>>> > You currently have 3.10 installed.
>>> >
>>> > Please install OpenShift 3.9 using this repository
>>> > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
>>> 
>>> >  >> >
>>> >
>>> > And add the following file to your vm
>>> >
>>> > Run:
>>> > vi /root/ansible-inventory-origin-39-aio
>>> >
>>> > Add:
>>> >
>>> > --
>>> > [OSEv3:children]
>>> > nodes
>>> > masters
>>> > etcd
>>> >
>>> > [OSEv3:vars]
>>> > ansible_connection=local
>>> > openshift_release=v3.9
>>> > openshift_logging_install_logging=true
>>> > short_version=3.9
>>> > openshift_deployment_type=origin
>>> >

Re: [ovirt-users] Engine reports

2018-04-04 Thread Peter Hudec

[PROD] r...@dipostat01.cnc.sk: /usr/share/ansible/openshift-ansible #
repoquery -i origin
Repository centos-openshift-origin is listed more than once in the
configuration

Name: origin
Version : 3.7.2
Release : 1.el7.git.0.f0186dd
Architecture: x86_64
Size: 957727742
Packager: CBS 
Group   : Unspecified
URL : https://github.com/openshift/origin
Repository  : centos-openshift-origin37-candidate
Summary : Open Source Container Management by Red Hat
Source  : origin-3.7.2-1.el7.git.0.f0186dd.src.rpm
Description :
OpenShift is a distribution of Kubernetes optimized for enterprise
application
development and deployment. OpenShift adds developer and operational centric
tools on top of Kubernetes to enable rapid application development, easy
deployment and scaling, and long-term lifecycle maintenance for small
and large
teams and applications. It provides a secure and multi-tenant
configuration for
Kubernetes allowing you to safely host many different applications and
workloads
on a unified cluster.

On 04/04/2018 16:26, Rich Megginson wrote:
> sudo repoquery -i origin


-- 
*Peter Hudec*
Infraštruktúrny architekt
phu...@cnc.sk 

*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2  35 000 100

Mobil:+421 905 997 203
*www.cnc.sk* 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

2018-04-04 Thread Rich Megginson

I'm sorry.  I misunderstood the request.

We are in the process of updating the instructions for installing viaq 
logging based on upstream origin 3.9 - https://github.com/ViaQ/Main/pull/37

In the meantime, you can follow along on that PR, and we will have 
instructions very soon.

On 04/04/2018 08:26 AM, Rich Megginson wrote:

On 04/04/2018 08:22 AM, Shirly Radco wrote:

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > wrote:

    almost the same issue, the versio for openshoft release changed 
to 3.9

    Failure summary:

      1. Hosts:    localhost
         Play:     Determine openshift_version to configure on first
    master
         Task:     For an RPM install, abort when the release
    requested does
    not match the available version.
         Message:  You requested openshift_release 3.9, which is not
    matched by
                   the latest OpenShift RPM we detected as origin-3.10.0
                   on host localhost.
                   We will only install the latest RPMs, so please 
ensure

    you are getting the release
                   you expect. You may need to adjust your Ansible
    inventory, modify the repositories
                   available on the host, or run the appropriate 
OpenShift

    upgrade playbook.

What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift 
origin-3.10.0?

origin is the upstream version of OpenShift, which is unsupported.

sudo repoquery -i origin

This will tell you which repo it came from

You will need to disable that repo and uninstall any packages which 
came from that repo

Another mystery is why it is trying to install origin in the first 
place.  openshift-ansible with 
openshift_deployment_type=openshift-enterprise should not try to 
install origin, it should install packages with names like 
atomic-openshift-master, atomic-openshift-node, etc.

    On 04/04/2018 14:18, Shirly Radco wrote:
    > Adding Nicolas since he hit the same issue.
    >
    > --
    >
    > SHIRLY RADCO
    >
    > BI SeNIOR SOFTWARE ENGINEER
    >
    > Red Hat Israel 
    >
    > 
    > TRIED. TESTED. TRUSTED. 
    >
    >
    > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco 

    > >> wrote:
    >
    >     Hi Peter,
    >
    >     The installation instructions currently support OpenShift 3.6.
    >
    >     I'm now working on updating them to support 3.9.
    >
    >     You currently have 3.10 installed.
    >
    >     Please install OpenShift 3.9 using this repository
    > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

    >  >
    >
    >     And add the following file to your vm
    >
    >     Run:
    >     vi /root/ansible-inventory-origin-39-aio
    >
    >     Add:
    >
    >     --
    >     [OSEv3:children]
    >     nodes
    >     masters
    >     etcd
    >
    >     [OSEv3:vars]
    >     ansible_connection=local
    >     openshift_release=v3.9
    >     openshift_logging_install_logging=true
    >     short_version=3.9
    >     openshift_deployment_type=origin
    >  openshift_master_identity_providers=[{'mappingMethod': 'lookup',
    >     'challenge': 'true', 'login': 'true', 'kind':
    >     'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
    >     # bug - doesn't use correct tag
    >     openshift_logging_image_version=v3.9
    >  openshift_logging_elasticsearch_proxy_image_version=v1.0.0
    >
    >     openshift_logging_es_allow_external=True
    >     openshift_logging_use_mux=True
    >     openshift_logging_mux_allow_external=True
    >  openshift_logging_mux_file_buffer_storage_type=hostmount
    >  openshift_logging_elasticsearch_storage_type=hostmount
    >
 openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
    >
    >     [nodes]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >     [masters]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >     [etcd]
    >     localhost storage=True openshift_node_labels="{'region':
    'infra'}"
    >     openshift_schedulable=True
    >
    >
    >     
    >
    >     Save and exit.
    >
    >
    >     ***Please make sure that you use /var as your Elasticsearch
    >     persistent storage directory.
    >
    >     And when you run the

Re: [ovirt-users] Engine reports

2018-04-04 Thread Rich Megginson

On 04/04/2018 08:22 AM, Shirly Radco wrote:

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec > wrote:

almost the same issue, the versio for openshoft release changed to 3.9

Failure summary:

  1. Hosts:    localhost
     Play:     Determine openshift_version to configure on first
master
     Task:     For an RPM install, abort when the release
requested does
not match the available version.
     Message:  You requested openshift_release 3.9, which is not
matched by
               the latest OpenShift RPM we detected as origin-3.10.0
               on host localhost.
               We will only install the latest RPMs, so please ensure
you are getting the release
               you expect. You may need to adjust your Ansible
inventory, modify the repositories
               available on the host, or run the appropriate OpenShift
upgrade playbook.

What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift 
origin-3.10.0?

origin is the upstream version of OpenShift, which is unsupported.

sudo repoquery -i origin

This will tell you which repo it came from

You will need to disable that repo and uninstall any packages which came 
from that repo

Another mystery is why it is trying to install origin in the first 
place.  openshift-ansible with 
openshift_deployment_type=openshift-enterprise should not try to install 
origin, it should install packages with names like 
atomic-openshift-master, atomic-openshift-node, etc.

On 04/04/2018 14:18, Shirly Radco wrote:
> Adding Nicolas since he hit the same issue.
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
>
> 
> TRIED. TESTED. TRUSTED. 
>
>
> On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco 
> >> wrote:
>
>     Hi Peter,
>
>     The installation instructions currently support OpenShift 3.6.
>
>     I'm now working on updating them to support 3.9.
>
>     You currently have 3.10 installed.
>
>     Please install OpenShift 3.9 using this repository
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

>     >
>
>     And add the following file to your vm
>
>     Run:
>     vi /root/ansible-inventory-origin-39-aio
>
>     Add:
>
>     --
>     [OSEv3:children]
>     nodes
>     masters
>     etcd
>
>     [OSEv3:vars]
>     ansible_connection=local
>     openshift_release=v3.9
>     openshift_logging_install_logging=true
>     short_version=3.9
>     openshift_deployment_type=origin
>     openshift_master_identity_providers=[{'mappingMethod': 'lookup',
>     'challenge': 'true', 'login': 'true', 'kind':
>     'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
>     # bug - doesn't use correct tag
>     openshift_logging_image_version=v3.9
>     openshift_logging_elasticsearch_proxy_image_version=v1.0.0
>
>     openshift_logging_es_allow_external=True
>     openshift_logging_use_mux=True
>     openshift_logging_mux_allow_external=True
>     openshift_logging_mux_file_buffer_storage_type=hostmount
>     openshift_logging_elasticsearch_storage_type=hostmount
>   
 openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
>
>     [nodes]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>     [masters]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>     [etcd]
>     localhost storage=True openshift_node_labels="{'region':
'infra'}"
>     openshift_schedulable=True
>
>
>     
>
>     Save and exit.
>
>
>     ***Please make sure that you use /var as your Elasticsearch
>     persistent storage directory.
>
>     And when you run the OpenShift ansible
>   

(https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible

>

Re: [ovirt-users] Engine reports

2018-04-04 Thread Shirly Radco

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 5:07 PM, Peter Hudec  wrote:

> almost the same issue, the versio for openshoft release changed to 3.9
>
> Failure summary:
>
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.9, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
>
What is the rpm version installed of OpenShift origin?
Do you perhaps have another repo that includes the OpenShift origin-3.10.0?



> On 04/04/2018 14:18, Shirly Radco wrote:
> > Adding Nicolas since he hit the same issue.
> >
> > --
> >
> > SHIRLY RADCO
> >
> > BI SeNIOR SOFTWARE ENGINEER
> >
> > Red Hat Israel 
> >
> > 
> > TRIED. TESTED. TRUSTED. 
> >
> >
> > On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  > > wrote:
> >
> > Hi Peter,
> >
> > The installation instructions currently support OpenShift 3.6.
> >
> > I'm now working on updating them to support 3.9.
> >
> > You currently have 3.10 installed.
> >
> > Please install OpenShift 3.9 using this repository
> > https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> > 
> >
> > And add the following file to your vm
> >
> > Run:
> > vi /root/ansible-inventory-origin-39-aio
> >
> > Add:
> >
> > --
> > [OSEv3:children]
> > nodes
> > masters
> > etcd
> >
> > [OSEv3:vars]
> > ansible_connection=local
> > openshift_release=v3.9
> > openshift_logging_install_logging=true
> > short_version=3.9
> > openshift_deployment_type=origin
> > openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> > 'challenge': 'true', 'login': 'true', 'kind':
> > 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> > # bug - doesn't use correct tag
> > openshift_logging_image_version=v3.9
> > openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> >
> > openshift_logging_es_allow_external=True
> > openshift_logging_use_mux=True
> > openshift_logging_mux_allow_external=True
> > openshift_logging_mux_file_buffer_storage_type=hostmount
> > openshift_logging_elasticsearch_storage_type=hostmount
> > openshift_logging_elasticsearch_hostmount_path=/
> var/lib/elasticsearch
> >
> > [nodes]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> > [masters]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> > [etcd]
> > localhost storage=True openshift_node_labels="{'region': 'infra'}"
> > openshift_schedulable=True
> >
> >
> > 
> >
> > Save and exit.
> >
> >
> > ***Please make sure that you use /var as your Elasticsearch
> > persistent storage directory.
> >
> > And when you run the OpenShift ansible
> > (https://www.ovirt.org/develop/release-management/
> features/metrics/setting-up-viaq-logging/#running-ansible
> >  features/metrics/setting-up-viaq-logging/#running-ansible>)
> > use the file you just created like this:
> >
> > # cd /usr/share/ansible/openshift-ansible
> > # (or wherever you cloned the git repo if using git)
> > ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> > @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> > playbooks/byo/config.yml
> >
> > Best regards,
> >
> > --
> >
> > SHIRLY RADCO
> >
> > BI SeNIOR SOFTWARE ENGINEER
> >
> > Red Hat Israel 
> >
> > 
> > TRIED. TESTED. TRUSTED. 
> >
> >
> > On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > > wrote:
> >
> > Tried to install ovirt metrics, but got error
> >
> > ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> > @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> > playbooks/byo/config.yml
> >
> >   1. Hosts:localhost
> >  Play: Determine openshift_version to

Re: [ovirt-users] Engine reports

2018-04-04 Thread Peter Hudec

almost the same issue, the versio for openshoft release changed to 3.9

Failure summary:


  1. Hosts:localhost
 Play: Determine openshift_version to configure on first master
 Task: For an RPM install, abort when the release requested does
not match the available version.
 Message:  You requested openshift_release 3.9, which is not matched by
   the latest OpenShift RPM we detected as origin-3.10.0
   on host localhost.
   We will only install the latest RPMs, so please ensure
you are getting the release
   you expect. You may need to adjust your Ansible
inventory, modify the repositories
   available on the host, or run the appropriate OpenShift
upgrade playbook.


On 04/04/2018 14:18, Shirly Radco wrote:
> Adding Nicolas since he hit the same issue.
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  > wrote:
> 
> Hi Peter,
> 
> The installation instructions currently support OpenShift 3.6.
> 
> I'm now working on updating them to support 3.9.
> 
> You currently have 3.10 installed.
> 
> Please install OpenShift 3.9 using this repository 
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> 
> 
> And add the following file to your vm 
> 
> Run:
> vi /root/ansible-inventory-origin-39-aio
> 
> Add:
> 
> --
> [OSEv3:children]
> nodes
> masters
> etcd
> 
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind':
> 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> 
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
> 
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> 
> 
> 
> Save and exit.
> 
> 
> ***Please make sure that you use /var as your Elasticsearch
> persistent storage directory.
> 
> And when you run the OpenShift ansible
> 
> (https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible
> 
> )
> use the file you just created like this:
> 
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
> 
> Best regards,
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > wrote:
> 
> Tried to install ovirt metrics, but got error
> 
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
> 
>   1. Hosts:    localhost
>      Play:     Determine openshift_version to configure on first
> master
>      Task:     For an RPM install, abort when the release
> requested does
> not match the available version.
>      Message:  You requested openshift_release 3.7, which is not
> matched by
>                the latest OpenShift RPM we detected as origin-3.10.0
>                on host localhost.
>                We will only install the latest RPMs, so please
> ensure
> you are getting the release
>                you expect. You may need to adjust your Ansible
>

Re: [ovirt-users] Engine reports

2018-04-04 Thread Peter Hudec

Hi SHIRLY,

I had clean server before installing. I will try to follow your advice.

Peter

On 04/04/2018 14:17, Shirly Radco wrote:
> Hi Peter,
> 
> The installation instructions currently support OpenShift 3.6.
> 
> I'm now working on updating them to support 3.9.
> 
> You currently have 3.10 installed.
> 
> Please install OpenShift 3.9 using this repository 
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
> 
> And add the following file to your vm 
> 
> Run:
> vi /root/ansible-inventory-origin-39-aio
> 
> Add:
> 
> --
> [OSEv3:children]
> nodes
> masters
> etcd
> 
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind':
> 'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
> 
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
> 
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
> 
> 
> 
> 
> Save and exit.
> 
> 
> ***Please make sure that you use /var as your Elasticsearch persistent
> storage directory.
> 
> And when you run the OpenShift ansible
> (https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible)
> use the file you just created like this:
> 
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
> 
> Best regards,
> 
> --
> 
> SHIRLY RADCO
> 
> BI SeNIOR SOFTWARE ENGINEER
> 
> Red Hat Israel 
> 
>   
> TRIED. TESTED. TRUSTED. 
> 
> 
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  > wrote:
> 
> Tried to install ovirt metrics, but got error
> 
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
> 
>   1. Hosts:    localhost
>      Play:     Determine openshift_version to configure on first master
>      Task:     For an RPM install, abort when the release requested does
> not match the available version.
>      Message:  You requested openshift_release 3.7, which is not
> matched by
>                the latest OpenShift RPM we detected as origin-3.10.0
>                on host localhost.
>                We will only install the latest RPMs, so please ensure
> you are getting the release
>                you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>                available on the host, or run the appropriate OpenShift
> upgrade playbook.
> 
>         regards
>                 Peter
> 
> 
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> 
> > 
> https://ovirt.org/develop/release-management/features/metrics/metrics-store/
> 
> 
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> >  
>  >>
> > wrote:
> >
> >     Hi,
> >
> >     I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> >     take the reports? I version 3.5, we had Jasper reports module using
> >     which we could take utilization reports. Can we do something similar
> >     here?
> >
> >     --
> >
> >     Thanks & Regards,
> >
> >
> >     Anantha Raghava
> >
> >
> >     Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> >     ___
> >     Users mailing list
> >     Users@ovirt.org

Re: [ovirt-users] Engine reports

2018-04-04 Thread Shirly Radco

Adding Nicolas since he hit the same issue.

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 3:17 PM, Shirly Radco  wrote:

> Hi Peter,
>
> The installation instructions currently support OpenShift 3.6.
>
> I'm now working on updating them to support 3.9.
>
> You currently have 3.10 installed.
>
> Please install OpenShift 3.9 using this repository
> https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo
>
> And add the following file to your vm
>
> Run:
> vi /root/ansible-inventory-origin-39-aio
>
> Add:
>
> --
> [OSEv3:children]
> nodes
> masters
> etcd
>
> [OSEv3:vars]
> ansible_connection=local
> openshift_release=v3.9
> openshift_logging_install_logging=true
> short_version=3.9
> openshift_deployment_type=origin
> openshift_master_identity_providers=[{'mappingMethod': 'lookup',
> 'challenge': 'true', 'login': 'true', 'kind': '
> AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
> # bug - doesn't use correct tag
> openshift_logging_image_version=v3.9
> openshift_logging_elasticsearch_proxy_image_version=v1.0.0
>
> openshift_logging_es_allow_external=True
> openshift_logging_use_mux=True
> openshift_logging_mux_allow_external=True
> openshift_logging_mux_file_buffer_storage_type=hostmount
> openshift_logging_elasticsearch_storage_type=hostmount
> openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch
>
> [nodes]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
> [masters]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
> [etcd]
> localhost storage=True openshift_node_labels="{'region': 'infra'}"
> openshift_schedulable=True
>
>
> 
>
> Save and exit.
>
>
> ***Please make sure that you use /var as your Elasticsearch persistent
> storage directory.
>
> And when you run the OpenShift ansible (https://www.ovirt.org/
> develop/release-management/features/metrics/setting-up-
> viaq-logging/#running-ansible) use the file you just created like this:
>
> # cd /usr/share/ansible/openshift-ansible
> # (or wherever you cloned the git repo if using git)
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/*ansible-inventory-origin-39-aio*
> playbooks/byo/config.yml
>
> Best regards,
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 
>
> On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:
>
>> Tried to install ovirt metrics, but got error
>>
>> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
>> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
>> playbooks/byo/config.yml
>>
>>   1. Hosts:localhost
>>  Play: Determine openshift_version to configure on first master
>>  Task: For an RPM install, abort when the release requested does
>> not match the available version.
>>  Message:  You requested openshift_release 3.7, which is not matched
>> by
>>the latest OpenShift RPM we detected as origin-3.10.0
>>on host localhost.
>>We will only install the latest RPMs, so please ensure
>> you are getting the release
>>you expect. You may need to adjust your Ansible
>> inventory, modify the repositories
>>available on the host, or run the appropriate OpenShift
>> upgrade playbook.
>>
>> regards
>> Peter
>>
>>
>> On 04/04/2018 09:13, Fred Rolland wrote:
>> > Hi,
>> >
>> > Check these links:
>> >
>> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
>> > https://ovirt.org/develop/release-management/features/metric
>> s/metrics-store/
>> >
>> > Regards,
>> > Fred
>> >
>> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
>> > >
>> > wrote:
>> >
>> > Hi,
>> >
>> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
>> > take the reports? I version 3.5, we had Jasper reports module using
>> > which we could take utilization reports. Can we do something similar
>> > here?
>> >
>> > --
>> >
>> > Thanks & Regards,
>> >
>> >
>> > Anantha Raghava
>> >
>> >
>> > Do not print this e-mail unless required. Save Paper & trees.
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org 
>> > http://lists.ovirt.org/mailman/listinfo/users
>> > 
>> >
>> >
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>> --
>> *Peter Hudec*
>>

Re: [ovirt-users] Engine reports

2018-04-04 Thread Shirly Radco

Hi Peter,

The installation instructions currently support OpenShift 3.6.

I'm now working on updating them to support 3.9.

You currently have 3.10 installed.

Please install OpenShift 3.9 using this repository
https://github.com/ViaQ/Main/blob/master/centos7-viaq.repo

And add the following file to your vm

Run:
vi /root/ansible-inventory-origin-39-aio

Add:

--
[OSEv3:children]
nodes
masters
etcd

[OSEv3:vars]
ansible_connection=local
openshift_release=v3.9
openshift_logging_install_logging=true
short_version=3.9
openshift_deployment_type=origin
openshift_master_identity_providers=[{'mappingMethod': 'lookup',
'challenge': 'true', 'login': 'true', 'kind':
'AllowAllPasswordIdentityProvider', 'name': 'allow_all'}]
# bug - doesn't use correct tag
openshift_logging_image_version=v3.9
openshift_logging_elasticsearch_proxy_image_version=v1.0.0

openshift_logging_es_allow_external=True
openshift_logging_use_mux=True
openshift_logging_mux_allow_external=True
openshift_logging_mux_file_buffer_storage_type=hostmount
openshift_logging_elasticsearch_storage_type=hostmount
openshift_logging_elasticsearch_hostmount_path=/var/lib/elasticsearch

[nodes]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True

[masters]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True

[etcd]
localhost storage=True openshift_node_labels="{'region': 'infra'}"
openshift_schedulable=True




Save and exit.


***Please make sure that you use /var as your Elasticsearch persistent
storage directory.

And when you run the OpenShift ansible (
https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/#running-ansible)
use the file you just created like this:

# cd /usr/share/ansible/openshift-ansible
# (or wherever you cloned the git repo if using git)
ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e @/root/vars.yaml
-i /root/*ansible-inventory-origin-39-aio* playbooks/byo/config.yml

Best regards,

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:

> Tried to install ovirt metrics, but got error
>
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.7, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
> regards
> Peter
>
>
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> > https://ovirt.org/develop/release-management/features/
> metrics/metrics-store/
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> > >
> > wrote:
> >
> > Hi,
> >
> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> > take the reports? I version 3.5, we had Jasper reports module using
> > which we could take utilization reports. Can we do something similar
> > here?
> >
> > --
> >
> > Thanks & Regards,
> >
> >
> > Anantha Raghava
> >
> >
> > Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> *Peter Hudec*
> Infraštruktúrny architekt
> phu...@cnc.sk 
>
> *CNC, a.s.*
> Borská 6, 841 04 Bratislava
> Recepcia: +421 2  35 000 100
>
> Mobil:+421 905 997 203
> *www.cnc.sk* 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

2018-04-04 Thread Fred Rolland

Shirly, can you take a look?

On Wed, Apr 4, 2018 at 12:17 PM, Peter Hudec  wrote:

> Tried to install ovirt metrics, but got error
>
> ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
> @/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
> playbooks/byo/config.yml
>
>   1. Hosts:localhost
>  Play: Determine openshift_version to configure on first master
>  Task: For an RPM install, abort when the release requested does
> not match the available version.
>  Message:  You requested openshift_release 3.7, which is not matched by
>the latest OpenShift RPM we detected as origin-3.10.0
>on host localhost.
>We will only install the latest RPMs, so please ensure
> you are getting the release
>you expect. You may need to adjust your Ansible
> inventory, modify the repositories
>available on the host, or run the appropriate OpenShift
> upgrade playbook.
>
> regards
> Peter
>
>
> On 04/04/2018 09:13, Fred Rolland wrote:
> > Hi,
> >
> > Check these links:
> >
> > https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> > https://ovirt.org/develop/release-management/features/
> metrics/metrics-store/
> >
> > Regards,
> > Fred
> >
> > On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> > >
> > wrote:
> >
> > Hi,
> >
> > I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> > take the reports? I version 3.5, we had Jasper reports module using
> > which we could take utilization reports. Can we do something similar
> > here?
> >
> > --
> >
> > Thanks & Regards,
> >
> >
> > Anantha Raghava
> >
> >
> > Do not print this e-mail unless required. Save Paper & trees.
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> --
> *Peter Hudec*
> Infraštruktúrny architekt
> phu...@cnc.sk 
>
> *CNC, a.s.*
> Borská 6, 841 04 Bratislava
> Recepcia: +421 2  35 000 100
>
> Mobil:+421 905 997 203
> *www.cnc.sk* 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

2018-04-04 Thread Peter Hudec

Tried to install ovirt metrics, but got error

ANSIBLE_LOG_PATH=/tmp/ansible.log ansible-playbook -vvv -e
@/root/vars.yaml -i /root/ansible-inventory-origin-37-aio
playbooks/byo/config.yml

  1. Hosts:localhost
 Play: Determine openshift_version to configure on first master
 Task: For an RPM install, abort when the release requested does
not match the available version.
 Message:  You requested openshift_release 3.7, which is not matched by
   the latest OpenShift RPM we detected as origin-3.10.0
   on host localhost.
   We will only install the latest RPMs, so please ensure
you are getting the release
   you expect. You may need to adjust your Ansible
inventory, modify the repositories
   available on the host, or run the appropriate OpenShift
upgrade playbook.

regards
Peter

On 04/04/2018 09:13, Fred Rolland wrote:
> Hi,
> 
> Check these links:
> 
> https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
> https://ovirt.org/develop/release-management/features/metrics/metrics-store/
> 
> Regards,
> Fred
> 
> On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava
> >
> wrote:
> 
> Hi,
> 
> I see that oVirt DWH is installed with Version 4.2.x. Now, how do I
> take the reports? I version 3.5, we had Jasper reports module using
> which we could take utilization reports. Can we do something similar
> here?
> 
> -- 
> 
> Thanks & Regards,
> 
> 
> Anantha Raghava
> 
> 
> Do not print this e-mail unless required. Save Paper & trees.
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 

-- 
*Peter Hudec*
Infraštruktúrny architekt
phu...@cnc.sk 

*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2  35 000 100

Mobil:+421 905 997 203
*www.cnc.sk* 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

2018-04-04 Thread Fred Rolland

Hi,

Check these links:

https://ovirt.org/blog/2018/01/ovirt-report-using-grafana/
https://ovirt.org/develop/release-management/features/metrics/metrics-store/

Regards,
Fred

On Tue, Apr 3, 2018 at 9:38 AM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:

> Hi,
>
> I see that oVirt DWH is installed with Version 4.2.x. Now, how do I take
> the reports? I version 3.5, we had Jasper reports module using which we
> could take utilization reports. Can we do something similar here?
> --
>
> Thanks & Regards,
>
>
> Anantha Raghava
>
> Do not print this e-mail unless required. Save Paper & trees.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine-reports portal and cpu cores

2015-05-28 Thread Yaniv Dary




On 05/13/2015 10:49 AM, Alexandr Krivulya wrote:

Ок, I understand it. But in admin portal on hosts detail tab I see for
example 32 logical cores vs 16 in reports because of Hyper-Threading
enabled. All VM's on this host consumes 26 vCores. Does it
overallocation? According to report - yes, but actually I think not.

Can you clarify?

This article is good reading material for this:
http://wahlnetwork.com/2013/09/30/hyper-threading-gotcha-virtual-machine-vcpu-sizing/ 



It's still over allocation since you have more logical cores than 
physical, but it is weird that the database reports something different 
than the UI.
Eli, when hyper-threading is enabled, how is that saved in the database, 
does the UI display vale change, but the database values stay the same?





13.05.2015 10:32, Shirly Radco пишет:

H Alexandr,

The vCores are the logical cpu cores,
and if you has more vCores than Host Cores it means that you have over 
allocation for the hosts.
So, if on a specific vm one of the cores will be on 100% usage than all the vms 
using this core will show 100% as well.

Best,
---
Shirly Radco
BI Software Engineer
Red Hat Israel Ltd.



- Original Message -

From: Alexandr Krivulya shur...@shurik.kiev.ua
To: users@ovirt.org
Sent: Tuesday, May 12, 2015 3:30:32 PM
Subject: [ovirt-users] engine-reports portal and cpu cores

Hello,
why we have in reports host cores but not logical cpu cores? For example
in Cluster Capacity Vs. Usage report I always have more vCores then
Host Cores.
Thank you.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


--
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
  8272306
Email: yd...@redhat.com
IRC : ydary

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] engine-reports portal and cpu cores

2015-05-13 Thread Alexandr Krivulya

Ок, I understand it. But in admin portal on hosts detail tab I see for
example 32 logical cores vs 16 in reports because of Hyper-Threading
enabled. All VM's on this host consumes 26 vCores. Does it
overallocation? According to report - yes, but actually I think not.

Can you clarify?

13.05.2015 10:32, Shirly Radco пишет:
 H Alexandr,

 The vCores are the logical cpu cores, 
 and if you has more vCores than Host Cores it means that you have over 
 allocation for the hosts.
 So, if on a specific vm one of the cores will be on 100% usage than all the 
 vms using this core will show 100% as well.

 Best,
 --- 
 Shirly Radco 
 BI Software Engineer 
 Red Hat Israel Ltd.



 - Original Message -
 From: Alexandr Krivulya shur...@shurik.kiev.ua
 To: users@ovirt.org
 Sent: Tuesday, May 12, 2015 3:30:32 PM
 Subject: [ovirt-users] engine-reports portal and cpu cores

 Hello,
 why we have in reports host cores but not logical cpu cores? For example
 in Cluster Capacity Vs. Usage report I always have more vCores then
 Host Cores.
 Thank you.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] Engine reports

Re: [ovirt-users] engine-reports portal and cpu cores

Re: [ovirt-users] engine-reports portal and cpu cores

27 matches

Site Navigation

Mail list logo

Footer information