- Infra - oVirt List Archives

[JIRA] (OVIRT-2038) oVirt dashboard is not being updated
by Marc Dequènes (Duck) (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2038?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-2038: --------------------------------------------- The redirection is done. The cleanup needs review here: https://github.com/oVirt/ovirt-site/pull/1624 > oVirt dashboard is not being updated > ------------------------------------ > > Key: OVIRT-2038 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2038 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: signature.asc, signature.asc, signature.asc > > > Hi, > looking at https://ovirt.org/dashboard/ I see that latest data are from > March while http://ovirt.biterg.io/ is updated to today. > Can you please check what's got broken in data retrieval from bitergia? > Thanks, > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://redhat.com/summit> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2038) oVirt dashboard is not being updated
by Marc Dequènes (Duck) (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2038?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2038: ---------------------------------------- Attachment: signature.asc On 05/21/2018 10:41 PM, Brian Proffitt wrote: > By all means, you don't need my clearance for this. This also affects RDO, Gluster and probably not anymore ManageIQ. And this means the Community.rh.c dashboard is also to be replaced. > oVirt dashboard is not being updated > ------------------------------------ > > Key: OVIRT-2038 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2038 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: signature.asc, signature.asc, signature.asc > > > Hi, > looking at https://ovirt.org/dashboard/ I see that latest data are from > March while http://ovirt.biterg.io/ is updated to today. > Can you please check what's got broken in data retrieval from bitergia? > Thanks, > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://redhat.com/summit> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by eyal edri (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1759: ---------------------------------- I think we've seen it so far only on vdsm-jsonrpc-java, but maybe I'm not aware of all the incidents. Also, differ between the old way we published in 4.1 ( copy from job ) and the new flow in 4.2 with CQ, which is a different issue than before. I think 1 hour should suffice, but it depends on how loaded the CQ is, [~bkorren(a)redhat.com] any thoughts? > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Piotr Kliczewski (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Piotr Kliczewski commented on OVIRT-1759: ----------------------------------------- [mailto:eedri@redhat.com] I do not think it is related only to vdsm-jsonrpc-java and it my opinion it can happen for anyone. In general I give couple of hrs between merging jsonrpc version update patch and the engine patch. Do you have any specific time in your mind for how long should I wait? > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by eyal edri (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1759: ---------------------------------- [~pkliczew(a)redhat.com] since this issue only happened with vdsm-jsonrpc-java AFAIK, due to its tight integration with engine, How often would you say such issue happens? can we allow for a delay between version bumps patches of the project to try and avoid it until we implement a permenant solution? > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2044) Drop oVirt 4.1 resources from CI
by Barak Korren (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2044?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2044: ----------------------------------- Assignee: Barak Korren (was: infra) > Drop oVirt 4.1 resources from CI > -------------------------------- > > Key: OVIRT-2044 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2044 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: Barak Korren > > Tracker ticket from dropping all resources relating to the now EOLed oVirt 4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2044) Drop oVirt 4.1 resources from CI
by Barak Korren (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2044?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2044: -------------------------------- Epic Link: OVIRT-400 > Drop oVirt 4.1 resources from CI > -------------------------------- > > Key: OVIRT-2044 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2044 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Tracker ticket from dropping all resources relating to the now EOLed oVirt 4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2044) Drop oVirt 4.1 resources from CI
by Barak Korren (oVirt JIRA) 21 May '18

21 May '18

Barak Korren created OVIRT-2044: ----------------------------------- Summary: Drop oVirt 4.1 resources from CI Key: OVIRT-2044 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2044 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI client projects Reporter: Barak Korren Assignee: infra Tracker ticket from dropping all resources relating to the now EOLed oVirt 4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2043) hyperkitty not showing replies
by eyal edri (oVirt JIRA) 21 May '18

21 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2043?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2043: -------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > hyperkitty not showing replies > ------------------------------ > > Key: OVIRT-2043 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2043 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Marc Dequènes (Duck) > > Hi, > It looks like hyperkitty has stopped threading / grouping together newer > threads. It's showing the original, but not replies. > Here is an example where there are replies, but they don't show in the UI: > https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/UGGNDS4SVJ2GHA… > But older ones in that list do show all replies. > Am I doing something wrong, or is this a list issue? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2043) hyperkitty not showing replies
by Greg Sheremeta (oVirt JIRA) 21 May '18

21 May '18

Greg Sheremeta created OVIRT-2043: ------------------------------------- Summary: hyperkitty not showing replies Key: OVIRT-2043 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2043 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, It looks like hyperkitty has stopped threading / grouping together newer threads. It's showing the original, but not replies. Here is an example where there are replies, but they don't show in the UI: https://lists.ovirt.org/archives/list/devel@ovirt.org/thread/UGGNDS4SVJ2GHA… But older ones in that list do show all replies. Am I doing something wrong, or is this a list issue? -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0