- Infra - oVirt List Archives

[JIRA] (OVIRT-895) mailing list memberships reminder - do we need that?
by Evgheni Dereveanchin (oVirt JIRA) 01 Dec '16

01 Dec '16

Evgheni Dereveanchin created OVIRT-895: ------------------------------------------ Summary: mailing list memberships reminder - do we need that? Key: OVIRT-895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-895 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low I'm subscribed to a bunch of lists and every month I get membership reminder emails. Do we have them for a reason? If not - I'd like to disable them (can be done per-list in the settings or globally across the Mailman instance) -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-891: ------------------------------------ {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 from python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren edited comment on OVIRT-891 at 12/1/16 12:05 PM: -------------------------------------------------------------- {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 for python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) was (Author: bkorren(a)redhat.com) {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 from python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-894) Add support of sercers and credentials in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

Barak Korren created OVIRT-894: ---------------------------------- Summary: Add support of sercers and credentials in Standard-CI Key: OVIRT-894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-894 Project: oVirt - virtualization made easy Issue Type: New Feature Components: General Reporter: Barak Korren Assignee: infra Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include: # Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster) # Launching remote processes (Check code with remote services) While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-890: ------------------------------------ It shouldn't really matter _where_ we publish. As I see it there are two main option to publish _anything_ from standard CI: # Have build_artifacts.sh put it in "exported_artifacts" and then have "the system" publish it to where it needs to go - this is what the experimental flow is doing for example for RPMs. # Publish directly from build_artifacts.sh It should be obvious that solution #2 is more flexible and will require less maintenance from us in the long run, but it has a couple of issues: # For publishing typically some credentials are needed # The decision where to publish ends up being made at the discretion of the developer, as opposed to on an environment level. I don't think #2 is really an issue. WRT #1, this is something we've encountered before, and perhaps we should solve it by adding support for credentials and secrets in Standard CI (OVIRT-894). > Add support to publish containers in standard CI > ------------------------------------------------ > > Key: OVIRT-890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker, standard-ci > > Mostly likely to Dockerhub or OpenShift registry. > We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-894) Add support of sercers and credentials in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-894?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-894: ------------------------------- Epic Link: OVIRT-400 > Add support of sercers and credentials in Standard-CI > ----------------------------------------------------- > > Key: OVIRT-894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-894 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include: > # Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster) > # Launching remote processes (Check code with remote services) > While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-891: ------------------------------------------------- You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-893) Build oVirt 4.1.0 beta1
by sbonazzo (oVirt JIRA) 01 Dec '16

01 Dec '16

sbonazzo created OVIRT-893: ------------------------------ Summary: Build oVirt 4.1.0 beta1 Key: OVIRT-893 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-893 Project: oVirt - virtualization made easy Issue Type: Task Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-893) Build oVirt 4.1.0 beta1
by sbonazzo (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-893?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-893: --------------------------- Epic Link: OVIRT-411 > Build oVirt 4.1.0 beta1 > ----------------------- > > Key: OVIRT-893 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-893 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-893) Build oVirt 4.1.0 beta1
by sbonazzo (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-893?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-893: --------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.1.0 beta1 > ----------------------- > > Key: OVIRT-893 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-893 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-889: ------------------------------------------------- Its a sub-task of the general task, so we can track and work on each sub-task seperately > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-890: ------------------------------- Labels: containers docker standard-ci (was: ) > Add support to publish containers in standard CI > ------------------------------------------------ > > Key: OVIRT-890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker, standard-ci > > Mostly likely to Dockerhub or OpenShift registry. > We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-891: ------------------------------------ I don't think this belongs in standard-CI, standard CI is for verifying _code_ not artifacts (no matter how fancy and fashionable they are). Verifying complete artifacts is what systems tests are for. > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-889: ------------------------------- Labels: containers docker (was: ) > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-889: ------------------------------------ Isn`t this a duplicate of OVIRT-848 ? Also I've repentantly stated - containers are NOT special, standard CI can already build RPMs, images and tarballs, so it does not need to be changed just so you could build containers. The whole point of standard-CI was that we don't have to change it every time a new shiny thing comes along. There is one issue with handling the situation of building containers in standard CI if and when standard CI itself will use containers (OVIRT-873), and the solution for that is to allow optional bind mounts so we can bind mount /var/run/docker.sock only if it exists (and not fail if it doesn't) - I made OVIRT-892 to specify and track this. > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-892: ------------------------------- Labels: containers (was: ) > Allow for optional bind mounts in Standard-CI > --------------------------------------------- > > Key: OVIRT-892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Labels: containers, docker, standard-ci > > Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. > We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. > We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: > # Fail - what it used to do > # Create what it needs - what it does now > # Just ignore and not mound > Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-892: ------------------------------- Labels: containers docker standard-ci (was: containers) > Allow for optional bind mounts in Standard-CI > --------------------------------------------- > > Key: OVIRT-892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Labels: containers, docker, standard-ci > > Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. > We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. > We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: > # Fail - what it used to do > # Create what it needs - what it does now > # Just ignore and not mound > Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-892: ------------------------------- Epic Link: OVIRT-400 > Allow for optional bind mounts in Standard-CI > --------------------------------------------- > > Key: OVIRT-892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. > We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. > We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: > # Fail - what it used to do > # Create what it needs - what it does now > # Just ignore and not mound > Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

