[JIRA] (OVIRT-1288) Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1288?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-1288:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once
> --------------------------------------------------------------------------------------------
>
> Key: OVIRT-1288
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Gerrit/git
> Reporter: Barak Korren
> Assignee: Evgheni Dereveanchin
>
> Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once.
> I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none.
> This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jir... ]
Evgheni Dereveanchin updated OVIRT-1295:
----------------------------------------
Priority: Low (was: Medium)
> Add job to auto-rebase patches that are ready to be merged
> -----------------------------------------------------------
>
> Key: OVIRT-1295
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: eedri
> Assignee: infra
> Priority: Low
>
> We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts.
> A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI.
> This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases.
> [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything.
> Initially we'll try enabling it for ovirt-engine on 4.1 branch.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jir... ]
Evgheni Dereveanchin updated OVIRT-1312:
----------------------------------------
Epic Link: OVIRT-400 (was: OVIRT-403)
> Make 'scan_for_artifacts.sh' publish repos separately
> -----------------------------------------------------
>
> Key: OVIRT-1312
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: infra
>
> The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions.
> The issue is that if one of the repos fails to sync, the rest do not get synced either.
> We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jir... ]
Evgheni Dereveanchin updated OVIRT-1312:
----------------------------------------
Epic Link: OVIRT-400 (was: OVIRT-403)
> Make 'scan_for_artifacts.sh' publish repos separately
> -----------------------------------------------------
>
> Key: OVIRT-1312
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: infra
>
> The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions.
> The issue is that if one of the repos fails to sync, the rest do not get synced either.
> We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1334) Setup a cleanup job for the mirrors
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1334?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-1334:
-------------------------------------------
Assignee: Barak Korren (was: infra)
> Setup a cleanup job for the mirrors
> -----------------------------------
>
> Key: OVIRT-1334
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1334
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: Barak Korren
>
> Out transactional mirrors do not currently have a cleanup job. This means packages are kept forever, or at least until specific mirrors are removed.
> This means we may run out of space.
> Need to first verify this is actually needed in practice once OVIRT-1332 and OVIRT-1333 are implemented.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months
[JIRA] (OVIRT-1387) change gateway IP on PHX HE hypervisors
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1387?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-1387:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> change gateway IP on PHX HE hypervisors
> ---------------------------------------
>
> Key: OVIRT-1387
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1387
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Evgheni Dereveanchin
> Assignee: Evgheni Dereveanchin
>
> We have an incorrect gateway set in HA configs of ovirt-srv01, ovirt-srv02 and ovirt-srv03v which can cause issues like the ones described in OVIRT-1369
> During the next host update window we need to edit /etc/ovirt-hosted-engine/hosted-engine.conf and change the gateway before rebooting. This has to be done in global maintenance to avoid unnecessary Engine restarts.
--
This message was sent by Atlassian JIRA
(v1000.1092.0#100053)
7 years, 4 months