- Infra - oVirt List Archives

[JIRA] (OVIRT-801) [gerrit hooks] enable check_bug_url for master branch
by Shlomo Ben David (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-801?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-801: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] enable check_bug_url for master branch > ----------------------------------------------------- > > Key: OVIRT-801 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-801 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > - Currently we are not checking bug urls for master branch. > - We need to enable check_bug_url for master branch and set it to be optional for 'master' > branch but mandatory for 'stable' branches. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[oVirt Jenkins] 'test-repo_ovirt_experimental_3.6' - Build #3149 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_411_199881220.1477928070722 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/3149/, Build Number: 3149, Build Status: SUCCESS ------=_Part_411_199881220.1477928070722--

1 0

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5
by sbonazzo (oVirt JIRA) 31 Oct '16

31 Oct '16

sbonazzo created OVIRT-800: ------------------------------ Summary: Build oVirt 4.0.5 RC5 Key: OVIRT-800 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-800 Project: oVirt - virtualization made easy Issue Type: Task Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5
by sbonazzo (oVirt JIRA) 31 Oct '16

31 Oct '16

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

1 0

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5
by sbonazzo (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-800?page=com.atlassian.jira.p… ] sbonazzo reassigned OVIRT-800: ------------------------------ Assignee: lveyde (was: infra) > Build oVirt 4.0.5 RC5 > --------------------- > > Key: OVIRT-800 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-800 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: lveyde > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

Subject: oVirt 4.0.5 RC5 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 31 Oct '16

31 Oct '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.5, tr: 4.0.5) A list of bugs that require attention is here: - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>

1 0

Gerrit emails - Returned mail: see transcript for details
by Martin Sivak 31 Oct '16

31 Oct '16

