[JIRA] (OVIRT-1851) Make chaneg-queue throw-away not-building patches quickly
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1851?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1851:
--------------------------------
Epic Link: OVIRT-400
> Make chaneg-queue throw-away not-building patches quickly
> ---------------------------------------------------------
>
> Key: OVIRT-1851
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1851
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Change Queue
> Reporter: Barak Korren
> Assignee: infra
>
> Currently test failures and build failures are treated the same by the check queue - in both cases the change queue runs a bisection to find out the change that caused the failure.
> It the case of a build failure - it is possible to know immediately which patch failed to build, so we can remove it immediately from the queue and avoid some expensive bisection runs.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100076)
6 years, 5 months
[JIRA] (OVIRT-1851) Make chaneg-queue throw-away not-building patches quickly
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1516275013-22664-382
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1851:
-----------------------------------
Summary: Make chaneg-queue throw-away not-building patches quickly
Key: OVIRT-1851
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1851
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra
Currently test failures and build failures are treated the same by the check queue - in both cases the change queue runs a bisection to find out the change that caused the failure.
It the case of a build failure - it is possible to know immediately which patch failed to build, so we can remove it immediately from the queue and avoid some expensive bisection runs.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100076)
------------=_1516275013-22664-382
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1851:</h3>
<pre> Summary: Make chaneg-queue throw-away not-building patches quickly
Key: OVIRT-1851
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1851
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra</pre>
<p>Currently test failures and build failures are treated the same by the check queue – in both cases the change queue runs a bisection to find out the change that caused the failure.</p>
<p>It the case of a build failure – it is possible to know immediately which patch failed to build, so we can remove it immediately from the queue and avoid some expensive bisection runs.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1516275013-22664-382--
6 years, 5 months
[ OST Failure Report ] [ oVirt-Host ] [ 17-01-2018 ] [ 002_bootstrap.add_hosts ]
by Dafna Ron
Hi,
We have a failure in test 002_bootstrap.add_hosts from upgrade suite.
Can you please check the issue?
*Link and headline of suspected patches: Reported as failed:
https://gerrit.ovirt.org/#/c/86152/ <https://gerrit.ovirt.org/#/c/86152/> -
build: post 4.2.1-1*
*Reported as root cause: https://gerrit.ovirt.org/#/c/85421/
<https://gerrit.ovirt.org/#/c/85421/> - Require katello-agentLink to Job:*
*http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4908/
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4908/>Link
to all
logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4908/a...
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4908/artifact>(Relevant)
error snippet from the log: <error>nsaction commit.2018-01-17
00:08:41,743-05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [8f86c69] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing
Host lago-upgrade-from-release-suite-master-host0. Setting kernel
arguments.2018-01-17 00:08:41,977-05 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] Swallowing exception as
preferring stderr2018-01-17 00:08:41,977-05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [8f86c69]
Error during deploy dialog2018-01-17 00:08:41,978-05 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] SSH error running
command root@lago-upgrade-from-release-suite-master-host0:'umask 0077;
MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap
"chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" >
/dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x &&
"${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
DIALOG/customization=bool:True': RuntimeException: Unexpected error during
execution: bash: line 1: 1419 Segmentation fault
"${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
DIALOG/customization=bool:True2018-01-17 00:08:41,979-05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] Error during host
lago-upgrade-from-release-suite-master-host0 install2018-01-17
00:08:41,983-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] EVENT_ID:
VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during
installation of Host lago-upgrade-from-release-suite-master-host0:
Unexpected error during execution: bash: line 1: 1419 Segmentation
fault "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
DIALOG/customization=bool:True.2018-01-17 00:08:41,983-05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] Error during host
lago-upgrade-from-release-suite-master-host0 install, preferring first
exception: Unexpected connection termination2018-01-17 00:08:41,983-05
ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] Host installation
failed for host '76f737a5-fc15-4641-91c8-f5ef28b02436',
'lago-upgrade-from-release-suite-master-host0': Unexpected connection
termination2018-01-17 00:08:41,989-05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] START,
SetVdsStatusVDSCommand(HostName =
lago-upgrade-from-release-suite-master-host0,
SetVdsStatusVDSCommandParameters:{hostId='76f737a5-fc15-4641-91c8-f5ef28b02436',
status='InstallFailed', nonOperationalReason='NONE',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id:
47ad9c872018-01-17 00:08:41,995-05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] FINISH,
SetVdsStatusVDSCommand, log id: 47ad9c872018-01-17 00:08:42,003-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] EVENT_ID:
VDS_INSTALL_FAILED(505), Host lago-upgrade-from-release-suite-master-host0
installation failed. Unexpected connection termination.2018-01-17
00:08:42,014-05 INFO
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [8f86c69] Lock freed to object
'EngineLock:{exclusiveLocks='[76f737a5-fc15-4641-91c8-f5ef28b02436=VDS]',
sharedLocks=''}'</error>*
6 years, 5 months
ovirt-imageio is failing to build on fc27/fcraw
by Barak Korren
Hi Guys,
I'm sure you are aware that 'ovirt-imageio' is currently failing to
build on FC27 and Rawhide.
I'm not sure you get the implications tough.
The 1st thing that the release change-queue is checking, before
running OST, is if all builds for all patches it is checking are
building successfully for all platforms that the project has jobs for.
This means that essentially no new 'ovirt-imageio' packages are making
it into the tested and nightly repos for __any__ platform.
Furthermore, with the way the system works for now, there is no
special handling for build failures, with means they are treated like
OST failures, which means the system runs an expensive bisection
search to find the failing patch. So when your project fails to build,
it slows down checking for other project's patches.
I ask that you please do one of the following:
1. Fix the FC27 and RAWHIDE builds
2. Remove the FC27 and RAWHIDE build jobs
3. Turn the FC27 and RAWHIDE build jobs into check-merged jobs which
are not checked by the change-queue.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
6 years, 5 months
[JIRA] (OVIRT-1799) move project website to OpenShift v3
by Evgheni Dereveanchin (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1516270103-12367-245
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1799?page=com.atlassian.jir... ]
Evgheni Dereveanchin commented on OVIRT-1799:
---------------------------------------------
I want to share a strange experience with Online v3. I have a personal account and yesterday I received an email of the following content:
bq. Your access to OpenShift Online Starter was removed for account ***(a)gmail.com due to a prolonged period of inactivity.
My account was removed along with the pods that were running at the point. There was no prior notice and the app I was using on a daily basis is now gone. So we should be really careful when migrating as the free tier seems to be very unreliable and have unclear terms of service.
> move project website to OpenShift v3
> ------------------------------------
>
> Key: OVIRT-1799
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1799
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Hosting
> Reporter: Evgheni Dereveanchin
> Assignee: infra
>
> After moving the website off OpenShift v2 in OVIRT-1624 we can now start thinking about how to host it on v3. We have an internal instance ready but ideally we should host the actual site outside PHX.
> Opening this ticket to discuss the options
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100076)
------------=_1516270103-12367-245
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1799?page=com.atlassian.jir... ]</pre>
<h3>Evgheni Dereveanchin commented on OVIRT-1799:</h3>
<p>I want to share a strange experience with Online v3. I have a personal account and yesterday I received an email of the following content:</p>
<p>bq. Your access to OpenShift Online Starter was removed for account ***(a)gmail.com due to a prolonged period of inactivity.</p>
<p>My account was removed along with the pods that were running at the point. There was no prior notice and the app I was using on a daily basis is now gone. So we should be really careful when migrating as the free tier seems to be very unreliable and have unclear terms of service.</p>
<blockquote><h3>move project website to OpenShift v3</h3>
<pre> Key: OVIRT-1799
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1799
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Hosting
Reporter: Evgheni Dereveanchin
Assignee: infra</pre>
<p>After moving the website off OpenShift v2 in OVIRT-1624 we can now start thinking about how to host it on v3. We have an internal instance ready but ideally we should host the actual site outside PHX. Opening this ticket to discuss the options</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1516270103-12367-245--
6 years, 5 months
Subject: [ OST Failure Report ] [ oVirt Master ] [Jan 15th 2018 ] [ 004_basic_sanity.verify_glance_import ]
by Dafna Ron
Hi,
We had a failure in test : 004_basic_sanity.verify_glance_import
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/testRe...>
The issue is actually with engine loosing connection to host and assuming
there was a failure.
however, I could not find a failure in the vdsm which would be related to
this issue.
Please note that there is a NPE in the engine log for trying to update the
task status which I think is something that should be addressed.
*Link and headline of suspected patches: Patch repoted as the failed:
https://gerrit.ovirt.org/#/c/86198/2 <https://gerrit.ovirt.org/#/c/86198/2>*
Patch reported as root cause: https://gerrit.ovirt.org/#/c/84883/11
*Link to Job:*
*http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/>Link
to all
logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/a...
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4829/artifact/>(Relevant)
error snippet from the log: <error>2018-01-14 21:24:16,881-05 ERROR
[org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able
to update response for "6bae83f1-184c-475a-96e7-240e58ead94c"2018-01-14
21:25:34,824-05 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
(default task-6) [ae77e2a8-1473-487d-949b-e6f525dcb38f] Adding task
'388ef299-f83e-4af1-93a6-07781caf275f' (Parent Command
'AddImageFromScratch', Parameters Type
'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling
hasn't started yet..2018-01-14 21:25:34,866-05 INFO
[org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-6)
[ae77e2a8-1473-487d-949b-e6f525dcb38f] BaseAsyncTask::startPollingTask:
Starting to poll task '388ef299-f83e-4af1-93a6-07781caf275f'.2018-01-14
21:25:34,900-05 ERROR
[org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-6)
[ae77e2a8-1473-487d-949b-e6f525dcb38f] Command
'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' failed:
null2018-01-14 21:25:34,900-05 ERROR
[org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-6)
[ae77e2a8-1473-487d-949b-e6f525dcb38f] Exception:
java.lang.NullPointerException at
org.ovirt.engine.core.bll.VmCommand.executeCommand(VmCommand.java:163)
[bll.jar:] at
org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1140)
[bll.jar:] at
org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1282)
[bll.jar:] at
org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1931)
[bll.jar:] at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:164)
[utils.jar:] at
org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:103)
[utils.jar:] at
org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1342)
[bll.jar:] at
org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:407)
[bll.jar:] at
org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13)
[bll.jar:] at
org.ovirt.engine.core.bll.Backend.runAction(Backend.java:468)
[bll.jar:] at
org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:450)
[bll.jar:] at
org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:656)
[bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) [rt.jar:1.8.0_151] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_151] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.8.0_151] at
java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151]
at
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at
org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:78)
at
org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:88)
at
org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
[wildfly-ee-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:255)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:381)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:244)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
[weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at
org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
[wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422):</error>*
6 years, 5 months
[JIRA] (OVIRT-1850) rename he-basic to he-basic-noansible
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1516266206-23853-339
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1850?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1850:
----------------------------------
Please send the relevant patches to OST to rename the suite as you wish, as the suite maintainer.
As for [1], once [~gbenhaim(a)redhat.com] approves it there should be no issue merging it, worth also verifying with the manual job.
> rename he-basic to he-basic-noansible
> -------------------------------------
>
> Key: OVIRT-1850
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1850
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> Hi,
> Hosted-engine setup recently moved to using the ansible flow by default [2].
> I pushed [1] to make he-basic use the old flow, so that we keep testing it.
> Please merge [1], and rename 'he-basic' in the manual OST job to
> 'he-basic-noansible'. Thanks.
> [1] https://gerrit.ovirt.org/86398
> [2] https://gerrit.ovirt.org/83900
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100076)
------------=_1516266206-23853-339
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1850?page=com.atlassian.jir... ]</pre>
<h3>eyal edri commented on OVIRT-1850:</h3>
<p>Please send the relevant patches to OST to rename the suite as you wish, as the suite maintainer. As for [1], once [~gbenhaim(a)redhat.com] approves it there should be no issue merging it, worth also verifying with the manual job.</p>
<blockquote><h3>rename he-basic to he-basic-noansible</h3>
<pre> Key: OVIRT-1850
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1850
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi, Hosted-engine setup recently moved to using the ansible flow by default [2]. I pushed [1] to make he-basic use the old flow, so that we keep testing it. Please merge [1], and rename ‘he-basic’ in the manual OST job to ‘he-basic-noansible’. Thanks. [1] <a href="https://gerrit.ovirt.org/86398">https://gerrit.ovirt.org/86398</a> [2] <a href="https://gerrit.ovirt.org/83900">https://gerrit.ovirt.org/83900</a> — Didi</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1516266206-23853-339--
6 years, 5 months
[JIRA] (OVIRT-1850) rename he-basic to he-basic-noansible
by Yedidyah Bar David (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1516264295-14313-214
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Yedidyah Bar David created OVIRT-1850:
-----------------------------------------
Summary: rename he-basic to he-basic-noansible
Key: OVIRT-1850
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1850
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra
Hi,
Hosted-engine setup recently moved to using the ansible flow by default [2].
I pushed [1] to make he-basic use the old flow, so that we keep testing it.
Please merge [1], and rename 'he-basic' in the manual OST job to
'he-basic-noansible'. Thanks.
[1] https://gerrit.ovirt.org/86398
[2] https://gerrit.ovirt.org/83900
--
Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100076)
------------=_1516264295-14313-214
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Yedidyah Bar David created OVIRT-1850:</h3>
<pre> Summary: rename he-basic to he-basic-noansible
Key: OVIRT-1850
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1850
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi,</p>
<p>Hosted-engine setup recently moved to using the ansible flow by default [2].</p>
<p>I pushed [1] to make he-basic use the old flow, so that we keep testing it.</p>
<p>Please merge [1], and rename ‘he-basic’ in the manual OST job to ‘he-basic-noansible’. Thanks.</p>
<p>[1] <a href="https://gerrit.ovirt.org/86398">https://gerrit.ovirt.org/86398</a> [2] <a href="https://gerrit.ovirt.org/83900">https://gerrit.ovirt.org/83900</a> — Didi</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1516264295-14313-214--
6 years, 5 months
oVirt infra weekly meeting notes 17.01.2018
by Evgheni Dereveanchin
Hi everyone,
Please find the topics of this week's infra meeting below:
PHX DC:
- CVE patching ongoing, most services are already patched, few hosts and
VMs left
- BIOS patching breaks lago on newer machines - to be fixed by lago team
- Slave configuration being moved to global_setup OVIRT-1810
- Hardware refresh proposals for this year?
- Add switches as we’re out of port
- Would be great to have more bare metals
--
Regards,
Evgheni Dereveanchin
6 years, 5 months