Barak Korren created OVIRT-892: ---------------------------------- Summary: Allow for optional bind mounts in Standard-CI Key: OVIRT-892 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: # Fail - what it used to do # Create what it needs - what it does now # Just ignore and not mound Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-891: ----------------------------------------------- Summary: Add support for verification / testing of containers in standard CI Key: OVIRT-891 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra >From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-890: ----------------------------------------------- Summary: Add support to publish containers in standard CI Key: OVIRT-890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra Mostly likely to Dockerhub or OpenShift registry. We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-889: ----------------------------------------------- Summary: Add support for building containers in standard CI Key: OVIRT-889 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3800 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Dec '16

01 Dec '16

------=_Part_19_556033321.1480570134122 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3800/, Build Number: 3800, Build Status: FAILURE ------=_Part_19_556033321.1480570134122--

4 10

[JIRA] (OVIRT-848) Add support for building containers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-848?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-848: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support for building containers in oVirt CI > ----------------------------------------------- > > Key: OVIRT-848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > > more and more projects in oVirt are starting to build containers and using Docker files in their reops. > We need to start preparing oVirt CI to know how to handle containers and support containers the same way we support rpms today. > This will be a parent task with multiple sub-tasks that will follow, the following is a draft list of what we might need to do to add this support: > # Install Registry server ( maybe use openshift.ovirt.org ) > # Add for standard CI 'build-containers.sh' support > # Add verification steps for the build before publishing to registry > # Look at 3rd party OSS projects that might help and integrate with existing solutions -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

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

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-627: ----------------------------------------------- Assignee: bkorren (was: infra) I guess this is the second step after we see Zuul integration works. I think the 1st thing we should do is create some sort of design diagram of how we want the flow to work and what input/output/triggers it should have. > 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: bkorren > > 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.606.0#100023)

1 0

[JIRA] (OVIRT-888) mock build ignores unfound packages
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-888?page=com.atlassian.jira.p… ] Barak Korren closed OVIRT-888. ------------------------------ Resolution: Duplicate Duplicate of OVIRT-886 > mock build ignores unfound packages > ----------------------------------- > > Key: OVIRT-888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-888 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > If I mis-specify a package in check-merged.packages (e.g. typo), Jenkins > silently ignores the problem and let check-merged.sh start. > Debugging the ensuing problems is a pain. If jenkins is unable to build > the specified environment, it should fail and report the error. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-888) mock build ignores unfound packages
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-888?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-888: ------------------------------- Status: In Progress (was: To Do) > mock build ignores unfound packages > ----------------------------------- > > Key: OVIRT-888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-888 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > If I mis-specify a package in check-merged.packages (e.g. typo), Jenkins > silently ignores the problem and let check-merged.sh start. > Debugging the ensuing problems is a pain. If jenkins is unable to build > the specified environment, it should fail and report the error. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-888) mock build ignores unfound packages
by danken (oVirt JIRA) 01 Dec '16

