- Infra - oVirt List Archives

Network test that randomly fails on CI
by Ala Hino 10 Jun '18

10 Jun '18

Hi, From time to time, I see the following failure of a network test. I understood from Ed that it is a CI known issue. Would appreciate if this can be fixed ASAP. Thanks. *09:59:56* self = <network.integration.ovs.ovs_info_test.TestOvsInfo testMethod=test_ovs_info_with_sb_nic>*09:59:56* *09:59:56* def test_ovs_info_with_sb_nic(self):*09:59:56* with dummy_device() as nic:*09:59:56* > with _setup_ovs_network(self.ovsdb, nic):*09:59:56* *09:59:56* network/integration/ovs/ovs_info_test.py:78: *09:59:56* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *09:59:56* /usr/lib64/python2.7/contextlib.py:17: in __enter__*09:59:56* return self.gen.next()*09:59:56* network/integration/ovs/ovs_info_test.py:63: in _setup_ovs_network*09:59:56* t.add(*_northbound_port())*09:59:56* ../lib/vdsm/network/ovs/driver/__init__.py:46: in __exit__*09:59:56* self.result = self.commit()*09:59:56* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *09:59:56* *09:59:56* self = <vdsm.network.ovs.driver.vsctl.Transaction object at 0x7fdbab22db50>*09:59:56* *09:59:56* def commit(self):*09:59:56* if not self.commands:*09:59:56* return*09:59:56* *09:59:56* timeout_option = []*09:59:56* if self.timeout:*09:59:56* timeout_option = ['--timeout=' + str(self.timeout)]*09:59:56* *09:59:56* args = []*09:59:56* for command in self.commands:*09:59:56* args += ['--'] + command.cmd*09:59:56* exec_line = [_ovs_vsctl_cmd()] + timeout_option + OUTPUT_FORMAT + args*09:59:56* logging.debug('Executing commands: %s' % ' '.join(exec_line))*09:59:56* *09:59:56* rc, out, err = netcmd.exec_sync(exec_line)*09:59:56* if rc != 0:*09:59:56* err = err.splitlines()*09:59:56* if OvsDBConnectionError.is_ovs_db_conn_error(err):*09:59:56* raise OvsDBConnectionError('\n'.join(err))*09:59:56* else:*09:59:56* raise ConfigNetworkError(*09:59:56* ne.ERR_BAD_PARAMS,*09:59:56* > 'Executing commands failed: %s' % '\n'.join(err))*09:59:56* E ConfigNetworkError: (21, 'Executing commands failed: ovs-vsctl: cannot create a bridge named vdsmbr_test because a bridge named vdsmbr_test already exists')*09:59:56* *09:59:56* ../lib/vdsm/network/ovs/driver/vsctl.py:78: ConfigNetworkError

2 3

[JIRA] (OVIRT-2156) create gerrit repo: ovirt-engine-ui-extensions
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2156?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2156: -------------------------------- Assignee: Gal Ben Haim (was: infra) > create gerrit repo: ovirt-engine-ui-extensions > ---------------------------------------------- > > Key: OVIRT-2156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2156 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Gal Ben Haim > > Hi, > Please create ovirt-engine-ui-extensions in gerrit, mirrored to github > It can have the same people + permissions as ovirt-engine-dashboard (it > will probably replace ovirt-engine-dashbaord) > Best wishes, > Greg > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2176: ------------------------------------- Actually I think the user story is quite simple here - "As an ovirt developer, I would like to know as early as possible if platform changes are going to break oVirt so that I can react to them in a timely manner". Or perhaps its "As a platform component developer I would like to know if changes I make are causing issues in oVirt as early as possible so I can eliminate those issues as early as possible and have newer version of my component be adopted by oVirt". Actually which one of the two stories above we decide to aim for has significant influence on the kind of implementation we aim for. > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2164: ---------------------------------- [~ena(a)redhat.com] since you moved Python-Errata, do you think you can handle moving repoman as well? [~amarchuk] WDYT? > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- [~amarchuk] FYI > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- People want to run Lago on their FC28, so its quite important we'll prioritize it. > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2163: ----------------------------- Priority: Highest (was: Medium) > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- [~ena(a)redhat.com] is that something you can do? did you have time to go over repoman a bit? > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2176: ----------------------------- Epic Link: OVIRT-400 > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

eyal edri created OVIRT-2176: -------------------------------- Summary: oVirt CI should support fast moving platform releases Key: OVIRT-2176 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri Assignee: infra It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0