- Infra - oVirt List Archives

[JIRA] (OVIRT-729) Jenkins leaves behind connections in ESTABLISHED state
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-729?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-729: -------------------------------------------- Epic Link: OVIRT-403 > Jenkins leaves behind connections in ESTABLISHED state > ------------------------------------------------------ > > Key: OVIRT-729 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-729 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Throughout the last days I noticed several times when a slave got non-responsive and after rebooting it never recovered until being removed/re-added to Jenkins. > Further investigation on el7-vm06.phx.ovirt.org revealed that on Jenkins the connection is still marked as "ESTABLISHED" hours after the slave crashed and rebooted: > {quote} > tcp6 0 0 66.187.230.92:33374 66.187.230.77:22 ESTABLISHED 14625/java > {quote} > Due to this new SSH connections are not opened and Jenkins can't reconnect to the slave. > I didn't see this behavior before, maybe it is related to the latest security upgrade of jenkins. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-725) install secondary MX server
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-725?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-725: -------------------------------------------- Epic Link: OVIRT-403 > install secondary MX server > --------------------------- > > Key: OVIRT-725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-725 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Mailing lists (Mailman) > Reporter: Evgheni Dereveanchin > Assignee: infra > > We currently just have a single MX record and mail server. For better reliability it's a good idea to set up a secondary MX that would act as a relay. This can help during primary MX maintenance as mail will be accumulated on the secondary MX and flushed to the primary once that comes up. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-516) Yamlize jenkins-old.ovirt.org jobs
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-516?page=com.atlassian.jira.p… ] eyal edri [Administrator] closed OVIRT-516. ------------------------------------------- > Yamlize jenkins-old.ovirt.org jobs > ---------------------------------- > > Key: OVIRT-516 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-516 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: Nadav Goldin > Assignee: infra > Labels: jenkins, jobs > Fix For: OVIRT-INFRA-JUN-2016 > > > This ticket is for tracking none-yamlized jobs we have left in http://jenkins-old.ovirt.org and should be yamlized. > h5. Confirmed needed(and should be enabled in jenkins-old) > # manual build jobs ( we need to think if these are needed, if so, they should probably use a common yaml template ) > mom_any_create-rpms_manual > ovirt-dwh_any_create-rpms_manual > ovirt-engine-cli_any_create-rpms_manual > ovirt-host-deploy_any_create-rpms_manual > ovirt-iso-uploader_any_create-rpms_manual > ovirt-reports_any_create-rpms_manual > ovirt-setup-lib_any_create-rpms_manual > ovirt-vmconsole_any_create-rpms_manual > vdsm-jsonrpc-java_any_create-rpms_manual > vdsm_any_create-rpms_manual > ovirt-log-collector_any_create-rpms_manual > ovirt-hosted-engine-ha_any_create-rpms_manual > ovirt-hosted-engine-setup_any_create-rpms_manual > ovirt-image-uploader_any_create-rpms_manual > ovirt-engine-extension-aaa-ldap_any_create-rpms_manual > ovirt-engine-extension-aaa-misc_any_create-rpms_manual > ovirt-engine-extension-logger-log4j_any_create-rpms_manual > otopi_any_create-rpms_manual > # repo closure > repos_master_check-closure_merged > repos_3.6_check-closure_merged > spagobi_repo_merged (not sure if needed) > # should be moved to STD CI > ovirt-live_3.6-create-iso > ovirt-live_master-create-iso > vdsm_master_verify-error-codes_merged -> should be in vdsm check-patch/merge (std ci) > infra-puppet_production_check-puppet-manifests_gerrit > # in progress of moving to STD CI, should keep enabled on old jenkins until done > ovirt-engine_3.6_dao-unit-tests_created > ovirt-engine_3.6_dao-unit-tests_merged > ovirt-engine_master_dao-unit-tests_created > ovirt-engine_master_dao-unit-tests_merged > ovirt-engine_master_find-bugs_gerrit > ovirt-engine_master_find-bugs_merged > ovirt-engine_master_find-bugs_gerrit > ovirt-engine_3.6_find-bugs_gerrit > ovirt-engine_3.6_find-bugs_merged > # general jobs > ovirt-engine_master_coverity-analysis_merged > system_update_puppet ( should be part of STD CI for puppet repo?) > system_restart-gerrit-service > h5. Still unmapped jobs > ovirt-appliance_for-testing_build-artifacts-el7-x86_64 > ovirt-setup-lib_unit-tests > qemu-kvm-rhev_create-rpms_el6 > validate_open_sources_licenses_ovirt > h5. Jobs that can be deleted after putting rpms in static-repo > vhostmd_create-rpms_el6 > vhostmd_create-rpms_el7 -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-721) Re: gerrit - Prevent pushing directly to origin/branches
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-721?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-721: -------------------------------------------- Epic Link: OVIRT-403 > Re: gerrit - Prevent pushing directly to origin/branches > -------------------------------------------------------- > > Key: OVIRT-721 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-721 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > Priority: Highest > > Opening a ticket on it. > On Tue, Sep 6, 2016 at 11:13 AM, Roy Golan <rgolan(a)redhat.com> wrote: > > Using ```git push origin HEAD:origin/ovirt-engine-3.6``` I'm able to > > merge my work and bypass any review. This needs to be prevented to > > unprivileged people i.e only stable branch maintainers. > > > > See example in https://gerrit.ovirt.org/#/c/62425/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > 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.319.1#100012)