01 Dec '16

danken created OVIRT-888: ---------------------------- Summary: mock build ignores unfound packages Key: OVIRT-888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-888 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra If I mis-specify a package in check-merged.packages (e.g. typo), Jenkins silently ignores the problem and let check-merged.sh start. Debugging the ensuing problems is a pain. If jenkins is unable to build the specified environment, it should fail and report the error. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

oVirt infra daily report - unstable production jobs - 154
by jenkins＠jenkins.phx.ovirt.org 01 Dec '16

01 Dec '16

------=_Part_15_1761377290.1480546810780 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/154//artifact/exported-a… Cheers, Jenkins ------=_Part_15_1761377290.1480546810780 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 30/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_check-merged-el7-x86…">ovirt-provider-ovn_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/">system-backup_jenkins_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_15_1761377290.1480546810780--

1 0

planned reboot of servers
by Evgheni Dereveanchin 30 Nov '16

30 Nov '16

Hi everyone, I will update and reboot more servers today, mainly: artifactory.ovirt.org ci-templates-repo.phx.ovirt.org foreman.phx.ovirt.org glance.phx.ovirt.org graphite.phx.ovirt.org proxy.phx.ovirt.org As most of these are used by builds, I will temporarily set Jenkins to maintenance mode. Builds will be added to the queue and will run as soon as the maintenance is complete. Regards, Evgheni Dereveanchin

1 1

[JIRA] (OVIRT-887) deploy a production OpenShift instance in PHX
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '16

30 Nov '16

Evgheni Dereveanchin created OVIRT-887: ------------------------------------------ Summary: deploy a production OpenShift instance in PHX Key: OVIRT-887 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-887 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra After successfully testing the pilot OpenShift instance in PHX it's time to deploy a production setup. This ticket is to track what we'd need and discuss the details. For example, the following points don't apply to the pilot instance and need to be planned well for the production one: 1) container persistent storage 2) node topology 3) user authentication -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-887) deploy a production OpenShift instance in PHX
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '16

30 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-887?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-887: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > deploy a production OpenShift instance in PHX > --------------------------------------------- > > Key: OVIRT-887 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-887 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > After successfully testing the pilot OpenShift instance in PHX it's time to deploy a production setup. This ticket is to track what we'd need and discuss the details. > For example, the following points don't apply to the pilot instance and need to be planned well for the production one: > 1) container persistent storage > 2) node topology > 3) user authentication -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Gil Shinar (oVirt JIRA) 30 Nov '16

30 Nov '16

Gil Shinar created OVIRT-886: -------------------------------- Summary: Yum install does not throw error on missing package Key: OVIRT-886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gil Shinar Assignee: infra When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

Re: [ovirt-devel] master won't start
by Eyal Edri 30 Nov '16

30 Nov '16

