- Infra - oVirt List Archives

[JIRA] (OVIRT-485) add documentation on how to add new vm to phx lab
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-485?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-485: ----------------------------------------------- Assignee: Pavel Zhukov (was: infra) > add documentation on how to add new vm to phx lab > ------------------------------------------------- > > Key: OVIRT-485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-485 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Pavel Zhukov > > We need to have the procedure on how to add a new VM to PHX DC, especially around production VMs: > 1. Any template we should be using? > 2. DNS/DHCP settings > 3. High availablity settings for production VM > 4. Which DC/Cluster to add it to.. > 5. Documentation for the new VM ( + backup needed ) -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-487) Order the permissions in gerrit.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-487?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-487: ----------------------------------------------- Assignee: Anton Marchukov (was: infra) > Order the permissions in gerrit.ovirt.org > ----------------------------------------- > > Key: OVIRT-487 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-487 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Anton Marchukov > -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-451) jenkins slaves ssh connection drops too often
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-451?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-451: ------------------------------------------------- still an issue? > jenkins slaves ssh connection drops too often > --------------------------------------------- > > Key: OVIRT-451 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-451 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > I'm connecting to ovirt servers (jenkins slaves, resources,...) using foreman.ovirt.org as bastion. > if I don't actively use the keyboard on the ssh connection, the connection is closed in a few seconds with: > packet_write_wait: Connection to UNKNOWN: Broken pipe > please configure the servers for not closing the ssh connection automatically or for doing that only after 1 hour. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-460) set up another slave for ovirt -system-test
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-460?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-460: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) there should be 4 more slaves running fc23 now. > set up another slave for ovirt -system-test > ------------------------------------------- > > Key: OVIRT-460 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-460 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anatoly > Assignee: infra > > Please bring up srv10 in phx for the node system tests -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-433) add doc for infra docs on how to get access to resources
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-433?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-433: ----------------------------------------------- Assignee: dcaro (was: infra) > add doc for infra docs on how to get access to resources > -------------------------------------------------------- > > Key: OVIRT-433 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-433 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: dcaro > > When a new infra member joins the oVirt infra team, he needs to provide publish SSH key and push commit to puppet in order to get access to resources. > this should be documented in the official docs at:http://ovirt-infra-docs.readthedocs.org/en/latest/ -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-420) Move all jenkins slaves to use local disk with vdsm custom hook
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-420?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-420: ----------------------------------------------- Assignee: Anton Marchukov (was: infra) probably after we upgrade ovirt-engine to 3.6.5 > Move all jenkins slaves to use local disk with vdsm custom hook > --------------------------------------------------------------- > > Key: OVIRT-420 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-420 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Hosting, Jenkins > Reporter: eyal edri [Administrator] > Assignee: Anton Marchukov > > Once we move all slaves to use the local custom hook, we can free most of the network traffic from the storage server to the slaves, increasing network stability, job speed and generally enjoying from a faster network in PHX. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-413) decommission deb81-vm01.phx.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-413?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-413: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) can you see if we still running this vm? > decommission deb81-vm01.phx.ovirt.org > ------------------------------------- > > Key: OVIRT-413 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-413 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: Nadav Goldin > Priority: Low > > Decommission deb81-vm01.phx.ovirt.org : all jenkins jobs running on debian have been dropped now that the relevant packages have been included in Debian SID. > Please free the resources allow to create more EL7 slaves. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-412) ensure integration team can login on resources.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-412?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-412: ------------------------------------------------- [~sbonazzo(a)redhat.com] anyone from integration still can't access? > ensure integration team can login on resources.ovirt.org > -------------------------------------------------------- > > Key: OVIRT-412 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-412 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Affects Versions: Production > Reporter: sbonazzo > Assignee: infra > Priority: High > > puppet should be already configured with all public ssh keys and hashed passwords but for some reason integration team (except me) people are not able to login. > Please ensure integration team can login to the server. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-274) Adjusting mailman to prevent messages from getting pulled into spam folders
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-274?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-274: ----------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Adjusting mailman to prevent messages from getting pulled into spam folders > --------------------------------------------------------------------------- > > Key: OVIRT-274 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-274 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Mailing lists (Mailman) > Affects Versions: Test > Reporter: bproffit > Assignee: Marc Dequènes (Duck) > Labels: DKIM, mailman, > > oVirt mailing list users are reporting messages are getting dropped into their Gmail spam folders [1]. According to Sven Kieske [2]: > "This is a known gmail/ mailman (mailing list management software) issue. > "Google for gmail mailman dkim give you a good explanation. here's the short version: > "gmail does use/respect DKIM (anti spam technique) > "mailman mangles DKIM headers (a patched version is available, but not in EL6) and so some mails from DKIM enabled domains get mangled by mailman, so google thinks those mails are spam, because the DKIM > header is not correct anymore." > So would it be possible to update/configure our mailman instance to properly implement the DKIM protocol? > [1] http://lists.ovirt.org/pipermail/users/2014-November/029157.html > [2] http://lists.ovirt.org/pipermail/users/2014-November/029167.html -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-489) Create a POC of a jenkin slave running the jobs completely on RAM
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-489?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-489: ----------------------------------------------- Assignee: Pavel Zhukov (was: infra) > Create a POC of a jenkin slave running the jobs completely on RAM > ----------------------------------------------------------------- > > Key: OVIRT-489 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-489 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: Pavel Zhukov > -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-383: -------------------------------------------- Resolution: Done Status: Closed (was: New) db upgrade jobs moved into standard ci. if needed, please update code in check-patch.sh > Re: DB upgrade jobs are not using engine-setup > ---------------------------------------------- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri <eedri(a)redhat.com> wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scr… > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika <emesika(a)redhat.com> wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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.5.0#72002)