Hi, there might be something bad in our SPF config. Please check. Martin ---------- Forwarded message ---------- From: Mail Delivery Subsystem <MAILER-DAEMON(a)gerrit.ovirt.org> Date: Mon, Oct 31, 2016 at 2:05 PM Subject: Returned mail: see transcript for details To: msivak(a)redhat.com The original message was received at Mon, 31 Oct 2016 09:05:24 -0400 from gerrit.ovirt.org [127.0.0.1] ----- The following addresses had permanent fatal errors ----- <laravot(a)redhat.com> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT) <akrejcir(a)redhat.com> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT) <ahadas(a)redhat.com> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT) ----- Transcript of session follows ----- ... while talking to mx1.redhat.com.: >>> DATA <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT 550 5.1.1 <ahadas(a)redhat.com>... User unknown <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT 550 5.1.1 <akrejcir(a)redhat.com>... User unknown <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT 550 5.1.1 <laravot(a)redhat.com>... User unknown <<< 554 5.5.1 Error: no valid recipients Final-Recipient: RFC822; laravot(a)redhat.com Action: failed Status: 5.7.1 Remote-MTA: DNS; mx1.redhat.com Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400 Final-Recipient: RFC822; akrejcir(a)redhat.com Action: failed Status: 5.7.1 Remote-MTA: DNS; mx1.redhat.com Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400 Final-Recipient: RFC822; ahadas(a)redhat.com Action: failed Status: 5.7.1 Remote-MTA: DNS; mx1.redhat.com Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400 ---------- Forwarded message ---------- From: msivak(a)redhat.com To: Arik Hadas <ahadas(a)redhat.com> Cc: Andrej Krejcir <akrejcir(a)redhat.com>, Liron Aravot <laravot(a)redhat.com> Date: Mon, 31 Oct 2016 09:05:24 -0400 Subject: Change in ovirt-engine[master]: core: Update OVF in storage domains for HE VM edit Hello Arik Hadas, I'd like you to do a code review. Please visit https://gerrit.ovirt.org/65085 to review the following change. Change subject: core: Update OVF in storage domains for HE VM edit ...................................................................... core: Update OVF in storage domains for HE VM edit Updating hosted engine VM saves OVF to storage domain as well as to the DB. This patch is complementary to: https://gerrit.ovirt.org/#/c/51842 Change-Id: Ib02d41136458677399428c62c8e475b4cb2fcb79 Bug-Url: https://bugzilla.redhat.com/1372000 Signed-off-by: Andrej Krejcir <akrejcir(a)redhat.com> --- M backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java M backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java 2 files changed, 22 insertions(+), 22 deletions(-) git pull ssh://gerrit.ovirt.org:29418/ovirt-engine refs/changes/85/65085/3 diff --git a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java index 3c0bada..9c64003 100644 --- a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java +++ b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java @@ -22,6 +22,7 @@ import org.ovirt.engine.core.bll.quota.QuotaConsumptionParameter; import org.ovirt.engine.core.bll.quota.QuotaSanityParameter; import org.ovirt.engine.core.bll.quota.QuotaVdsDependent; +import org.ovirt.engine.core.bll.storage.ovfstore.OvfDataUpdater; import org.ovirt.engine.core.bll.utils.IconUtils; import org.ovirt.engine.core.bll.utils.PermissionSubject; import org.ovirt.engine.core.bll.validator.IconValidator; @@ -37,7 +38,6 @@ import org.ovirt.engine.core.common.action.LockProperties; import org.ovirt.engine.core.common.action.LockProperties.Scope; import org.ovirt.engine.core.common.action.PlugAction; -import org.ovirt.engine.core.common.action.ProcessOvfUpdateForStoragePoolParameters; import org.ovirt.engine.core.common.action.RngDeviceParameters; import org.ovirt.engine.core.common.action.UpdateVmVersionParameters; import org.ovirt.engine.core.common.action.VdcActionType; @@ -178,7 +178,17 @@ // Trigger OVF update for hosted engine VM only if (getVm().isHostedEngine()) { - registerRollbackHandler(new HostedEngineEditNotifier(getVm())); + registerRollbackHandler(new TransactionCompletionListener() { + @Override + public void onSuccess() { + OvfDataUpdater.getInstance().triggerNow(); + } + + @Override + public void onRollback() { + // No notification is needed + } + }); } // save user selected value for hotplug before overriding with db values (when updating running vm) @@ -1150,25 +1160,6 @@ public VmValidator createVmValidator(VM vm) { return new VmValidator(vm); - } - - private static class HostedEngineEditNotifier implements TransactionCompletionListener { - final VM vm; - - public HostedEngineEditNotifier(VM vm) { - this.vm = vm; - } - - @Override - public void onSuccess() { - Backend.getInstance().runInternalAction(VdcActionType.ProcessOvfUpdateForStoragePool, - new ProcessOvfUpdateForStoragePoolParameters(vm.getStoragePoolId())); - } - - @Override - public void onRollback() { - // No notification is needed - } } protected InClusterUpgradeValidator getClusterUpgradeValidator() { diff --git a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java index 6dc3881..788e046 100644 --- a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java +++ b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java @@ -27,6 +27,8 @@ private static final Logger log = LoggerFactory.getLogger(OvfDataUpdater.class); private static final OvfDataUpdater INSTANCE = new OvfDataUpdater(); + private volatile String updateTimerJobId; + private OvfDataUpdater() { } @@ -40,7 +42,7 @@ public void initOvfDataUpdater() { SchedulerUtil scheduler = Injector.get(SchedulerUtilQuartzImpl.class); - scheduler.scheduleAFixedDelayJob(this, "ovfUpdateTimer", new Class[] {}, + updateTimerJobId = scheduler.scheduleAFixedDelayJob(this, "ovfUpdateTimer", new Class[] {}, new Object[] {}, Config.<Integer> getValue(ConfigValues.OvfUpdateIntervalInMinutes), Config.<Integer> getValue(ConfigValues.OvfUpdateIntervalInMinutes), TimeUnit.MINUTES); log.info("Initialization of OvfDataUpdater completed successfully."); @@ -84,4 +86,11 @@ } } } + + public void triggerNow() { + if (updateTimerJobId != null) { + SchedulerUtil scheduler = Injector.get(SchedulerUtilQuartzImpl.class); + scheduler.triggerJob(updateTimerJobId); + } + } } -- To view, visit https://gerrit.ovirt.org/65085 To unsubscribe, visit https://gerrit.ovirt.org/settings Gerrit-MessageType: newchange Gerrit-Change-Id: Ib02d41136458677399428c62c8e475b4cb2fcb79 Gerrit-PatchSet: 3 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Andrej Krejcir <akrejcir(a)redhat.com> Gerrit-Reviewer: Andrej Krejcir <akrejcir(a)redhat.com> Gerrit-Reviewer: Arik Hadas <ahadas(a)redhat.com> Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Jenny Tokar <jtokar(a)redhat.com> Gerrit-Reviewer: Liron Aravot <laravot(a)redhat.com> Gerrit-Reviewer: Martin Sivák <msivak(a)redhat.com> Gerrit-Reviewer: Phillip Bailey <phbailey(a)redhat.com> Gerrit-Reviewer: Roman Mohr <rmohr(a)redhat.com> Gerrit-Reviewer: Yanir Quinn <yquinn(a)redhat.com> Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org>

2 1

[JIRA] (OVIRT-799) Gerrit emails - Returned mail: see transcript for details
by Evgheni Dereveanchin (oVirt JIRA) 31 Oct '16

31 Oct '16

