[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-903:
-------------------------------------------------
well, depending on the amount of effort needed to update the job, we
might want to wait with it until the jobs are moved to an ost suit, which
is in progress.
On Dec 4, 2016 13:07, "Yedidyah Bar David" <didi(a)redhat.com> wrote:
On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt
atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=23805#comment-23805 ]
from-master_el7_merged/
Indeed, and I explained in the ticket why it's not enough as-is.
Best,
--
Didi
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
> master-to-master CI upgrade tests
> ---------------------------------
>
> Key: OVIRT-903
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> Recently a patch to the engine [1] added a new package,
> with a certain set of dependencies, which broke upgrade.
> This is similar to [2] but for a new package.
> CI wasn't affected, I think because of [3].
> To make CI test such flows, we should have a job that:
> 1. Builds, installs and sets up the version we want to test
> 2. Pushes a dummy change to the local git repo (to force
> a new version), build the patched tree, create a yum repo
> with the build and add it to yum.repos.d.
> 3. yum update
> 4. engine-setup
> Another option is to revert [3], or to duplicate - have
> both "upgrade current to self" and "upgrade latest snapshot
> to current". The downside is that it will be checked later
> than above plan - instead of in the same build, will only
> be tested in the first build that uses the snapshot after
> it was updated, and also will be misleading, as the reason
> why that job failed will not be apparent (which was why
> [3] was added).
> Please handle. I can of course try to help. Best,
> [1] https://gerrit.ovirt.org/66999
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249
> [3] https://gerrit.ovirt.org/67263
> --
> Didi
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
Re: [JIRA] (OVIRT-903) master-to-master CI upgrade tests
by Eyal Edri
well, depending on the amount of effort needed to update the job, we
might want to wait with it until the jobs are moved to an ost suit, which
is in progress.
On Dec 4, 2016 13:07, "Yedidyah Bar David" <didi(a)redhat.com> wrote:
On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt
JIRA) <jira(a)ovirt-jira.atlassian.net> wrote:
>
> [ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.
atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=23805#comment-23805 ]
>
> eyal edri [Administrator] commented on OVIRT-903:
> -------------------------------------------------
>
> We have master->master upgrade job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-
from-master_el7_merged/
Indeed, and I explained in the ticket why it's not enough as-is.
Best,
--
Didi
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
7 years, 5 months
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by Yedidyah Bar David (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira... ]
Yedidyah Bar David commented on OVIRT-903:
------------------------------------------
On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt
Indeed, and I explained in the ticket why it's not enough as-is.
Best,
--
Didi
> master-to-master CI upgrade tests
> ---------------------------------
>
> Key: OVIRT-903
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> Recently a patch to the engine [1] added a new package,
> with a certain set of dependencies, which broke upgrade.
> This is similar to [2] but for a new package.
> CI wasn't affected, I think because of [3].
> To make CI test such flows, we should have a job that:
> 1. Builds, installs and sets up the version we want to test
> 2. Pushes a dummy change to the local git repo (to force
> a new version), build the patched tree, create a yum repo
> with the build and add it to yum.repos.d.
> 3. yum update
> 4. engine-setup
> Another option is to revert [3], or to duplicate - have
> both "upgrade current to self" and "upgrade latest snapshot
> to current". The downside is that it will be checked later
> than above plan - instead of in the same build, will only
> be tested in the first build that uses the snapshot after
> it was updated, and also will be misleading, as the reason
> why that job failed will not be apparent (which was why
> [3] was added).
> Please handle. I can of course try to help. Best,
> [1] https://gerrit.ovirt.org/66999
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249
> [3] https://gerrit.ovirt.org/67263
> --
> Didi
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-903:
-------------------------------------------------
We have master->master upgrade job:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_...
> master-to-master CI upgrade tests
> ---------------------------------
>
> Key: OVIRT-903
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi all,
> Recently a patch to the engine [1] added a new package,
> with a certain set of dependencies, which broke upgrade.
> This is similar to [2] but for a new package.
> CI wasn't affected, I think because of [3].
> To make CI test such flows, we should have a job that:
> 1. Builds, installs and sets up the version we want to test
> 2. Pushes a dummy change to the local git repo (to force
> a new version), build the patched tree, create a yum repo
> with the build and add it to yum.repos.d.
> 3. yum update
> 4. engine-setup
> Another option is to revert [3], or to duplicate - have
> both "upgrade current to self" and "upgrade latest snapshot
> to current". The downside is that it will be checked later
> than above plan - instead of in the same build, will only
> be tested in the first build that uses the snapshot after
> it was updated, and also will be misleading, as the reason
> why that job failed will not be apparent (which was why
> [3] was added).
> Please handle. I can of course try to help. Best,
> [1] https://gerrit.ovirt.org/66999
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249
> [3] https://gerrit.ovirt.org/67263
> --
> Didi
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-900:
-------------------------------------------------
If he has merge rights on master, then yes.
Maybe its a good idea to ask the vdsm maintainers who should have merge rights on master ( i.e belongs in the master maintainers group )
> Re: Rebase over other author's patch cannot be pushed to gerrit
> ---------------------------------------------------------------
>
> Key: OVIRT-900
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Barak Korren
> Assignee: Shlomo Ben David
>
> Forwarding to infra-support.
> On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote:
> > Not sure since when it was changed, but I noticed that I can't push patches
> > if I'm not the author
> >
> > Counting objects: 50, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (50/50), done.
> > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done.
> > Total 50 (delta 34), reused 0 (delta 0)
> > remote: Resolving deltas: 100% (34/34)
> > remote: Processing changes: refs: 1, done
> > remote:
> > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4
> > remote: ERROR: author email address rnachimu(a)redhat.com
> > remote: ERROR: does not match your user account.
> > remote: ERROR:
> > remote: ERROR: The following addresses are currently registered:
> > remote: ERROR: bronhaim(a)gmail.com
> > remote: ERROR: ybronhei(a)redhat.com
> > remote: ERROR:
> > remote: ERROR: To register an email address, please visit:
> > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact
> > remote:
> > remote:
> > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm
> > ! [remote rejected] HEAD -> refs/for/master (invalid author)
> > error: failed to push some refs to
> > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm'
> >
> > We must have permissions to do that, this is part of the rebasing part, and
> > I think its fine to fix patches on behalf of someone else.. but its not the
> > best practice for reviewing.
> > anyway, please undo this change, unless its something that related only to
> > my env.. let me know
> >
> > Thanks
> >
> > --
> > Yaniv Bronhaim.
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
[JIRA] (OVIRT-896) Re: Jenkins issues
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-896?page=com.atlassian.jira... ]
eyal edri [Administrator] reassigned OVIRT-896:
-----------------------------------------------
Assignee: Shlomo Ben David (was: infra)
Please try to help [~fdeutsch] debug the issue
> Re: Jenkins issues
> ------------------
>
> Key: OVIRT-896
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-896
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Shlomo Ben David
>
> better to send such info to infra-support to document as a ticket. ( adding
> infra-support )
> On Thu, Dec 1, 2016 at 12:22 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote:
> > Hey,
> >
> > so - I have an issue
> > this job:
> > is often picking a wrong commit!
> > http://jenkins.ovirt.org/user/fabiand/my-views/view/ovirt-
> > node-ng/job/ovirt-node-ng_master_build-artifacts-el7-
> > x86_64/219/consoleFull
> >
> > It says it resetted to master, but master is actually a different commit.
> > I observed this a few times in the recent days.
> >
> > Does somebody have an idea why this could be happening?
> >
> > 00:00:02.156 Checking out Revision
> > c1970c6f7a6404e8ab030147eec81233905345cf (origin/master)
> >
> > on my local host:
> > $ git rev-parse FETCH_HEAD^{commit} # timeout=10
> > 9123c1fd3ce15b02f2e69efdc367ae1477193aef
> >
> > c1970c6f7a6404e8ab030147eec81233905345cf -- does actually no exist (in
> > my history)
> >
> > - fabian
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by Shlomo Ben David (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira... ]
Shlomo Ben David commented on OVIRT-900:
----------------------------------------
Hi,
Nope, the 'Forge author Identity' is set specifically with the following
permissions:
'vdsm-master-maintainers' group for the 'master' branch
'vdsm-stable-maintainers' group for 'stable' branches
- The user ybronhei(a)redhat.com is a member of 'vdsm-stable-maintainers'
and 'vdsm-arch-dependencies' groups
- The user is not a member of 'vdsm-master-maintainers' group.
Should I add him to the 'vdsm-master-maintainers' group?
Best Regards,
Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL
RHCSA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
On Thu, Dec 1, 2016 at 6:17 PM, eyal edri [Administrator] (oVirt JIRA) <
> Re: Rebase over other author's patch cannot be pushed to gerrit
> ---------------------------------------------------------------
>
> Key: OVIRT-900
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Barak Korren
> Assignee: Shlomo Ben David
>
> Forwarding to infra-support.
> On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote:
> > Not sure since when it was changed, but I noticed that I can't push patches
> > if I'm not the author
> >
> > Counting objects: 50, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (50/50), done.
> > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done.
> > Total 50 (delta 34), reused 0 (delta 0)
> > remote: Resolving deltas: 100% (34/34)
> > remote: Processing changes: refs: 1, done
> > remote:
> > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4
> > remote: ERROR: author email address rnachimu(a)redhat.com
> > remote: ERROR: does not match your user account.
> > remote: ERROR:
> > remote: ERROR: The following addresses are currently registered:
> > remote: ERROR: bronhaim(a)gmail.com
> > remote: ERROR: ybronhei(a)redhat.com
> > remote: ERROR:
> > remote: ERROR: To register an email address, please visit:
> > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact
> > remote:
> > remote:
> > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm
> > ! [remote rejected] HEAD -> refs/for/master (invalid author)
> > error: failed to push some refs to
> > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm'
> >
> > We must have permissions to do that, this is part of the rebasing part, and
> > I think its fine to fix patches on behalf of someone else.. but its not the
> > best practice for reviewing.
> > anyway, please undo this change, unless its something that related only to
> > my env.. let me know
> >
> > Thanks
> >
> > --
> > Yaniv Bronhaim.
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> --
> Barak Korren
> bkorren(a)redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months
[JIRA] (OVIRT-871) unrelated CI failure
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-871?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-871:
--------------------------------------------
Resolution: Fixed
Status: Done (was: To Do)
We had an issue with the artifactory server which was resolved.
> unrelated CI failure
> --------------------
>
> Key: OVIRT-871
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-871
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: danken
> Assignee: infra
>
> Change https://gerrit.ovirt.org/#/c/67101/ just failed on
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/...
> which I believe is utterly unrelated to the patch. please resolved the underlying problem.
> [ERROR] Failed to execute goal on project restapi-definition: Could not resolve dependencies for project org.ovirt.engine.api:restapi-definition:jar:4.1.0-SNAPSHOT: Failed to collect dependencies at org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Failed to read artifact descriptor for org.ovirt.engine.api:metamodel-runtime:jar:1.1.8: Could not transfer artifact org.ovirt.engine.api:metamodel-runtime:pom:1.1.8 from/to ovirt-maven-repository (http://artifactory.ovirt.org/artifactory/ovirt-mirror): Failed to transfer file: http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/ovirt/engine/ap.... Return code is: 502 , ReasonPhrase:Proxy Error. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce...
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :restapi-definition
> Makefile:256: recipe for target 'maven' failed
> make[1]: *** [maven] Error 1
> make[1]: Leaving directory '/home/jenkins/workspace/ovirt-engine_master_check-patch-fc24-x86_64/ovirt-engine/rpmbuild/BUILD/ovirt-engine-4.1.0'
> Makefile:263: recipe for target 'tmp.built' failed
> make: *** [tmp.built] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.2ykGhi (%build)
--
This message was sent by Atlassian JIRA
(v1000.610.2#100023)
7 years, 5 months