1 0

[JIRA] (OVIRT-384) DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-384?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-384: -------------------------------------------- Resolution: Done Status: Closed (was: New) DB upgrade jobs moved to STD CI. If needed, please update code in check-patch.sh to use engine-setup. > DB upgrade jobs are not using engine-setup > ------------------------------------------ > > Key: OVIRT-384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-384 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eli Mesika > Assignee: snaftaly > > Hi > > Currently DB upgrade jobs are using schema.sh script and not engine-setup > This may cause CI upgrade tests to be successful while they are actually > failed when running from engine-setup > Since we are using engine-setup to upgrade the database, CI tests must use > the same exact method in order to be reliable > I had faced this week 2 different cases when my patches passed CI but failed > actually engine-setup causing a loose of time to me and to other that > already rebased on a problematic patch. > > > Thanks > Eli Mesika -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-313) deleting yamlized jobs from git doesn't remove them from jenkins
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-313?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-313: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) > deleting yamlized jobs from git doesn't remove them from jenkins > ---------------------------------------------------------------- > > Key: OVIRT-313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-313 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: Nadav Goldin > Labels: yaml > > we have an issue with yamlized jobs: removing them from yaml doesn't disable them and doesn't delete them from jenkins. Example is: > http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el6-x86_64_merged/ > that should have been disabled / removed after job dropped by yaml files with commit 7479c7cde296a6bf8b7202f7483e408470e7e58f -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-306) [Infra docs] add howto on adding yaml patch to ci
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-306?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-306: ----------------------------------------------- Assignee: snaftaly (was: infra) I believe you had a draft somewhere on this? > [Infra docs] add howto on adding yaml patch to ci > ------------------------------------------------- > > Key: OVIRT-306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-306 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: snaftaly > Priority: Highest > > we need a wiki explaining how to add a new job in jenkins via jjb. > it should be easy to anyone not familiar with jjb. > should contain guidelines on naming conventions and code in the job as well. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-306) [Infra docs] add howto on adding yaml patch to ci
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-306?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-306: -------------------------------------------- Summary: [Infra docs] add howto on adding yaml patch to ci (was: [wiki] write a wiki page on how developer can add a jenkins job via jjb) > [Infra docs] add howto on adding yaml patch to ci > ------------------------------------------------- > > Key: OVIRT-306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-306 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > we need a wiki explaining how to add a new job in jenkins via jjb. > it should be easy to anyone not familiar with jjb. > should contain guidelines on naming conventions and code in the job as well. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

[JIRA] (OVIRT-251) chain ovirt-engine merge jobs
by eyal edri [Administrator] (oVirt JIRA) 27 Apr '16

27 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-251: -------------------------------------------- Resolution: Done Status: Closed (was: New) not relevant anymore with STD CI. There is another ticket in general to create a pipeline of tests, this is in the hands of developers now, as all the code is in check-patch/check-merged and it can be modified to run as a chain if needed. > chain ovirt-engine merge jobs > ----------------------------- > > Key: OVIRT-251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Currently a merge event triggers: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > All of them performs builds at different stages. > I suggest to run first > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > and if it finish with success, I suggest to use rpms built from > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > for running: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > otherwise abort the chain as soon as it fails. > This will reduce the times we rebuild the same code and the slaves load. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