Evgheni Dereveanchin created OVIRT-799: ------------------------------------------ Summary: Gerrit emails - Returned mail: see transcript for details Key: OVIRT-799 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-799 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Mails coming from Gerrit are rejected by Red Hat due to the change in SPF policy enforcement: <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT This likely happens due to the fact that Gerrit uses the authors emails in the From: field which is likely to be marked as SPAM. We should use a sender address in the ovirt.org domain for all mail sent by Gerrit to avoid this. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-799) Gerrit emails - Returned mail: see transcript for details
by Evgheni Dereveanchin (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-799?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-799: ------------------------------------------ Assignee: Shlomo Ben David (was: infra) > Gerrit emails - Returned mail: see transcript for details > --------------------------------------------------------- > > Key: OVIRT-799 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-799 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Shlomo Ben David > > Mails coming from Gerrit are rejected by Red Hat due to the change in SPF policy enforcement: > <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT > This likely happens due to the fact that Gerrit uses the authors emails in the From: field which is likely to be marked as SPAM. We should use a sender address in the ovirt.org domain for all mail sent by Gerrit to avoid this. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-776) Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402
by Evgheni Dereveanchin (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-776?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-776: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402 > ----------------------------------------------------------- > > Key: OVIRT-776 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-776 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Looks like a network issue, scp fails with a timeout on a socket. > Can you please have a look? > On Mon, Oct 17, 2016 at 10:22 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > See <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/changes> > > > > Changes: > > > > [Gal Ben Haim] Fix check-patch to collect logs on failure > > > > ------------------------------------------ > > [...truncated 1897 lines...] > > ## took 2809 seconds > > ## rc = 1 > > ########################################################## > > ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv > > ##! Last 20 log enties: logs/mocker-fedora-23-x86_64. > > fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log > > ##! > > + true > > + env_cleanup > > + echo '#########################' > > ######################### > > + local res=0 > > + local uuid > > + echo '======== Cleaning up' > > ======== Cleaning up > > + [[ -e <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/deployment-he_basic_suite_4.0> ]] > > + echo '----------- Cleaning with lago' > > ----------- Cleaning with lago > > + lago --workdir <http://jenkins.ovirt.org/job/ > > ovirt_4.0_he-system-tests/ws/ovirt-system-tests/deployment- > > he_basic_suite_4.0> destroy --yes --all-prefixes > > + echo '----------- Cleaning with lago done' > > ----------- Cleaning with lago done > > + [[ 0 != \0 ]] > > + echo '======== Cleanup done' > > ======== Cleanup done > > + exit 0 > > Took 2642 seconds > > =================================== > > ##! > > ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > ##!######################################################## > > ########################################################## > > Build step 'Execute shell' marked build as failure > > Performing Post build task... > > Match found for :.* : True > > Logical operation result is TRUE > > Running script : #!/bin/bash -xe > > echo 'shell_scripts/system_tests.collect_logs.sh' > > > > # > > # Required jjb vars: > > # version > > # > > VERSION=4.0 > > SUITE_TYPE= > > > > WORKSPACE="$PWD" > > OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" > > TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" > > > > rm -rf "$WORKSPACE/exported-artifacts" > > mkdir -p "$WORKSPACE/exported-artifacts" > > > > if [[ -d "$TESTS_LOGS" ]]; then > > mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" > > fi > > > > [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/ > > hudson4967817357021364058.sh > > + echo shell_scripts/system_tests.collect_logs.sh > > shell_scripts/system_tests.collect_logs.sh > > + VERSION=4.0 > > + SUITE_TYPE= > > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > + OVIRT_SUITE=4.0 > > + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests/exported-artifacts> > > + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts> > > + mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts> > > + [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts> ]] > > + mv <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/lago_logs> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/nosetests-002_bootstrap.py.xml> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/nosetests-004_basic_sanity.py.xml> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/exported-artifacts/test_logs> < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/ > > artifact/exported-artifacts/> > > POST BUILD TASK : SUCCESS > > END OF POST BUILD TASK : 0 > > Match found for :.* : True > > Logical operation result is TRUE > > Running script : #!/bin/bash -xe > > echo "shell-scripts/mock_cleanup.sh" > > > > shopt -s nullglob > > > > > > WORKSPACE="$PWD" > > > > # Make clear this is the cleanup, helps reading the jenkins logs > > cat <<EOC > > _______________________________________________________________________ > > ####################################################################### > > # # > > # CLEANUP # > > # # > > ####################################################################### > > EOC > > > > > > # Archive the logs, we want them anyway > > logs=( > > ./*log > > ./*/logs > > ) > > if [[ "$logs" ]]; then > > tar cvzf exported-artifacts/logs.tgz "${logs[@]}" > > rm -rf "${logs[@]}" > > fi > > > > # stop any processes running inside the chroot > > failed=false > > mock_confs=("$WORKSPACE"/*/mocker*) > > # Clean current jobs mockroot if any > > for mock_conf_file in "${mock_confs[@]}"; do > > [[ "$mock_conf_file" ]] || continue > > echo "Cleaning up mock $mock_conf" > > mock_root="${mock_conf_file##*/}" > > mock_root="${mock_root%.*}" > > my_mock="/usr/bin/mock" > > my_mock+=" --configdir=${mock_conf_file%/*}" > > my_mock+=" --root=${mock_root}" > > my_mock+=" --resultdir=$WORKSPACE" > > > > #TODO: investigate why mock --clean fails to umount certain dirs > > sometimes, > > #so we can use it instead of manually doing all this. > > echo "Killing all mock orphan processes, if any." > > $my_mock \ > > --orphanskill \ > > || { > > echo "ERROR: Failed to kill orphans on $chroot." > > failed=true > > } > > > > mock_root="$(\ > > grep \ > > -Po "(?<=config_opts\['root'\] = ')[^']*" \ > > "$mock_conf_file" \ > > )" || : > > [[ "$mock_root" ]] || continue > > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > > if [[ "$mounts" ]]; then > > echo "Found mounted dirs inside the chroot $chroot. Trying to > > umount." > > fi > > for mount in "${mounts[@]}"; do > > sudo umount --lazy "$mount" \ > > || { > > echo "ERROR: Failed to umount $mount." > > failed=true > > } > > done > > done > > > > # Clean any leftover chroot from other jobs > > for mock_root in /var/lib/mock/*; do > > this_chroot_failed=false > > mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : > > if [[ "$mounts" ]]; then > > echo "Found mounted dirs inside the chroot $mock_root." \ > > "Trying to umount." > > fi > > for mount in "${mounts[@]}"; do > > sudo umount --lazy "$mount" \ > > || { > > echo "ERROR: Failed to umount $mount." > > failed=true > > this_chroot_failed=true > > } > > done > > if ! $this_chroot_failed; then > > sudo rm -rf "$mock_root" > > fi > > done > > > > if $failed; then > > echo "Aborting." > > exit 1 > > fi > > > > # remove mock system cache, we will setup proxies to do the caching and > > this > > # takes lots of space between runs > > shopt -u nullglob > > sudo rm -Rf /var/cache/mock/* > > > > # restore the permissions in the working dir, as sometimes it leaves files > > # owned by root and then the 'cleanup workspace' from jenkins job fails to > > # clean and breaks the jobs > > sudo chown -R "$USER" "$WORKSPACE" > > > > [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/ > > hudson2195449912416509862.sh > > + echo shell-scripts/mock_cleanup.sh > > shell-scripts/mock_cleanup.sh > > + shopt -s nullglob > > + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > + cat > > _______________________________________________________________________ > > ####################################################################### > > # # > > # CLEANUP # > > # # > > ####################################################################### > > + logs=(./*log ./*/logs) > > + [[ -n ./ovirt-system-tests/logs ]] > > + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs > > ./ovirt-system-tests/logs/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_ > > basic_suite_4.0.sh/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/state.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/build.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/stdout_stderr.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > install_packages/root.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > init/stdout_stderr.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ > > ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. > > clean_rpmdb/stdout_stderr.log > > + rm -rf ./ovirt-system-tests/logs > > + failed=false > > + mock_confs=("$WORKSPACE"/*/mocker*) > > + for mock_conf_file in '"${mock_confs[@]}"' > > + [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> ]] > > + echo 'Cleaning up mock ' > > Cleaning up mock > > + mock_root=mocker-fedora-23-x86_64.fc23.cfg > > + mock_root=mocker-fedora-23-x86_64.fc23 > > + my_mock=/usr/bin/mock > > + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests'> > > + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' > > + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/'> > > + echo 'Killing all mock orphan processes, if any.' > > Killing all mock orphan processes, if any. > > + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he- > > system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 > > --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/> > > --orphanskill > > WARNING: Could not find required logging config file: < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/logging.ini.> Using default... > > INFO: mock.py version 1.2.18 starting (python version = 3.4.3)... > > Start: init plugins > > INFO: selinux enabled > > Finish: init plugins > > Start: run > > Finish: run > > ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' < > > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/ > > ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> > > + mock_root=fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad > > + [[ -n fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad ]] > > + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) > > ++ mount > > ++ awk '{print $3}' > > ++ grep fedora-23-x86_64-0c362156a2fa4a935ea8b988eb73b2ad > > + : > > + [[ -n '' ]] > > + false > > + shopt -u nullglob > > + sudo rm -Rf /var/cache/mock/fedora-23-x86_64- > > 0c362156a2fa4a935ea8b988eb73b2ad > > + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ > > ovirt_4.0_he-system-tests/ws/> > > POST BUILD TASK : SUCCESS > > END OF POST BUILD TASK : 1 > > Recording test results > > Archiving artifacts > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by danken (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] danken commented on OVIRT-757: ------------------------------ Thanks. https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered automatically right after I've merged a patch to vdsm's gerrit. > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-757: ------------------------------------ Enabled travis on vds repo: https://travis-ci.org/oVirt/vdsm Please check if it works for you > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

2 1

SSL Server Test: www.ovirt.org (Powered by Qualys SSL Labs)
by Yaniv Kaul 31 Oct '16

31 Oct '16

Someone tweeted about our incomplete certificate chain - see https://www.ssllabs.com/ssltest/analyze.html?d=www.ovirt.org

3 2

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Juan Hernández (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-761: -------------------------------------- CC [~omachace(a)redhat.com] Travis CI integration for the Python SDK is now enabled. For future releases it would be good to make sure that the build in Mac OS X works before actually releasing the new version. > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-798?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-798: ------------------------------------------------- We already got a few reports on this, [~duck][~sbendavi(a)redhat.com] can you have a look? > outgoing mail failure - SPF fail > -------------------------------- > > Key: OVIRT-798 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > When adding a reviewer to a patch on gerrit, I get an email: > The original message was received at Mon, 31 Oct 2016 05:07:32 -0400 > from gerrit.ovirt.org [127.0.0.1] > ----- The following addresses had permanent fatal errors ----- > <sbonazzo(a)redhat.com> > (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], > 'redhat.com'; REJECT) > ----- Transcript of session follows ----- > ... while talking to mx1.redhat.com.: > >>> DATA > <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT > 550 5.1.1 <sbonazzo(a)redhat.com>... User unknown > <<< 554 5.5.1 Error: no valid recipients > Final-Recipient: RFC822; sbonazzo(a)redhat.com > Action: failed > Status: 5.7.1 > Remote-MTA: DNS; mx1.redhat.com > Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: > 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT > Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400 > Please check/handle. Thanks. > -- > Didi -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail
by Yedidyah Bar David (oVirt JIRA) 31 Oct '16

31 Oct '16

Yedidyah Bar David created OVIRT-798: ---------------------------------------- Summary: outgoing mail failure - SPF fail Key: OVIRT-798 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi, When adding a reviewer to a patch on gerrit, I get an email: The original message was received at Mon, 31 Oct 2016 05:07:32 -0400 from gerrit.ovirt.org [127.0.0.1] ----- The following addresses had permanent fatal errors ----- <sbonazzo(a)redhat.com> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT) ----- Transcript of session follows ----- ... while talking to mx1.redhat.com.: >>> DATA <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT 550 5.1.1 <sbonazzo(a)redhat.com>... User unknown <<< 554 5.5.1 Error: no valid recipients Final-Recipient: RFC822; sbonazzo(a)redhat.com Action: failed Status: 5.7.1 Remote-MTA: DNS; mx1.redhat.com Diagnostic-Code: SMTP; 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400 Please check/handle. Thanks. -- Didi -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-757: ---------------------------------- Assignee: Barak Korren (was: infra) > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-757: ------------------------------- Status: In Progress (was: To Do) > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-790) 732846953375 infra-support
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-790?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-790: -------------------------------------------- > 732846953375 infra-support > -------------------------- > > Key: OVIRT-790 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-790 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: m.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Juan Hernández (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-761: -------------------------------------- Thank you very much Barak. I agree, lets test Travis for a while before making any other change. > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-761: ------------------------------- Status: In Progress (was: To Do) > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-761: ------------------------------------ I've enabled Python and Ruby SDKs in Travis: https://travis-ci.org/oVirt/ovirt-engine-sdk-ruby https://travis-ci.org/oVirt/ovirt-engine-sdk To have a Mac OS X slave we'll need buy/have it donated, Lets see of travis is good enough for now. It should be possible to run Standard-CI scripts from travis to avoid some code duplication. > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Barak Korren (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-761: ---------------------------------- Assignee: Barak Korren (was: infra) > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?
by Juan Hernández (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-761?page=com.atlassian.jira.p… ] Juan Hernández commented on OVIRT-761: -------------------------------------- Not sure what permissions are needed exactly, but I think that those that have "admin" access to the "oVirt" organization can just go to travis-ci.org and enable/disable the projects, it is just a matter of flipping a switch. I'd appreciate someone with that access can do it for the Python and Ruby SDKs, as we had already more than one situation where Mac OS X users complained about build failures. I also suggest to reconsider adding support for Mac OS X to Jenkins. I know that it isn't possible to have a Mac OS X VM, but maybe we could have at least one bare metal Mac OS X slave. > Re: Do we or can we have Mac OS slaves in Jenkins? > -------------------------------------------------- > > Key: OVIRT-761 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Opening a ticket. > On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández <jhernand(a)redhat.com> > wrote: > > Hello, > > > > Part of the Ruby SDK uses native code that needs to be compiled during > > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and > > many ManageIQ developers/users use Mac OS. In the past I had some issues > > with this environment, as the C compiler there behaves in an slightly > > different way than GCC. Those issues were discovered only when the SDK > > was already released. To avoid that I would like to have Jenkins jobs > > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS > > slaves? If not, can we have them? > > > > Regards, > > Juan Hernandez > > > > -- > > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > > 3ºD, 28016 Madrid, Spain > > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-753: -------------------------------------------- Blocked By: pending response from node team Status: Blocked (was: To Do) Should be handled by node team, as the code is in the appliance repo. > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-753: ------------------------------------------------- [~fdeutsch] I'm guessing Tolik wrote this job? can anyone from the node team have a look and fail early on the code? > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-750) Issues with mvn central syncrhronization
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-750?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-750: ------------------------------------------------- does it still happen? > Issues with mvn central syncrhronization > ---------------------------------------- > > Key: OVIRT-750 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-750 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > When I release new version of jsonrpc and update the engine to use it the > build fails and it is required to manually perform refresh of artifactory > cache. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-751) Persistent maven caches on the mock slaves
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-751?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-751: ------------------------------------------------- I think we should give it a try for ovirt-engine and be proactive on this, since it also serve us as it will reduce load on network and jenkins server and also reduce feedback time to check-patch jobs. If its a simple patch, lets just send it and check it out, shouldn't take too much time. > Persistent maven caches on the mock slaves > ------------------------------------------ > > Key: OVIRT-751 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-751 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > I think we need to design a way to retain maven caches on the mocked jenkins slaves. Currently it is stored inside the mock and thus maven downloads packages from artifactory server each time. > However there is really no reason for that. Maven artifacts are designed to be immutable so once artifact is in the repo there is no trivial way to change it without creating a new version. In fact it should never be needed and the correct solution for that is to always create a new version. > SNAPSHOOT artifacts are in fact timestamped and each one have different file name. It is just not visible since maven automatically takes the latest one. But it is not related to caching as the new snapshoot will be a new artifact still. > So based on that point there is no reason to purge maven cache each time, but there are reasons why not to purge. Not purging them will reduce the build times of all java jobs and also reduce the network traffic we have. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-752) Fwd: export ovirt-engine-dashboard gerrit repo to github?
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-752?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-752: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) Evgheni, can you have a look at this? I think we documented the procedure on how do to do it here: http://infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects… > Fwd: export ovirt-engine-dashboard gerrit repo to github? > --------------------------------------------------------- > > Key: OVIRT-752 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-752 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Opening a ticket. Looks like we're missing backup on github for > ovirt-dashboard. > ---------- Forwarded message ---------- > From: Scott Dickerson <sdickers(a)redhat.com> > Date: Thu, Oct 6, 2016 at 5:53 PM > Subject: export ovirt-engine-dashboard gerrit repo to github? > To: infra(a)ovirt.org > Hi, > What do we need to do in order to get the ovirt-engine-dashboard gerrit > repo [1] mirrored/exported out to oVirt's github [2] in the same way > ovirt-engine does? > [1] - https://gerrit.ovirt.org/gitweb?p=ovirt-engine-dashboard.git;a=summary > [2] - https://github.com/oVirt > Thanks, > Scott > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-760?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-760: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) Shlomi, can you please add all the bug status changing hooks to this project? > Gerrit hooks for ovirt-imageio project > -------------------------------------- > > Key: OVIRT-760 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Shlomo Ben David > > Hi,can you please add gerrit hooks to ovirt-imageio project? > Thanks > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-766) Code Review - Error invalid author
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-766?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-766: -------------------------------------------- Resolution: Fixed Status: Done (was: Blocked) > Code Review - Error invalid author > ---------------------------------- > > Key: OVIRT-766 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-766 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > While editing a commit message or a file from gerrit I get: > Code Review - Error invalid author > when I save and publish the change. > Can you please fix it? > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-766) Code Review - Error invalid author
by sbonazzo (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-766?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-766: -------------------------------- [~eedri] yes it was solved, thanks. > Code Review - Error invalid author > ---------------------------------- > > Key: OVIRT-766 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-766 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > While editing a commit message or a file from gerrit I get: > Code Review - Error invalid author > when I save and publish the change. > Can you please fix it? > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project
by sbonazzo (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-760?page=com.atlassian.jira.p… ] sbonazzo commented on OVIRT-760: -------------------------------- > Can you please specify which hooks do you want enabled? those updating bugzilla status > Gerrit hooks for ovirt-imageio project > -------------------------------------- > > Key: OVIRT-760 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi,can you please add gerrit hooks to ovirt-imageio project? > Thanks > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by danken (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] danken commented on OVIRT-757: ------------------------------ It would be Vdsm's unit tests, which are also run by check-patch. vdsm source tree already has .travis.yml which github uses to trigger Travis runs We love jenkins CI and we don't want to replace it, only augment, with very little cost to the ovirt project. Travis has a nice look-and-feel; but more importantly, it keeps the outcome of jobs indefinitely. We'd like to see TravisCI for for the very same reason we have a github mirror to our gerrit: github provides a widely-used platform, that might be more approachable to the general public, even though I personally like it less. > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project
by eyal edri [Administrator] (oVirt JIRA) 31 Oct '16

31 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-757: ------------------------------------------------- Few questions: 1. Which tests will run there? same as check-patch/check-merged? 2. How will the travis configuration be managed/configured 3. Why use another CI system when we can run it on jenkins.ovirt.org? is there any limitation to existing jenkins server that Travis doesn't have? can you elaborate? > [VDSM] Add Travis CI to vdsm github project > ------------------------------------------- > > Key: OVIRT-757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now a travis configuration running vdsm tests > on both Fedora 24 and Centos 7. > You can see example build shere: > https://travis-ci.org/nirs/vdsm/builds/166263228 > These builds are currently configured in my private vdsm > fork on github. > We want to enable Travis CI service on vdsm github project, > so each time a patch is merged (sync from gerrit) or each time > a pull request is submitted, a build is started. > Developers can use these builds in 2 ways: > - fork vdsm and enable travis on their fork > - submit pull requests to get them tested > When a build fails, travis sends email to the author about the > failure, this works fine for developers forks without any > additional configuration. > You can configure github for us, or give Dan and/or me the > permissions to configure the github project. > Cheers, > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

2 1

oVirt infra daily report - unstable production jobs - 123
by jenkins＠jenkins.phx.ovirt.org 31 Oct '16

31 Oct '16

------=_Part_404_2004505292.1477868406756 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/123//artifact/exported-a… Cheers, Jenkins ------=_Part_404_2004505292.1477868406756 Content-Type: application/octet-stream; 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/10/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/deploy-to-ovirt_experimental_master/">deploy-to-ovirt_experimental_master</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-model_4.0_build-artifacts-fc2…">ovirt-engine-api-model_4.0_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-engine_master_build-artifacts-el7-x86_64/">ovirt-engine_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-engine_master_coverity-analysis/">ovirt-engine_master_coverity-analysis</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_upgrade-from-3.6_el7_merge…">ovirt-engine_master_upgrade-from-3.6_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-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-release_master_build-artifacts-all-x86_6…">ovirt-release_master_build-artifacts-all-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_3.6_he-system-tests/">ovirt_3.6_he-system-tests</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_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</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_4.0_he-system-tests/">ovirt_4.0_he-system-tests</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/repoman_master_check-merged-el6-x86_64/">repoman_master_check-merged-el6-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/repoman_master_check-merged-el7-x86_64/">repoman_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/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/scan_security_and_license_ovirt-engine_master/">scan_security_and_license_ovirt-engine_master</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/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</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/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</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/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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_404_2004505292.1477868406756--

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-797?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-797: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] update tracker failed to update bugs > --------------------------------------------------- > > Key: OVIRT-797 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > Priority: High > > bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, > it only returns True if the passed value is True, False otherwise. > I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

