August 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2078: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Eyal Edri > Assignee: Evgheni Dereveanchin > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2540) improving the upgrade suites
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2540?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2540: -------------------------------- Assignee: Galit Rosenthal (was: infra) > improving the upgrade suites > ----------------------------- > > Key: OVIRT-2540 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2540 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Galit Rosenthal > Priority: High > > our upgrade suites are testing engine upgrade with no objects created pre upgrade and after upgrade are running a basic sanity test. > 1. upgrade should not take more then basic sanity and as we are running both for the upgrade suite we need to change it > 2. we are not testing vdsm/host upgrade and we are also not testing basic objects upgrade > the upgrade suites should be modified. > [~mwperina] said he would write a design and until we have modified the test-cases we should perhaps stop running upgrade on every run as I do not think its contributing to our testing. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2566: ---------------------------------- we can consider this once we enable zuul/patch gating. [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] will we be able to enable network suite for gating network patches? > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2757) Re: Jenkins Developer group
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2757?page=com.atlassian.jira.… ] Eyal Edri closed OVIRT-2757. ---------------------------- Resolution: Fixed > Re: Jenkins Developer group > --------------------------- > > Key: OVIRT-2757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2757 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > Adding infra-support to generate a ticket. > > On 16 Jul 2019, at 13:34, Andrej Cernek <acernek(a)redhat.com> wrote: > > > > Hi, > > I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. > > Thank you > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/O4RERPUWYX2ZP… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2446) Github push trigger will fail if was trigger by a tag push
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2446?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2446: ----------------------------- Status: To Do (was: Blocked) > Github push trigger will fail if was trigger by a tag push > ---------------------------------------------------------- > > Key: OVIRT-2446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2446 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roy Golan > Assignee: infra > > When pushing a tag to a GH it triggers the jenkins webhook. In the invoked > job, > it will try to fech a new head with that tag, but that will fail since the > repo doesn't have > a head since it is started as git init. > A breakdown from > https://jenkins.ovirt.org/job/oVirt_ovirt-openshift-extensions_standard-on-… > - git init a repo > *14:57:15* > git init > /home/jenkins/workspace/oVirt_ovirt-openshift-extensions_standard-on-ghpush/ovirt-openshift-extensions > # timeout=10 > - git fetch tags (maybe the problem is here as it doesn't reffer to refs/tags) > *15:35:07* [check-merged.el7.x86_64] > git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/* > - fetch upstream changes, which is here a tag v0.3.2, so it uses > 'refs/tags/v0.3.2' > *14:57:18* > git fetch --tags --progress > https://github.com/oVirt/ovirt-openshift-extensions > +refs/tags/v0.3.2:myhead > This fails with > *14:57:19* stderr: error: cannot update ref 'refs/heads/myhead': > trying to write non-commit object > 3c7b5a5d243d1f3bcecbe7b527726b06113d0ec5 to branch 'refs/heads/myhead' > While in regular merge with a tag on it uses 'refs/heads/master': > *15:35:10* [check-merged.el7.x86_64] > git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/master:myhead > Since refs/tags/v0.3.2 doesn't exist locally it can't reference it. Since > refs/heads/master exists locally it can create the alias 'myhead' to it. > I would like to have the option to push a tag and trigger a build but this > is not working atm without a commit attached to it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2294) HC symlinks to deployment scripts
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2294?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2294: ---------------------------------- [~accountid:5b25ec3f8b08c009c48b25c9] can you add info on this? is it still needed? > HC symlinks to deployment scripts > ---------------------------------- > > Key: OVIRT-2294 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2294 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Components: OST > Reporter: Galit Rosenthal > Assignee: infra > > HC - create symlinks for deployment scripts -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2695: ----------------------------- Resolution: Fixed Status: Done (was: Blocked) > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[CQ]: 102841, 26 (ovirt-node-coreos) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

Change 102841,26 (ovirt-node-coreos) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/102841/26 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15607/

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2785: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch
by Dafna Ron (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2785: ---------------------------------- any time 🙂 > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0