1 0

[JIRA] (OVIRT-721) Re: gerrit - Prevent pushing directly to origin/branches
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-721?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-721: -------------------------------------------- Priority: Highest (was: Medium) > Re: gerrit - Prevent pushing directly to origin/branches > -------------------------------------------------------- > > Key: OVIRT-721 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-721 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > Priority: Highest > > Opening a ticket on it. > On Tue, Sep 6, 2016 at 11:13 AM, Roy Golan <rgolan(a)redhat.com> wrote: > > Using ```git push origin HEAD:origin/ovirt-engine-3.6``` I'm able to > > merge my work and bypass any review. This needs to be prevented to > > unprivileged people i.e only stable branch maintainers. > > > > See example in https://gerrit.ovirt.org/#/c/62425/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > 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.319.1#100012)

1 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-612: -------------------------------------------- Epic Link: OVIRT-400 > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-476) migrate puppet infra jobs to standard ci
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-476?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-476: -------------------------------------------- Status: To Do (was: In Progress) > migrate puppet infra jobs to standard ci > ---------------------------------------- > > Key: OVIRT-476 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-476 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, Puppet > Reporter: Nadav Goldin > Assignee: infra > > * existing(none-yamlized) jobs: > http://jenkins.ovirt.org/job/system_update_puppet/ > http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests… > * add puppet parser validate check -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-476) migrate puppet infra jobs to standard ci
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-476?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-476: ----------------------------------------------- Assignee: infra (was: Nadav Goldin) > migrate puppet infra jobs to standard ci > ---------------------------------------- > > Key: OVIRT-476 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-476 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins, Puppet > Reporter: Nadav Goldin > Assignee: infra > > * existing(none-yamlized) jobs: > http://jenkins.ovirt.org/job/system_update_puppet/ > http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests… > * add puppet parser validate check -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.pl… ] eyal edri [Administrator] updated OVIRT-95: ------------------------------------------- Priority: Lowest > [jenkins] add job to run upgrade vdsm from version X to version Y > ----------------------------------------------------------------- > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0

[JIRA] (OVIRT-627) Implement Zuul as pre-merge action to run experimental flows
by eyal edri [Administrator] (oVirt JIRA) 18 Sep '16

18 Sep '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-627: ------------------------------------------------- Actually replacing the existing flows which run post merge, we need to check if its possible to run pre-merge with Zuul the entire flow and reject patches if it fails. > Implement Zuul as pre-merge action to run experimental flows > ------------------------------------------------------------- > > Key: OVIRT-627 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-627 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > Today, we can test a patch per project on each of the ovirt versions using experimanal flow > i,e: > run build_artifacts with a patch -> deploy to experimental -> run test job > this is problematic since it actually deploys the build with the patch to the experimental repo which should only contain built pkg that are merged. > We need to either close the flow or add param to the build artifacts that says 'create temp repo/test repo' so the built rpm won't be part of the official tested repo and the link to latest_tested won't be updated if this option is triggered. -- This message was sent by Atlassian JIRA (v1000.319.1#100012)

1 0