[ovirt-users] Re: [ANN] oVirt 4.4.1 Fourth Release Candidate is now available for testing

2020-06-14 Thread Glenn Marcy
This candidate changes the version of the OpenStack Java API from 3.2.8 to 
3.2.9, which isn't available in the repositories.
Installation produces the error:

[ ERROR ] fatal: [localhost -> ovirt-engine.example.com]: FAILED! => 
{"changed": false, "failures": [], "msg": "Depsolve Error occured: 
 Problem: cannot install the best candidate for the job
 - nothing provides openstack-java-cinder-client >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-cinder-model >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-client >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-glance-client >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-glance-model >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-keystone-client >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-keystone-model >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-quantum-client >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-quantum-model >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch
 - nothing provides openstack-java-resteasy-connector >= 3.2.9 needed by 
ovirt-engine-4.4.1.3-1.el8.noarch", "rc": 1, "results": []}

Regards,

Glenn Marcy


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


[ovirt-users] Re: Engine is one month ahead

2020-06-14 Thread Strahil Nikolov via Users
It seems that the current events are OK and have today's date.
The issue is that the Dashboard is showing events with filter '> Today' which 
also catches those events logged in July 2020.

I guess If I fix those (or just wait till July), the Dashboard won't show them 
any more.

Best Regards,
Strahil Nikolov






В неделя, 14 юни 2020 г., 11:41:36 ч. Гринуич+3, Strahil Nikolov 
 написа: 





Hello All,

I have a problem which started after the latest patching 4.3.9 to 4.3.10 .

Symptoms so far:
1. Engine reports that Hypervisours are drifting too much
2. ETL service stopped working
3. Web UI constantly notifies me that the nodes are again active (fills the 
screen till the bottom)

So far I have found an issue with one of the Hypervisours and after removing 
chrony's drift file and reboot - no more issues are observed.
I found in the DB that DWH last update was one month (yes, that's July) ahead , 
so updating it to June has fixed the ETL issue.
The problem with the constant "Host has been activated" was fixed by updating 
the Engine database , table Job (July was changed with June).


The only problem I have now is that every event in the Web (and in the DB of 
course) is pointing to July.

Any ideas how the engine is taking the time ,cause a restart doesn't fix the 
issue?

As you can see both Hypervisours and HE VM are OK:

[root@engine ~]# ntpdate -q time.cloudflare.com
server 162.159.200.1, stratum 3, offset 0.000816, delay 0.02812
server 162.159.200.123, stratum 3, offset 0.000939, delay 0.02834
14 Jun 11:40:05 ntpdate[30135]: adjust time server 162.159.200.1 offset 
0.000816 sec
[root@engine ~]# logout
Connection to engine closed.
[root@ovirt1 ~]# for i in ovirt{1..3} ; do ntpdate -q time.cloudflare.com ; done
server 162.159.200.123, stratum 3, offset 0.002658, delay 0.02948
server 162.159.200.1, stratum 3, offset 0.001741, delay 0.02768
14 Jun 11:40:24 ntpdate[29562]: adjust time server 162.159.200.1 offset 
0.001741 sec
server 162.159.200.1, stratum 3, offset 0.002529, delay 0.02914
server 162.159.200.123, stratum 3, offset 0.001931, delay 0.02788
14 Jun 11:40:31 ntpdate[29597]: adjust time server 162.159.200.123 offset 
0.001931 sec
server 162.159.200.123, stratum 3, offset 0.001765, delay 0.02742
server 162.159.200.1, stratum 3, offset 0.002551, delay 0.02924
14 Jun 11:40:37 ntpdate[29618]: adjust time server 162.159.200.123 offset 
0.001765 sec


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


[ovirt-users] Engine is one month ahead

2020-06-14 Thread Strahil Nikolov via Users
Hello All,

I have a problem which started after the latest patching 4.3.9 to 4.3.10 .

Symptoms so far:
1. Engine reports that Hypervisours are drifting too much
2. ETL service stopped working
3. Web UI constantly notifies me that the nodes are again active (fills the 
screen till the bottom)

So far I have found an issue with one of the Hypervisours and after removing 
chrony's drift file and reboot - no more issues are observed.
I found in the DB that DWH last update was one month (yes, that's July) ahead , 
so updating it to June has fixed the ETL issue.
The problem with the constant "Host has been activated" was fixed by updating 
the Engine database , table Job (July was changed with June).


The only problem I have now is that every event in the Web (and in the DB of 
course) is pointing to July.

Any ideas how the engine is taking the time ,cause a restart doesn't fix the 
issue?

As you can see both Hypervisours and HE VM are OK:

[root@engine ~]# ntpdate -q time.cloudflare.com
server 162.159.200.1, stratum 3, offset 0.000816, delay 0.02812
server 162.159.200.123, stratum 3, offset 0.000939, delay 0.02834
14 Jun 11:40:05 ntpdate[30135]: adjust time server 162.159.200.1 offset 
0.000816 sec
[root@engine ~]# logout
Connection to engine closed.
[root@ovirt1 ~]# for i in ovirt{1..3} ; do ntpdate -q time.cloudflare.com ; done
server 162.159.200.123, stratum 3, offset 0.002658, delay 0.02948
server 162.159.200.1, stratum 3, offset 0.001741, delay 0.02768
14 Jun 11:40:24 ntpdate[29562]: adjust time server 162.159.200.1 offset 
0.001741 sec
server 162.159.200.1, stratum 3, offset 0.002529, delay 0.02914
server 162.159.200.123, stratum 3, offset 0.001931, delay 0.02788
14 Jun 11:40:31 ntpdate[29597]: adjust time server 162.159.200.123 offset 
0.001931 sec
server 162.159.200.123, stratum 3, offset 0.001765, delay 0.02742
server 162.159.200.1, stratum 3, offset 0.002551, delay 0.02924
14 Jun 11:40:37 ntpdate[29618]: adjust time server 162.159.200.123 offset 
0.001765 sec


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


[ovirt-users] Re: ovirt 4.3.10 Web UI constantly "finished activating host"

2020-06-14 Thread Strahil Nikolov via Users
Hey Didi,

it seems that there is still timeshift in the DB - lots of stuff was reporting 
ahead of time.

I had to update the table jobs with the correct month and now at least I have 
no more spam in the web ui.

Best Regards,
Strahil Nikolov






В четвъртък, 11 юни 2020 г., 9:39:45 ч. Гринуич+3, Yedidyah Bar David 
 написа: 





On Thu, Jun 11, 2020 at 6:55 AM Strahil Nikolov via Users

 wrote:
>
> I'm not sure if this one is related to "time shift" in the DB (as I found 
> that dwh_history_timekeeping had some entries 1 month ahead/ETL service 
> issues also/, but I keep getting spammed that the host has been activated.
>
>
> Any hint ?


I'd start with:

1. Check (in /var/log) if you had a case of time moving forward and
than backward for some weird reason

2. Dump the entire db (engine, perhaps also dwh if you want) and
search for future dates. If you only find a few, it might be easier to
handle them one-by-one (hopefully by updating the relevant entity from
the UI, not directly in the db). If it's many, it might require
something more significant.

In 4.4, that's just:

su - postgres -c 'pg_dump engine' | less

In 4.3:

su - postgres -c 'scl enable rh-postgresql10 "pg_dump engine"' | less

Then search e.g. '2020-07', or '2020-06-2', etc.

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