1 0

Permissions to manually re-trigger jenkins-gerrit jobs
by Allon Mureinik 27 Apr '16

27 Apr '16

Hi guys, Can you grant me [username: amureini] permissions to manually retrigger gerrit jobs (http://jenkins.ovirt.org/gerrit_manual_trigger/)? Thanks, Allon

2 2

Yaml-ized jobs: Can they be unstable?
by Fabian Deutsch 26 Apr '16

26 Apr '16

Hey, is there a way how a yamlized job can become unstable? I'd liek to run some sanity node tests after a run, and mark a run as unstable if this happens. According to the jenkins docs, a job is unstable if one or more publishers fail. Can this be achieved with yamlized jobs? - fabian

2 2

Fwd: CloudSpin is back!
by Brian Proffitt 26 Apr '16

26 Apr '16

All: This is Donny, who worked with me to do an oVirt case study last year. He now works for Red Hat, and is interested in donating server space to the oVirt project, if needed. See the message below and let's get the discussion going! Peace, Brian ---------- Forwarded message ---------- From: Donny Davis <dondavis(a)redhat.com> Date: Sat, Apr 23, 2016 at 12:16 AM Subject: CloudSpin is back! To: Brian Proffitt <bproffit(a)redhat.com> Brian, As promised, CloudSpin is back. This time I am bringing a little more to the party. I have some (30) public ipv4 address for the community, I would assume mainly for committers or infra needs. IPv4 address are so hard to get a hold of outside the "cloud", but the one's I do have will be shared for a great project. I also have some dedicated HW servers for the ovirt project. There are currently 3 idle servers with ssd's and a 100+ GB of RAM each. Please let me know what you need, or the dev's want I have an all new DC, with 52TB of SAN storage, and a new blade chassis. Everything is on 10GBE fiber. The only change is the name, I didn't renew cloudspin in time and some **sh*l* took it from me... Anyways, I am on the fortnebula domain now. System status as of now is as follows Ovirt - 6 Nodes with 48GB each and 2x Quad core 2.93 GHZ procs (196 GB of RAM for each is enroute) Openstack - 4 Node with 96GB of ram and 2x Quad core 2.93 GHZ procs Openshift - 3 Node with 96GB of ram and 2x Quad core 2.93 GHZ procs One Critical systems SAN 2TB available (This SAN out preforms SSD storage) One General Storage SAN 52TB available You helped me get to Red Hat, which was my dream. I would like to give something back to the ovirt community that got me here. If the demand is higher for any particular system, then resources will be shifted to the system with the highest demand IE, I will de-commision openstack or openshift to meet the demands required. Also everything is on UPS, and a generator is also going to be installed in the next few weeks. I aim to provide 99% uptime to the ovirt project. Thanks again Brian Donny Davis dondavis(a)redhat.com DOD Public Sector Solution Architect RHCVA Cell 805 814 6800 -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

3 2

ovirt-image-uploader_3.6_build-artifacts-el6-x86_64 failure
by Nadav Goldin 26 Apr '16

26 Apr '16

Hey Sandro, http://jenkins.ovirt.org/job/ovirt-image-uploader_3.6_build-artifacts-el6-x… is failing because: > DEBUG util.py:417: > http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el6/repodata/repom…: > [Errno 14] HTTP Error 404 - Not Found > but there is no /rpm/el6 for ovirt-master-snapshot already. should it be ovirt-3.6-snapshot? Thanks Nadav

3 5

[JIRA] (OVIRT-506) please put my Jenkins aaviram, in dev role group
by Nadav Goldin (oVirt JIRA) 26 Apr '16

26 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-506?page=com.atlassian.jira.p… ] Nadav Goldin reassigned OVIRT-506: ---------------------------------- Assignee: Nadav Goldin (was: infra) > please put my Jenkins aaviram, in dev role group > ------------------------------------------------ > > Key: OVIRT-506 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-506 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Amit Aviram > Assignee: Nadav Goldin > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

vdsm-jsonrpc-java_{master,3.6}_build-artifacts-fc23 Failure
by Nadav Goldin 26 Apr '16

26 Apr '16

