- Infra - oVirt List Archives

[CQ]: 106757, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106757,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106280,6 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106757/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19676/

1 0

[CQ]: 106797, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106797,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 104391,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106797/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19671/

1 0

[CQ]: 104222, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 104222,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 104391,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/104222/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19666/

1 0

[CQ]: 106787, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Feb '20

10 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106787,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106280,6 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106787/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19661/

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2861: ----------------------------------- Assignee: Barak Korren (was: infra) > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: Barak Korren > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2861 at 2/10/20 10:00 AM: --------------------------------------------------------------- I can see now that you don't have the gh-pages branch stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. was (Author: bkorren(a)redhat.com) I can see now that you don't have the gh-pages stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Barak Korren (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2861: ------------------------------------- I can see now that you don't have the gh-pages stored in Gerrit at all. What you need to do is first push the branch to Gerrit with a "normal" push (I assume you have a copy of it from GitHub), and after you've done that you can wort on it with patches just like you would on any other branch in Gerrit. The automated mirror process to GitHub should cause the pages to show up for your merged changes. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[CQ]: 106789,2 (ovirt-vmconsole) failed "ovirt-master" system tests
by oVirt Jenkins 10 Feb '20

10 Feb '20

Change 106789,2 (ovirt-vmconsole) 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/106789/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/19656/

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel commented on OVIRT-2861: --------------------------------- Just to be clear, I’ve pushed and merged patches to ovirt-engine-sdk freely using gerrit, the problem only happens to me with this branch, gh-pages. > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0

[JIRA] (OVIRT-2861) Requesting permission to ovirt-engine-sdk in Github
by Ori Liel (oVirt JIRA) 10 Feb '20

10 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2861?page=com.atlassian.jira.… ] Ori Liel commented on OVIRT-2861: --------------------------------- # git checkout gh-pages (gh-pages is a branch of ovirt-engine-sdk) # commit my changes locally # git push origin HEAD:refs/for/gh-pages Doesn’t work, says it doesn’t recognize the repository. or I’m not authorized. I’ve pushed patches to branches before this way, and it worked. So I asked the previous maintainer of the project what he thinks the problem may be. His answer was: I think you need to push it directly to github, not to gerrit That’s all I know > Requesting permission to ovirt-engine-sdk in Github > --------------------------------------------------- > > Key: OVIRT-2861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2861 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Ori Liel > Assignee: infra > Priority: High > > I'm a maintainer of ovirt-engine-sdk. > I'm able to merge changes to this repository through gerrit. > However, I don't have direct permissions for this repository on github. > Can I please be granted permissions for this repository Github? > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100119)

1 0