System tests didn't caught this, I'm guessing since all tests are using only JSONRPC? Any point in adding a test to catch this or since we're dropping XMLRPC it won't be needed? On Wed, Nov 30, 2016 at 8:12 AM, Martin Perina <mperina(a)redhat.com> wrote: > Hi, > > here's the patch that should fix the issue: > > https://gerrit.ovirt.org/67559 > > Martin > > > On Wed, Nov 30, 2016 at 6:52 AM, Martin Perina <mperina(a)redhat.com> wrote: > >> Hi, >> >> I will post a fix in a few minutes, sorry for the breakage. >> >> Martin >> >> >> On Wed, Nov 30, 2016 at 4:53 AM, Greg Sheremeta <gshereme(a)redhat.com> >> wrote: >> >>> Reverting 6d6c6bdc fixes the issue. >>> >>> core: xmlrpc removal >>> >>> Now with jsonrpc being primary protocol we fade out xmlrpc >>> implementation. >>> >>> @Piotr, please advise. >>> >>> Best wishes, >>> Greg >>> >>> >>> >>> >>> >>> On Tue, Nov 29, 2016 at 9:44 PM, Greg Sheremeta <gshereme(a)redhat.com> >>> wrote: >>> >>>> Hi, >>>> >>>> A fresh checkout of master with a fresh database will not start for me. >>>> I tried on two separate machines. ovirt-engine-4.0 branch is still working. >>>> >>>> Any ideas? >>>> >>>> Best wishes, >>>> Greg >>>> >>>> >>>> 2016-11-29 21:11:33,918-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-4) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.docs.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.docs.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.docs.war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,915-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-5) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.welcome.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.welcome.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.welcome. >>>> war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,909-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-2) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear".main: WFLYSRV0179: Failed >>>> to load module: deployment.engine.ear:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1078) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 21 more >>>> >>>> 2016-11-29 21:11:33,931-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-8) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.bll.jar".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.bll.jar".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.bll.jar:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,953-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-6) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.root.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.root.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.root.war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleNotFoundException: >>>> org.apache.xmlrpc:main >>>> at org.jboss.modules.ModuleLoader$FutureModule.getModule(ModuleLoader.java:651) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:328) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> >>>> 2016-11-29 21:11:33,932-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-3) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.services.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.services.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.services >>>> .war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,955-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-1) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.enginesso.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.enginesso.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.enginess >>>> o.war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,965-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-7) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.webadmin.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.webadmin.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.webadmin >>>> .war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,986-05 ERROR [org.jboss.msc.service.fail] (MSC >>>> service thread 1-8) MSC000001: Failed to start service >>>> jboss.module.service."deployment.engine.ear.userportal.war".main: >>>> org.jboss.msc.service.StartException in service >>>> jboss.module.service."deployment.engine.ear.userportal.war".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.userport >>>> al.war:main >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startS >>>> ervice(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2 >>>> .6.Final] >>>> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) >>>> [jboss-msc-1.2.6.Final.jar:1.2.6.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_101] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_101] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading module >>>> from /home/greg/ovirt-engine/share/ovirt-engine/modules/common/or >>>> g/apache/xmlrpc/main/module.xml >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:228) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:204) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:170) >>>> at org.jboss.modules.LocalModuleFinder.lambda$findModule$3(LocalModuleFinder.java:149) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> [rt.jar:1.8.0_101] >>>> at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:144) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:439) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:342) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:289) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadExportedModule(ModuleLoader.java:300) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:313) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloa >>>> dModule(ServiceModuleLoader.java:149) [wildfly-server-2.0.10.Final.j >>>> ar:2.0.10.Final] >>>> at org.jboss.modules.Module.addExportedPaths(Module.java:1229) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.addPaths(Module.java:1121) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.link(Module.java:1448) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1476) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:225) >>>> [jboss-modules.jar:1.5.1.Final] >>>> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) >>>> [wildfly-server-2.0.10.Final.jar:2.0.10.Final] >>>> ... 5 more >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add >>>> resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' (position: >>>> END_TAG seen ...<resources>\n <resource-root >>>> path="xmlrpc-common.jar"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(Modu >>>> leXmlParser.java:891) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleX >>>> mlParser.java:735) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(Mo >>>> duleXmlParser.java:535) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXm >>>> lParser.java:340) >>>> at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleX >>>> mlParser.java:226) >>>> ... 22 more >>>> >>>> 2016-11-29 21:11:33,990-05 ERROR [org.jboss.as.controller.management-operation] >>>> (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - >>>> address: ([("deployment" => "restapi.war")]) - failure description: >>>> {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ >>>> "jboss.naming.context.java.module.restapi.restapi.env.\"org. >>>> ovirt.engine.api.restapi.security.CORSSupportFilter\".backend is >>>> missing [jboss.naming.context.java.global.engine.bll.\"Backend!org.o >>>> virt.engine.core.common.interfaces.BackendLocal\"]", >>>> "jboss.naming.context.java.module.restapi.restapi.env.\"org. >>>> ovirt.engine.api.restapi.invocation.CurrentFilter\".backend is missing >>>> [jboss.naming.context.java.global.engine.bll.\"Backend!org.o >>>> virt.engine.core.common.interfaces.BackendLocal\"]" >>>> ]} >>>> 2016-11-29 21:11:33,993-05 ERROR [org.jboss.as.controller.management-operation] >>>> (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - >>>> address: ([("deployment" => "engine.ear")]) - failure description: { >>>> "WFLYCTL0080: Failed services" => { >>>> "jboss.module.service.\"deployment.engine.ear.welcome.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.welcome.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.welcome. >>>> war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.webadmin >>>> .war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.enginesso.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.enginesso.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.enginess >>>> o.war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear\".main" => >>>> "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear\".main: WFLYSRV0179: >>>> Failed to load module: deployment.engine.ear:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.userportal.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.userportal.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.userport >>>> al.war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.root.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.root.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.root.war:main >>>> Caused by: org.jboss.modules.ModuleNotFoundException: >>>> org.apache.xmlrpc:main", >>>> "jboss.module.service.\"deployment.engine.ear.docs.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.docs.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.docs.war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.bll.jar\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.bll.jar\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.bll.jar:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)", >>>> "jboss.module.service.\"deployment.engine.ear.services.war\".main" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.module.service.\"deployment.engine.ear.services.war\".main: >>>> WFLYSRV0179: Failed to load module: deployment.engine.ear.services >>>> .war:main >>>> Caused by: org.jboss.modules.ModuleLoadException: Error loading >>>> module from /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/module.xml >>>> Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to >>>> add resource root 'xmlrpc-common.jar' at path 'xmlrpc-common.jar' >>>> (position: END_TAG seen ...<resources>\\n <resource-root >>>> path=\"xmlrpc-common.jar\"/>... @6:46) caused by: >>>> java.io.FileNotFoundException: /home/greg/ovirt-engine/share/ >>>> ovirt-engine/modules/common/org/apache/xmlrpc/main/xmlrpc-common.jar >>>> (No such file or directory)" >>>> }, >>>> "WFLYCTL0288: One or more services were unable to start due to one >>>> or more indirect dependencies not being available." => { >>>> "Services that were unable to start:" => [ >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"bll.jar\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"docs.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"enginesso.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"root.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"services.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"userportal.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"webadmin.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.subunit.\"en >>>> gine.ear\".\"welcome.war\".FIRST_MODULE_USE", >>>> "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" >>>> ], >>>> "Services that may be the cause:" => [" >>>> jboss.naming.context.java.global.engine.bll.\"Backend!org. >>>> ovirt.engine.core.common.interfaces.BackendLocal\""] >>>> } >>>> } >>>> 2016-11-29 21:11:34,012-05 INFO [org.jboss.as.server] (ServerService >>>> Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : >>>> "engine.ear") >>>> 2016-11-29 21:11:34,012-05 INFO [org.jboss.as.server] (ServerService >>>> Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : >>>> "apidoc.war") >>>> 2016-11-29 21:11:34,012-05 INFO [org.jboss.as.server] (ServerService >>>> Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : >>>> "restapi.war") >>>> 2016-11-29 21:11:34,014-05 INFO [org.jboss.as.controller] (Controller >>>> Boot Thread) WFLYCTL0183: Service status report >>>> WFLYCTL0184: New missing/unsatisfied dependencies: >>>> >>>> >>>> >>>> >>>> -- >>>> Greg Sheremeta, MBA >>>> Red Hat, Inc. >>>> Sr. Software Engineer >>>> gshereme(a)redhat.com >>>> >>> >>> >>> >>> -- >>> Greg Sheremeta, MBA >>> Red Hat, Inc. >>> Sr. Software Engineer >>> gshereme(a)redhat.com >>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >>> >> >> > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- 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)