Hey Piotr and Oved, Can you have a look at: http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_build-artifacts-fc23-… http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.6_build-artifacts-fc23-x86… >> 07:02:35 Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: > 560.634 sec <<< FAILURE! - in > org.ovirt.vdsm.jsonrpc.client.reactors.stomp.SSLStompClientTestCase > >> 07:02:35 > testLongMessage(org.ovirt.vdsm.jsonrpc.client.reactors.stomp.SSLStompClientTestCase) > Time elapsed: 180.56 sec <<< ERROR! > >> 07:02:35 org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: > Connection timeout to ensure this isn't related to the Jenkins migration I re-triggered it on the old instance with the same results( http://jenkins-old.ovirt.org/job/vdsm-jsonrpc-java_master_build-artifacts-f… ) Thanks, Nadav.

4 7

[JIRA] (OVIRT-506) please put my Jenkins aaviram, in dev role group
by Amit Aviram (oVirt JIRA) 26 Apr '16

26 Apr '16

Amit Aviram created OVIRT-506: --------------------------------- Summary: please put my Jenkins aaviram, in dev role group Key: OVIRT-506 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-506 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Amit Aviram Assignee: infra -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

Re: Change in ovirt-engine[master]: engine : Change SSO classes to CamelCase
by Martin Perina 26 Apr '16

26 Apr '16

Hi, could you please take a look upgrade jobs? Following error seems to me like a CI issue: No JDK named ?java-1.8.0-openjdk? found Thanks Martin On Mon, Apr 25, 2016 at 5:15 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: engine : Change SSO classes to CamelCase > ...................................................................... > > > Patch Set 6: > > Build Failed > > > http://jenkins.phx.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el… > : FAILURE > > > http://jenkins.phx.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_m… > : FAILURE > > > http://jenkins.phx.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_6… > : SUCCESS > > > http://jenkins.phx.ovirt.org/job/ovirt-engine_master_check-merged-fc23-x86_… > : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/56410 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Iaa6b23079549330646701f3b2322db77934e7453 > Gerrit-PatchSet: 6 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Ravi Nori <rnori(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Martin Peřina <mperina(a)redhat.com> > Gerrit-Reviewer: Ravi Nori <rnori(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No >

2 3

[JIRA] (OVIRT-504) Lost privileges on jenkins.ovirt.org
by David Caro Estevez (oVirt JIRA) 26 Apr '16

26 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-504?page=com.atlassian.jira.p… ] David Caro Estevez reassigned OVIRT-504: ---------------------------------------- Assignee: David Caro Estevez (was: infra) > Lost privileges on jenkins.ovirt.org > ------------------------------------ > > Key: OVIRT-504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-504 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: David Caro Estevez > > Looks like during the migration to the new jenkins server my access rights > has been dropped. > Please restore them. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-505) Build oVirt 3.6.6 RC1
by sbonazzo (oVirt JIRA) 26 Apr '16

26 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-505?page=com.atlassian.jira.p… ] sbonazzo reassigned OVIRT-505: ------------------------------ Assignee: sbonazzo (was: infra) > Build oVirt 3.6.6 RC1 > --------------------- > > Key: OVIRT-505 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-505 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: High > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-505) Build oVirt 3.6.6 RC1
by sbonazzo (oVirt JIRA) 26 Apr '16

26 Apr '16

sbonazzo created OVIRT-505: ------------------------------ Summary: Build oVirt 3.6.6 RC1 Key: OVIRT-505 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-505 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: High -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-504) Lost privileges on jenkins.ovirt.org
by sbonazzo (oVirt JIRA) 26 Apr '16

26 Apr '16

sbonazzo created OVIRT-504: ------------------------------ Summary: Lost privileges on jenkins.ovirt.org Key: OVIRT-504 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-504 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Looks like during the migration to the new jenkins server my access rights has been dropped. Please restore them. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-503) Test email #2
by jenkins＠jenkins.phx.ovirt.org (oVirt JIRA) 25 Apr '16

25 Apr '16

jenkins(a)jenkins.phx.ovirt.org created OVIRT-503: --------------------------------------------------- Summary: Test email #2 Key: OVIRT-503 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-503 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: jenkins(a)jenkins.phx.ovirt.org Assignee: infra This is test email #2 sent from Jenkins -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

Jenkins login fails
by Piotr Kliczewski 25 Apr '16

25 Apr '16

