June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2093: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

Barak Korren created OVIRT-2093: ----------------------------------- Summary: Add OST 4.2 -> 4.2 upgrade suit Key: OVIRT-2093 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Barak Korren Assignee: infra Priority: High OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2093: -------------------------------- Epic Link: OVIRT-2091 > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: infra > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

Dafna Ron created OVIRT-2092: -------------------------------- Summary: standard-enqueue 4.2 not running Key: OVIRT-2092 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… but the tested is showing that it only ran once (yesterday): http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… and "next test" job is showing empty queue: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91899,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Jun '18

04 Jun '18

Change 91899,3 (ovirt-engine) 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/91899/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8029/

1 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2078: ------------------------------------- What is the use case? Can we put this in terms of a user story? > 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: infra > 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#100086)

1 0

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2076: ---------------------------------- [~stirabos(a)redhat.com] can you please add some info on how is the change resolved this error and if it it would effect any other projects? > name clash on vdsm module at host-deploy > ---------------------------------------- > > Key: OVIRT-2076 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > Add host is failing and was reported by gal for hc > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > (Relevant) error snippet from the host deploy log: > <error> > 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None) > 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported > 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf > _('Cannot resolve ovirt_hosted_engine_ha module') > RuntimeError: Cannot resolve ovirt_hosted_engine_ha module -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2074) missing dependency for python-isort
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2074?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2074: ---------------------------------- [~sbonazzo(a)redhat.com] can you please update on the status of the bug and when should we see this resolved? > missing dependency for python-isort > ----------------------------------- > > Key: OVIRT-2074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2074 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures > > need to change fc27 to fc28 to fix the failures. > Sandro submitted a change for some projects but some are still missing. > Sandro: > Fix is here: https://gerrit.ovirt.org/91769 ; needs an engine to be built on fedora to pass CI, I'm on it. > Going on failures, I will help him with the change for failed projects build-artifacts with the same issue. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1549: ---------------------------------- The repo you provided has an 'openstack-netron-openvswitch' pkg, so we can't use it because it has different naming that what oVirt uses right? Is there a different repo that has nightly builds or something similar that can we used in OST? > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2054: ----------------------------- Labels: ost_failures ost_race (was: ost_failures) > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0