3 2

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3776 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Nov '16

30 Nov '16

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3776/, Build Number: 3776, Build Status: FAILURE

1 3

[JIRA] (OVIRT-885) lago-devel list stopped archiving mails from November 2016
by eyal edri [Administrator] (oVirt JIRA) 30 Nov '16

30 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-885?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-885: -------------------------------------------- Epic Link: OVIRT-403 > lago-devel list stopped archiving mails from November 2016 > ---------------------------------------------------------- > > Key: OVIRT-885 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-885 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > Can't see any mails from Nov [1] even though the settings was set to weekly. > [1] http://lists.ovirt.org/pipermail/lago-devel/ -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-885) lago-devel list stopped archiving mails from November 2016
by eyal edri [Administrator] (oVirt JIRA) 30 Nov '16

30 Nov '16

eyal edri [Administrator] created OVIRT-885: ----------------------------------------------- Summary: lago-devel list stopped archiving mails from November 2016 Key: OVIRT-885 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-885 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Can't see any mails from Nov [1] even though the settings was set to weekly. [1] http://lists.ovirt.org/pipermail/lago-devel/ -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-878) [gerrit hooks] add more checks to set_modified hook
by Shlomo Ben David (oVirt JIRA) 30 Nov '16

30 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-878?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-878: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] add more checks to set_modified hook > ---------------------------------------------------- > > Key: OVIRT-878 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-878 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > set_modified hook is setting bug status to MODIFIED although there are open patches > We need to add more checks to test if there are still open patches (in the external tracker section) > If there are ==> don't change the bug status to MODIFIED -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-884) check workspace cleanup task
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '16