Hi, I am not able to login to: http://jenkins.ovirt.org/ Is the credentials are different for: http://jenkins.phx.ovirt.org/ Thanks, Piotr

3 4

httpcomponets-cliet_master/core_master create-rpms
by Nadav Goldin 25 Apr '16

25 Apr '16

Hey Juan, > > http://jenkins-old.ovirt.org/job/httpcomponents-client_master_create-rpms_m… > > http://jenkins-old.ovirt.org/job/httpcomponents-core_master_create-rpms_mer… > do you happened to know if these 2 jobs are still needed? they were last built on 06/2014, but they are in the 3.6 publisher(which is failing right now as we didn't migrate the past builds, only the yamlized jobs) Thanks, Nadav.

2 1

[JIRA] (OVIRT-502) migrate icingna instance to PHX
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

eyal edri [Administrator] created OVIRT-502: ----------------------------------------------- Summary: migrate icingna instance to PHX Key: OVIRT-502 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-502 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We still run old icigna instance on monitoring.ovirt.org (hosted on alterway). We need to create a new icinga2 instance on PHX and integrate it with graphite/graphana -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-406) Migrate foreman.ovirt.org to PHX DC
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-406?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-406: ----------------------------------------------- Assignee: bkorren (was: infra) Please start planning the best route for migration, maybe its possible to keep existing foreman proxy and work with a new foreman VM as first step? to ease the dns/dhcp issues? But lets start with specifying the required steps for the install / migration. I'm guessing we can start with 1.11 and upgrade to 1.12 when its out in June. > Migrate foreman.ovirt.org to PHX DC > ----------------------------------- > > Key: OVIRT-406 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-406 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: bkorren > > Migrate the foreman instance from existing all in one 3.4 instance to the new PHX DC. > We should install new foreman server on a new VM, and migrate / add hosts rather than migrate the DB, as we don't have too many hosts / vm which will allow up a clean move and reduce possible errors and also minimal downtime. -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-501) please put my Jenkins account omachace, in dev role group
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-501?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-501: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) > please put my Jenkins account omachace, in dev role group > --------------------------------------------------------- > > Key: OVIRT-501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-501 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Ondra Machacek > Assignee: Nadav Goldin > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-501) please put my Jenkins account omachace, in dev role group
by Ondra Machacek (oVirt JIRA) 25 Apr '16

25 Apr '16