Shlomo Ben David created OVIRT-797: -------------------------------------- Summary: [gerrit hooks] update tracker failed to update bugs Key: OVIRT-797 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomo Ben David Assignee: infra Priority: High bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, it only returns True if the passed value is True, False otherwise. I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-797) [gerrit hooks] update tracker failed to update bugs
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-797?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-797: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] update tracker failed to update bugs > --------------------------------------------------- > > Key: OVIRT-797 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-797 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomo Ben David > Assignee: infra > Priority: High > > bool(x) function isn't converts 'True' | 'False' strings into bool (True | False) values, > it only returns True if the passed value is True, False otherwise. > I've replaced it with ast.literal_eval() function that converts and returns the required bool values. -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-796?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-796: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] recreate set_post hook > ------------------------------------- > > Key: OVIRT-796 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > > The new hook will follow the bellow guidelines: > * It updates only u/s bugs (oVirt classification) > * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

Shlomo Ben David created OVIRT-796: -------------------------------------- Summary: [gerrit hooks] recreate set_post hook Key: OVIRT-796 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra The new hook will follow the bellow guidelines: * It updates only u/s bugs (oVirt classification) * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-796) [gerrit hooks] recreate set_post hook
by Shlomo Ben David (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-796?page=com.atlassian.jira.p… ] Shlomo Ben David updated OVIRT-796: ----------------------------------- Epic Link: OVIRT-403 > [gerrit hooks] recreate set_post hook > ------------------------------------- > > Key: OVIRT-796 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-796 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > > The new hook will follow the bellow guidelines: > * It updates only u/s bugs (oVirt classification) > * It updates the bug status in bugzilla only from NEW to POST -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-758) Vdsm docker testing images
by Barak Korren (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-758: ------------------------------------ Building and publishing Docker images should be quite simple to do from std-ci. There is no technical reason why this couldn`t be done directly in VDSM's check-patch.sh or build-artifacts.sh. But maybe mock will require some tweaking. But perhaps the docker files shouldn't be in the vdsm repo for the sake of not building them unnecessarily, this can also be avoided with a simple condition in the script file though. > Vdsm docker testing images > -------------------------- > > Key: OVIRT-758 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images. > See https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:d… > Currently I maintain the images in docker hub: > - https://hub.docker.com/r/nirs/vdsm-centos/ > - https://hub.docker.com/r/nirs/vdsm-fedora/ > I configured automatic build, so each time I push a change to this branch: > https://github.com/nirs/vdsm/tree/dockerfile > Docker go and rebuilds the images. > We want to move the images to docker hub ovirt account: > https://hub.docker.com/u/ovirt/ > And configure vdsm github project so docker will rebuild > the images when we push a changes to the dockerfile branch, > or another solution to allow easy update of the images by > merging a new dockerfile. > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-754) Guest name 'TestNode-node' is already in use.
by eyal edri [Administrator] (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-754?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-754: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) since the patch with the cleanup was merged, setting as resolved. Please reopen if the problem wasn't fixed. > Guest name 'TestNode-node' is already in use. > --------------------------------------------- > > Key: OVIRT-754 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-754 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > ====================================================================== > ERROR: test suite for <class 'testSanity.TestNode'> > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 208, in run > self.setUp() > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 291, in setUp > self.setupContext(ancestor) > File "/usr/lib/python2.7/site-packages/nose/suite.py", line 314, in > setupContext > try_run(context, names) > File "/usr/lib/python2.7/site-packages/nose/util.py", line 469, in try_run > return func() > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/testVirt.py", > line 150, in setUpClass > 77) > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/testVirt.py", > line 88, in _start_vm > dom = VM.create(name, img, ssh_port=ssh_port, memory_gb=memory_gb) > File > "/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng/tests/virt.py", > line 217, in create > dom = sh.virt_install(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/sh.py", line 1021, in __call__ > return RunningCommand(cmd, call_args, stdin, stdout, stderr) > File "/usr/lib/python2.7/site-packages/sh.py", line 486, in __init__ > self.wait() > File "/usr/lib/python2.7/site-packages/sh.py", line 500, in wait > self.handle_command_exit_code(exit_code) > File "/usr/lib/python2.7/site-packages/sh.py", line 516, in > handle_command_exit_code > raise exc(self.ran, self.process.stdout, self.process.stderr) > ErrorReturnCode_1: > RAN: '/bin/virt-install --import --print-xml --network=user,model=virtio > --noautoconsole --memory=2048 --rng=/dev/random --memballoon=virtio > --cpu=host --vcpus=4 --graphics=vnc --watchdog=default,action=poweroff > --serial=pty > --disk=path=/var/tmp/TestNode-node.qcow2,bus=virtio,format=qcow2,driver_type=qcow2,discard=unmap,cache=unsafe > --check=all=off --channel=unix,target_type=virtio,name=local.test.0 > --name=TestNode-node' > STDOUT: > STDERR: > ERROR Guest name 'TestNode-node' is already in use. > Seems to be a run in a not clean environment. Not sure about what caused > this. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-758) Vdsm docker testing images
by eyal edri [Administrator] (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-758: ------------------------------------------------- Is it possible to do it from Gerrit and not GitHub? [~bkorren(a)redhat.com][~ederevea] [~ngoldin(a)redhat.com] - We haven't talked about managing containers for oVirt yet (except for using OpenShift for the monitoring app), thoughts? > Vdsm docker testing images > -------------------------- > > Key: OVIRT-758 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Hi all, > Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images. > See https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:d… > Currently I maintain the images in docker hub: > - https://hub.docker.com/r/nirs/vdsm-centos/ > - https://hub.docker.com/r/nirs/vdsm-fedora/ > I configured automatic build, so each time I push a change to this branch: > https://github.com/nirs/vdsm/tree/dockerfile > Docker go and rebuilds the images. > We want to move the images to docker hub ovirt account: > https://hub.docker.com/u/ovirt/ > And configure vdsm github project so docker will rebuild > the images when we push a changes to the dockerfile branch, > or another solution to allow easy update of the images by > merging a new dockerfile. > Nir -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

Re: [ovirt-devel] [vdsm] branch ovirt-4.0.5 created
by Eyal Edri 30 Oct '16

30 Oct '16

On Mon, Oct 10, 2016 at 6:24 PM, Francesco Romani <fromani(a)redhat.com> wrote: > ----- Original Message ----- > > From: "Dan Kenigsberg" <danken(a)redhat.com> > > To: "Francesco Romani" <fromani(a)redhat.com> > > Cc: "Nir Soffer" <nsoffer(a)redhat.com>, devel(a)ovirt.org > > Sent: Monday, October 10, 2016 5:11:26 PM > > Subject: Re: [vdsm] branch ovirt-4.0.5 created > > > > On Mon, Oct 10, 2016 at 10:30:49AM -0400, Francesco Romani wrote: > > > Hi everyone, > > > > > > this time I choose to create the ovirt-4.0.5 branch. > > > I already merged some patches for 4.0.6. > > > > > > Unfortunately I branched a bit too early (from last tag :)) > > > > > > So patches > > > https://gerrit.ovirt.org/#/c/65303/1 > > > https://gerrit.ovirt.org/#/c/65304/1 > > > https://gerrit.ovirt.org/#/c/65305/1 > > > > > > Should be trivially mergeable - the only thing changed from ovirt-4.0 > > > counterpart > > > is the change-id. Please have a quick look just to doublecheck. > > > > Change-Id should be the same for a master patch and all of its backport. > > It seems that it was NOT changed, at least for > > https://gerrit.ovirt.org/#/q/I5cea6ec71c913d74d95317ff7318259d64b40969 > > which is a GOOD thing. > > Yes, sorry, indeed it is (and indeed it should not change). > > > I think we want to enable CI on the new 4.0.5 branch, right? Otherwise > > we'd need to fake the CI+1 flag until 4.0.5 is shipped. > > We should, but it is not urgently needed - just regular priority. > For the aforementioned first three patches especially I'm just overly > cautious. > > Was CI enabled for 4.0.5 branch? Adding infra as well. Shlomi, Did we enabled the regex for stable branch already and we don't need to manually update conf files? > -- > Francesco Romani > Red Hat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ > 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)

2 1

ovirt-engine-4.0.5 is not treated as a monitored stable branch
by Tal Nisan 30 Oct '16

30 Oct '16

This patch for example: https://gerrit.ovirt.org/#/c/65398/

4 8

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-763: ------------------------------------------------- You already have an option to specify a custom repo to use instead of the ones defined in the conf files. [~ngoldin(a)redhat.com] [~gbenhaim(a)redhat.com] do we have this feature documented on Lago docs? > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project
by eyal edri [Administrator] (oVirt JIRA) 30 Oct '16

30 Oct '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-760?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-760: ------------------------------------------------- Can you please specify which hooks do you want enabled? Shlomi, we should probably update the docs with the new avaiable hooks as well [1][2] [1] http://ovirt-gerrit-hooks.readthedocs.io/en/latest/ [2] http://infra-docs.readthedocs.io/en/latest/CI/Gerrit_Hooks.html On Mon, Oct 10, 2016 at 11:41 AM, sbonazzo (oVirt JIRA) < -- 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) > Gerrit hooks for ovirt-imageio project > -------------------------------------- > > Key: OVIRT-760 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi,can you please add gerrit hooks to ovirt-imageio project? > Thanks > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.3#100017)

1 0

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project
by sbonazzo (oVirt JIRA) 30 Oct '16

30 Oct '16

sbonazzo created OVIRT-760: ------------------------------ Summary: Gerrit hooks for ovirt-imageio project Key: OVIRT-760 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi,can you please add gerrit hooks to ovirt-imageio project? Thanks -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.383.2#100014)

2 1