30 Nov '16

Evgheni Dereveanchin created OVIRT-884: ------------------------------------------ Summary: check workspace cleanup task Key: OVIRT-884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-884 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins Reporter: Evgheni Dereveanchin Assignee: infra Recently we get lots of failures due to dirty workspaces on Jenkins slaves. The cleanup task is reporting success, yet its runtime is usually below 1 second, so it may not be running properly and causing the failures: http://jenkins.ovirt.org/job/system_cleanup-workspaces/5261/console Need to check this job to ensure it actually cleans up workspaces. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-883) jenkins backup failing
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '16

30 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-883?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-883: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > jenkins backup failing > ---------------------- > > Key: OVIRT-883 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-883 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > I applied OS updates to Jenkins and the backup server yesterday and rebooted both machines. Now Jenkins backup is failing: > http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/ > Need to troubleshoot why this is happening and fix backups on this critical service. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-883) jenkins backup failing
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '16

30 Nov '16

Evgheni Dereveanchin created OVIRT-883: ------------------------------------------ Summary: jenkins backup failing Key: OVIRT-883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-883 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Evgheni Dereveanchin Assignee: infra I applied OS updates to Jenkins and the backup server yesterday and rebooted both machines. Now Jenkins backup is failing: http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/ Need to troubleshoot why this is happening and fix backups on this critical service. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

oVirt infra daily report - unstable production jobs - 153
by jenkins＠jenkins.phx.ovirt.org 30 Nov '16

30 Nov '16

------=_Part_0_1308833088.1480460408027 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/153//artifact/exported-a… Cheers, Jenkins ------=_Part_0_1308833088.1480460408027 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 29/11/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc24-x86_64/">ovirt-engine_master_check-merged-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0-snapshot_build-artifac…">ovirt-node-ng_ovirt-4.0-snapshot_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-…">ovirt-provider-ovn_master_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_check-merged-el7-x86…">ovirt-provider-ovn_master_check-merged-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_0_1308833088.1480460408027--

1 0

planned jenkins and resources downtime
by Evgheni Dereveanchin 29 Nov '16

29 Nov '16