Ondra Machacek created OVIRT-501: ------------------------------------ Summary: please put my Jenkins account omachace, in dev role group Key: OVIRT-501 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-501 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Ondra Machacek Assignee: infra -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-500) Re: Cloning project with git:// fails
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-500?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-500: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) > Re: Cloning project with git:// fails > ------------------------------------- > > Key: OVIRT-500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-500 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > checking, looks like permissions problem, I can't clone it myself either: > > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > > is it supposed to have any special permissions? > On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > > Please see the git/gerrit failure that Vojtech is reporting. > > > > -------- Forwarded Message -------- > > Subject: Cloning project with git:// fails > > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > > From: Vojtech Szocs <vszocs(a)redhat.com> > > To: Sandro Bonazzola <sbonazzo(a)redhat.com> > > CC: Juan Hernández <jhernand(a)redhat.com>, Alexander Wels > > <awels(a)redhat.com>, Oved Ourfali <oourfali(a)redhat.com> > > > > Hi Sandro, > > > > after setting up automation and packaging directories > > for 'ovirt-engine-dashboard' project [1], Jenkins CI > > always gives -1 with following error: > > > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please see my comment at [2] - cloning with https:// > > and ssh:// works, but somehow git:// fails. > > > > I'm out of ideas as to why.. > > > > [1] https://gerrit.ovirt.org/#/c/56435/ > > [2] https://gerrit.ovirt.org/#/c/56480/ > > > > The only real difference between: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > > > and: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > > (for which cloning with git:// works as expected) > > > > seems to be "Enable signed push" option but I don't > > think that's related. > > > > Thanks, > > Vojtech > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-497) [docs] Add documents on what's on the ci-tools repo and how it gets there
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-497?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-497: ----------------------------------------------- Assignee: David Caro Estevez (was: infra) > [docs] Add documents on what's on the ci-tools repo and how it gets there > ------------------------------------------------------------------------- > > Key: OVIRT-497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-497 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: David Caro Estevez > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-499) please put my Jenkins mpolednik, in dev role group
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-499?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-499: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) > please put my Jenkins mpolednik, in dev role group > -------------------------------------------------- > > Key: OVIRT-499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-499 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: infra > > needed for vdsm job retrigerring -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-496) Add documentation for oVirt gerrit hooks
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-496?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-496: ----------------------------------------------- Assignee: dcaro (was: infra) > Add documentation for oVirt gerrit hooks > ---------------------------------------- > > Key: OVIRT-496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-496 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: dcaro > Priority: High > > We are missing documentation for all the Gerrit hooks and their configuration. > Please add a page to the official infra docs page with information on all the hooks. > It should include: > * relevant code/repos > * list of active hooks and their purpose > * location of conf files, meaning of each config option > * troubleshooting -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-500) Re: Cloning project with git:// fails
by Juan Hernández (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-500?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-500: -------------------------------------- Manual git clone from my environment works now. Can you retrigger the Jenkins jobs for this patch, to check that it works from Jenkins as well: packaging: Link UI plugin resources to oVirt Engine https://gerrit.ovirt.org/56480 The change id is 3199313f58642c201615e875164c2075ea74df63 . > Re: Cloning project with git:// fails > ------------------------------------- > > Key: OVIRT-500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-500 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > checking, looks like permissions problem, I can't clone it myself either: > > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > > is it supposed to have any special permissions? > On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > > Please see the git/gerrit failure that Vojtech is reporting. > > > > -------- Forwarded Message -------- > > Subject: Cloning project with git:// fails > > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > > From: Vojtech Szocs <vszocs(a)redhat.com> > > To: Sandro Bonazzola <sbonazzo(a)redhat.com> > > CC: Juan Hernández <jhernand(a)redhat.com>, Alexander Wels > > <awels(a)redhat.com>, Oved Ourfali <oourfali(a)redhat.com> > > > > Hi Sandro, > > > > after setting up automation and packaging directories > > for 'ovirt-engine-dashboard' project [1], Jenkins CI > > always gives -1 with following error: > > > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please see my comment at [2] - cloning with https:// > > and ssh:// works, but somehow git:// fails. > > > > I'm out of ideas as to why.. > > > > [1] https://gerrit.ovirt.org/#/c/56435/ > > [2] https://gerrit.ovirt.org/#/c/56480/ > > > > The only real difference between: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > > > and: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > > (for which cloning with git:// works as expected) > > > > seems to be "Enable signed push" option but I don't > > think that's related. > > > > Thanks, > > Vojtech > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-500) Re: Cloning project with git:// fails
by Nadav Goldin (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-500?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-500: ------------------------------------ fixed, can you test? ( I can clone locally) for future reference: it was missing 'git-daemon-export-ok' empty file under gerrit /home/gerrit2/review_site/git/ovirt-engine-dashboard.git followed [~rbarry] detailed docs at [https://gerrit.ovirt.org/#/c/50462/] > Re: Cloning project with git:// fails > ------------------------------------- > > Key: OVIRT-500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-500 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > checking, looks like permissions problem, I can't clone it myself either: > > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > > is it supposed to have any special permissions? > On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > > Please see the git/gerrit failure that Vojtech is reporting. > > > > -------- Forwarded Message -------- > > Subject: Cloning project with git:// fails > > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > > From: Vojtech Szocs <vszocs(a)redhat.com> > > To: Sandro Bonazzola <sbonazzo(a)redhat.com> > > CC: Juan Hernández <jhernand(a)redhat.com>, Alexander Wels > > <awels(a)redhat.com>, Oved Ourfali <oourfali(a)redhat.com> > > > > Hi Sandro, > > > > after setting up automation and packaging directories > > for 'ovirt-engine-dashboard' project [1], Jenkins CI > > always gives -1 with following error: > > > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please see my comment at [2] - cloning with https:// > > and ssh:// works, but somehow git:// fails. > > > > I'm out of ideas as to why.. > > > > [1] https://gerrit.ovirt.org/#/c/56435/ > > [2] https://gerrit.ovirt.org/#/c/56480/ > > > > The only real difference between: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > > > and: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > > (for which cloning with git:// works as expected) > > > > seems to be "Enable signed push" option but I don't > > think that's related. > > > > Thanks, > > Vojtech > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-500) Re: Cloning project with git:// fails
by Juan Hernández (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-500?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-500: -------------------------------------- On 04/25/2016 03:16 PM, Nadav Goldin wrote: > checking, looks like permissions problem, I can't clone it myself either: > > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > <http://gerrit.ovirt.org/ovirt-engine-dashboard.git> > Cloning into 'ovirt-engine-dashboard'... > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > > is it supposed to have any special permissions? > No, for an anonymous clone like this one everyone should have permission. > On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com > <mailto:jhernand@redhat.com>> wrote: > > Please see the git/gerrit failure that Vojtech is reporting. > > -------- Forwarded Message -------- > Subject: Cloning project with git:// fails > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > From: Vojtech Szocs <vszocs(a)redhat.com <mailto:vszocs@redhat.com>> > To: Sandro Bonazzola <sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com>> > CC: Juan Hernández <jhernand(a)redhat.com > <mailto:jhernand@redhat.com>>, Alexander Wels > <awels(a)redhat.com <mailto:awels@redhat.com>>, Oved Ourfali > <oourfali(a)redhat.com <mailto:oourfali@redhat.com>> > > Hi Sandro, > > after setting up automation and packaging directories > for 'ovirt-engine-dashboard' project [1], Jenkins CI > always gives -1 with following error: > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > <http://gerrit.ovirt.org/ovirt-engine-dashboard.git> > Cloning into 'ovirt-engine-dashboard'... > fatal: Could not read from remote repository. > > Please see my comment at [2] - cloning with https:// > and ssh:// works, but somehow git:// fails. > > I'm out of ideas as to why.. > > [1] https://gerrit.ovirt.org/#/c/56435/ > [2] https://gerrit.ovirt.org/#/c/56480/ > > The only real difference between: > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > and: > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > (for which cloning with git:// works as expected) > > seems to be "Enable signed push" option but I don't > think that's related. > > Thanks, > Vojtech > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org <mailto:Infra@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/infra > > -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > Re: Cloning project with git:// fails > ------------------------------------- > > Key: OVIRT-500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-500 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > checking, looks like permissions problem, I can't clone it myself either: > > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > > is it supposed to have any special permissions? > On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > > Please see the git/gerrit failure that Vojtech is reporting. > > > > -------- Forwarded Message -------- > > Subject: Cloning project with git:// fails > > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > > From: Vojtech Szocs <vszocs(a)redhat.com> > > To: Sandro Bonazzola <sbonazzo(a)redhat.com> > > CC: Juan Hernández <jhernand(a)redhat.com>, Alexander Wels > > <awels(a)redhat.com>, Oved Ourfali <oourfali(a)redhat.com> > > > > Hi Sandro, > > > > after setting up automation and packaging directories > > for 'ovirt-engine-dashboard' project [1], Jenkins CI > > always gives -1 with following error: > > > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > > Cloning into 'ovirt-engine-dashboard'... > > fatal: Could not read from remote repository. > > > > Please see my comment at [2] - cloning with https:// > > and ssh:// works, but somehow git:// fails. > > > > I'm out of ideas as to why.. > > > > [1] https://gerrit.ovirt.org/#/c/56435/ > > [2] https://gerrit.ovirt.org/#/c/56480/ > > > > The only real difference between: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > > > and: > > > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > > (for which cloning with git:// works as expected) > > > > seems to be "Enable signed push" option but I don't > > think that's related. > > > > Thanks, > > Vojtech > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-500) Re: Cloning project with git:// fails
by Nadav Goldin (oVirt JIRA) 25 Apr '16

25 Apr '16

Nadav Goldin created OVIRT-500: ---------------------------------- Summary: Re: Cloning project with git:// fails Key: OVIRT-500 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-500 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nadav Goldin Assignee: infra checking, looks like permissions problem, I can't clone it myself either: > git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > Cloning into 'ovirt-engine-dashboard'... > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > is it supposed to have any special permissions? On Mon, Apr 25, 2016 at 4:04 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > Please see the git/gerrit failure that Vojtech is reporting. > > -------- Forwarded Message -------- > Subject: Cloning project with git:// fails > Date: Mon, 25 Apr 2016 08:53:45 -0400 (EDT) > From: Vojtech Szocs <vszocs(a)redhat.com> > To: Sandro Bonazzola <sbonazzo(a)redhat.com> > CC: Juan Hernández <jhernand(a)redhat.com>, Alexander Wels > <awels(a)redhat.com>, Oved Ourfali <oourfali(a)redhat.com> > > Hi Sandro, > > after setting up automation and packaging directories > for 'ovirt-engine-dashboard' project [1], Jenkins CI > always gives -1 with following error: > > $ git clone git://gerrit.ovirt.org/ovirt-engine-dashboard.git > Cloning into 'ovirt-engine-dashboard'... > fatal: Could not read from remote repository. > > Please see my comment at [2] - cloning with https:// > and ssh:// works, but somehow git:// fails. > > I'm out of ideas as to why.. > > [1] https://gerrit.ovirt.org/#/c/56435/ > [2] https://gerrit.ovirt.org/#/c/56480/ > > The only real difference between: > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard > > and: > > https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-api-explorer > (for which cloning with git:// works as expected) > > seems to be "Enable signed push" option but I don't > think that's related. > > Thanks, > Vojtech > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-499) please put my Jenkins mpolednik, in dev role group
by Martin Polednik (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-499?page=com.atlassian.jira.p… ] Martin Polednik commented on OVIRT-499: --------------------------------------- works as before, thanks! > please put my Jenkins mpolednik, in dev role group > -------------------------------------------------- > > Key: OVIRT-499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-499 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: infra > > needed for vdsm job retrigerring -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-499) please put my Jenkins mpolednik, in dev role group
by Nadav Goldin (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-499?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-499: ------------------------------------ [~mpolednik(a)redhat.com] added tell me if its okay > please put my Jenkins mpolednik, in dev role group > -------------------------------------------------- > > Key: OVIRT-499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-499 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: infra > > needed for vdsm job retrigerring -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-499) please put my Jenkins mpolednik, in dev role group
by Martin Polednik (oVirt JIRA) 25 Apr '16

25 Apr '16

Martin Polednik created OVIRT-499: ------------------------------------- Summary: please put my Jenkins mpolednik, in dev role group Key: OVIRT-499 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-499 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Martin Polednik Assignee: infra needed for vdsm job retrigerring -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

User authentication on http://jenkins.ovirt.org
by Nadav Goldin 25 Apr '16

25 Apr '16

Hi all, I note again that personal user accounts were not migrated to the new Jenkins instance, so if you need other than read-only access please enrol again(press sign up in the welcome page). If you require permissions to trigger jobs manually: email infra-support(a)ovirt.org 'please put my Jenkins $username, in dev role group' for other permissions(create job, etc) - if it is a 'testing' job feel free to use http://jenkins-old.ovirt.org, as we are trying to minimize the number of none-yamlized jobs in the new instance. If that is not suitable please email what you need. Thanks, Nadav.

1 0

[JIRA] (OVIRT-498) Please grant me the permissions to trigger jobs
by eyal edri [Administrator] (oVirt JIRA) 25 Apr '16

25 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-498?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-498: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) > Please grant me the permissions to trigger jobs > ----------------------------------------------- > > Key: OVIRT-498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Fabian Deutsch > Assignee: Nadav Goldin > > Hey, > please rgant me the permission to trigger jobs. > - fabian -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-498) Please grant me the permissions to trigger jobs
by Fabian Deutsch (oVirt JIRA) 25 Apr '16

25 Apr '16

Fabian Deutsch created OVIRT-498: ------------------------------------ Summary: Please grant me the permissions to trigger jobs Key: OVIRT-498 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-498 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Fabian Deutsch Assignee: infra Hey, please rgant me the permission to trigger jobs. - fabian -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

Jenkins.ovirt.org Upgrade | 24/04/2016(Sunday) - 18:00 TLV
by Nadav Goldin 24 Apr '16

24 Apr '16

Hey all, On Sunday, 24.04.2015 - 18:00 TLV (17:00 CET) we plan to migrate Jenkins( http://jenkins.ovirt.org) to a new VM in the PHX datacenter, this will increase the instance storage and allow better connectivity with the slaves. 1. The expected downtime is 2 hours, during that time no patches will be checked and you could not login to Jenkins. Patches sent to gerrit during the downtime, might get checked after the downtime. 2.What will be migrated: All yamlized jobs, global configuration and most of the existing slaves. 3. The old Jenkins instance will still be available under jenkins-old.ovirt.org, with a minimum number of slaves. It will be kept at least in the following months for backup and for the none-yamlized jobs(but with no gerrit triggers) 4. User authentication: all users will have to enrol again, this can be done already this week via http://jenkins.phx.ovirt.org Another reminder will be sent ~ 2 hours before the migration. Thanks, Nadav.

1 1