[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1412?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1412:
-----------------------------------
Assignee: Barak Korren (was: infra)
> mock_runner root cache only holds for one day
> ---------------------------------------------
>
> Key: OVIRT-1412
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: Barak Korren
>
> It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it.
> As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned.
> We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script.
--
This message was sent by Atlassian JIRA
(v1000.1010.1#100044)
7 years, 5 months
[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1412:
-----------------------------------
Summary: mock_runner root cache only holds for one day
Key: OVIRT-1412
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it.
As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned.
We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script.
--
This message was sent by Atlassian JIRA
(v1000.1010.1#100044)
7 years, 5 months
[JIRA] (OVIRT-1412) mock_runner root cache only holds for one day
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1412?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1412:
--------------------------------
Epic Link: OVIRT-400
> mock_runner root cache only holds for one day
> ---------------------------------------------
>
> Key: OVIRT-1412
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1412
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
>
> It turns out that 'mock' check the timestamp on the mock cache and compares it with the timestamp on the mock configuration file. If the cache is older, mock removes it.
> As a work-around for that, mock_runner includes a '{{touch}}' command that changes the timestamp on the mock configuration file to be a day older then the current time. Once the cache becomes older then a day it should also become older then the configuration file and therefore cleaned.
> We need to change this so that instead of touching the configuration file we will touch the cache itself to ensure it is newer. That will guarantee the cache will stick around and will be used until it is erased by our cleanup script.
--
This message was sent by Atlassian JIRA
(v1000.1010.1#100044)
7 years, 5 months
Gerrit HTTP-500 error
by Gil Shinar
Hi,
Today we have seen this error again. Restart of Gerrit fixed this issue.
I have look a bit and found the following thread:
https://groups.google.com/forum/#!topic/repo-discuss/N5bIo4VlPGU
According to the above, there's a bug in Jgit. Its cache gets corrupted and
it cannot find objects.
Restart of Gerrit causes it to clear the cache and that fixes the problem.
In order to fix that, you cannot only upgrade JGit (as it is built in
inside Gerrit installation) but you have to upgrade Gerrit. According to
Gerrit's release notes, this issue had been fixed only since Gerrit 2.13.7
<https://www.gerritcodereview.com/releases/2.13.md#2.13.7>
It is not urgent but looks like a good idea to upgrade to this version or
the latest (2.13.8).
Gil
7 years, 5 months