[JIRA] (OVIRT-2540) improving the upgrade suites
by Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2540?page=com.atlassian.jir... ]
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)
5 years, 1 month
[JIRA] (OVIRT-2566) make network suite blocking
by Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ]
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-te...
> 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)
5 years, 1 month
[JIRA] (OVIRT-2446) Github push trigger will fail if was trigger by
a tag push
by Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2446?page=com.atlassian.jir... ]
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-o...
> - 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)
5 years, 1 month