Hi everyone, As part of a planned maintenance window I am going to apply OS updates and reboot the Jenkins master along with our resources file server. Affected services: jenkins.ovirt.org resources.ovirt.org This means that no new jobs will be started on the Jenkins and our repositories will be unavailable for a short period of time. I will follow up on this email once all services are back up and running. Regards, Evgheni Dereveanchin

1 1

[JIRA] (OVIRT-882) Setup a lab to try out Zuul
by Barak Korren (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-882?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-882: ---------------------------------- Assignee: Barak Korren (was: infra) > Setup a lab to try out Zuul > --------------------------- > > Key: OVIRT-882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-882 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: Barak Korren > > OVIRT-734 and OVIRT-841 call for using Zuul to enable merge gating as well as resolve various CI reliability issues. > Before we can do that we need some kind of a lab setup so we can try out Zuul inspect its features and learn its properties. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-882) Setup a lab to try out Zuul
by Barak Korren (oVirt JIRA) 29 Nov '16

29 Nov '16

Barak Korren created OVIRT-882: ---------------------------------- Summary: Setup a lab to try out Zuul Key: OVIRT-882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-882 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Barak Korren Assignee: infra OVIRT-734 and OVIRT-841 call for using Zuul to enable merge gating as well as resolve various CI reliability issues. Before we can do that we need some kind of a lab setup so we can try out Zuul inspect its features and learn its properties. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-882) Setup a lab to try out Zuul
by Barak Korren (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-882?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-882: ------------------------------- Epic Link: OVIRT-403 > Setup a lab to try out Zuul > --------------------------- > > Key: OVIRT-882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-882 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: infra > > OVIRT-734 and OVIRT-841 call for using Zuul to enable merge gating as well as resolve various CI reliability issues. > Before we can do that we need some kind of a lab setup so we can try out Zuul inspect its features and learn its properties. -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-881) prepare for bugizlla 5 upgrade - api changes
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

eyal edri [Administrator] created OVIRT-881: ----------------------------------------------- Summary: prepare for bugizlla 5 upgrade - api changes Key: OVIRT-881 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-881 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra Priority: High oVirt Bugzilla will be upgraded to Bugzilla 5.0 in the following months, We should make sure all our automation still works with the new API and verify mostly Gerrit Hooks still works. Also, the new version will include RESTAPI as oppose to XMLRPC which was used until now. Worth looking for existing tools / SDKs which exists that we might be able to use. cc [~amarchuk] [~sbendavi(a)redhat.com] [~ederevea] -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-881) prepare for bugizlla 5 upgrade - api changes
by eyal edri [Administrator] (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-881?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-881: -------------------------------------------- Epic Link: OVIRT-411 > prepare for bugizlla 5 upgrade - api changes > -------------------------------------------- > > Key: OVIRT-881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-881 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > oVirt Bugzilla will be upgraded to Bugzilla 5.0 in the following months, > We should make sure all our automation still works with the new API and verify mostly Gerrit Hooks still works. > Also, the new version will include RESTAPI as oppose to XMLRPC which was used until now. > Worth looking for existing tools / SDKs which exists that we might be able to use. > cc [~amarchuk] [~sbendavi(a)redhat.com] [~ederevea] -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-880) foreman disk space warnings
by Evgheni Dereveanchin (oVirt JIRA) 29 Nov '16

29 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-880?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-880: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > foreman disk space warnings > --------------------------- > > Key: OVIRT-880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-880 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Nagios is reporting low disk on the Foreman master (20% free) -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0

[JIRA] (OVIRT-880) foreman disk space warnings
by Evgheni Dereveanchin (oVirt JIRA) 29 Nov '16

29 Nov '16

Evgheni Dereveanchin created OVIRT-880: ------------------------------------------ Summary: foreman disk space warnings Key: OVIRT-880 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-880 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Nagios is reporting low disk on the Foreman master (20% free) -- This message was sent by Atlassian JIRA (v1000.586.0#100022)

1 0