[ OST Failure Report ] [ oVirt Master (ovirt-hosted-engine-setup) ] [ 26-02-2018 ] [ 007_sd_reattach.deactivate_storage_domain ]
by Dafna Ron
Hi,
We had a failure for 007_sd_reattach.deactivate_storage_domain because of
running tasks on the storage domain.
we have an open bug for this re-coring race on ost:
https://bugzilla.redhat.com/show_bug.cgi?id=1538228
Please note the change reported does not seem to be related to the failure
and I have re-triggered it.
*Link and headline of suspected patches: Patch is not relatedLink to
Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866>Link to
all
logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866/a...
<http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866/artifacts>(Relevant)
error snippet from the log: <error>2018-02-26 07:03:39,691-05 DEBUG
[org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall]
(default task-9) [bebde602-3277-4ec4-be4f-7d60969080ec] SqlCall for
procedure [GetAsyncTasksByEntityId] compiled2018-02-26 07:03:39,692-05
WARN
[org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand]
(default task-9) [bebde602-3277-4ec4-be4f-7d60969080ec] There are running
tasks: 'AsyncTask:{commandId='c455f212-4cb1-46e8-a2b5-61816c7e8b79',
rootCommandId='c455f212-4cb1-46e8-a2b5-61816c7e8b79',
storagePoolId='c0a3f481-4598-4b0a-aabc-4acc67cd45b5',
taskId='5b342d74-4726-4430-924a-2fb9d1ab9201',
vdsmTaskId='477aee46-f8d7-4676-bf33-3035e61e5ca9', stepId='null',
taskType='downloadImageFromStream',
status='running'}AsyncTask:{commandId='d2128202-bb95-4c29-80df-c5a822aad457',
rootCommandId='d2128202-bb95-4c29-80df-c5a822aad457',
storagePoolId='c0a3f481-4598-4b0a-aabc-4acc67cd45b5',
taskId='fe3a6031-ebce-463c-bba7-5c78ddda0f18',
vdsmTaskId='6ef057d6-6034-477b-ae01-bb87beb68584', stepId='null',
taskType='downloadImageFromStream', status='running'}'2018-02-26
07:03:39,692-05 WARN
[org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand]
(default task-9) [bebde602-3277-4ec4-be4f-7d60969080ec] Validation of
action 'DeactivateStorageDomainWithOvfUpdate' failed for user
admin@internal-authz. Reasons:
VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__DEACTIVATE,ERROR_CANNOT_DEACTIVATE_DOMAIN_WITH_TASKS2018-02-26
07:03:39,693-05 INFO
[org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand]
(default task-9) [bebde602-3277-4ec4-be4f-7d60969080ec] Lock freed to
object
'EngineLock:{exclusiveLocks='[167d2b72-445d-424c-ac1e-f3c8d6e8aeca=STORAGE]',
sharedLocks='[c0a3f481-4598-4b0a-aabc-4acc67cd45b5=POOL]'}'2018-02-26
07:03:39,693-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-9) [bebde602-3277-4ec4-be4f-7d60969080ec] method: runAction,
params: [DeactivateStorageDomainWithOvfUpdate,
DeactivateStorageDomainWithOvfUpdateParameters:{commandId='f64e5c4b-51b3-4b90-97d6-b6b2544d9874',
user='null', commandType='Unknown'}], timeElapsed: 63ms2018-02-26
07:03:39,698-05 ERROR
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
task-9) [] Operation Failed: [Cannot deactivate Storage while there are
running tasks on this Storage.-Please wait until tasks will finish and try
again.]2018-02-26 07:03:40,659-05 DEBUG
[org.ovirt.engine.core.utils.timer.FixedDelayJobListener]
(DefaultQuartzScheduler6) [] Rescheduling
DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterServiceSyncJob.refreshGlusterServices#-9223372036854775801
as there is no unfired trigger.2018-02-26 07:03:40,660-05 DEBUG
[org.ovirt.engine.core.utils.timer.FixedDelayJobListener]
(DefaultQuartzScheduler1) [] Rescheduling
DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795
as there is no unfired trigger.2018-02-26 07:03:40,764-05 INFO
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
(EE-ManagedThreadFactory-engineScheduled-Thread-81) [] Polling and updating
Async Tasks: 6 tasks, 4 tasks to poll now2018-02-26 07:03:40,767-05 DEBUG
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksStatusesVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-81) [] START,
SPMGetAllTasksStatusesVDSCommand(
IrsBaseVDSCommandParameters:{storagePoolId='c0a3f481-4598-4b0a-aabc-4acc67cd45b5',
ignoreFailoverLimit='false'}), log id: 226c225f</error>*
6 years, 9 months
Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1236
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1236/dis...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision c8d6af9a9106cbde3fd8cda1b8ed27dda3020def (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f c8d6af9a9106cbde3fd8cda1b8ed27dda3020def
Commit message: "Fix issue with Lago CI jobs"
> git rev-list --no-walk c8d6af9a9106cbde3fd8cda1b8ed27dda3020def # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins2846270470932699215.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1474, in _commonLoadRepoXML
if self._latestRepoXML(local):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML
repomd = self.metalink_data.repomd
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda>
metalink_data = property(fget=lambda self: self._getMetalink(),
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 906, in _getMetalink
shutil.move(result, self.metalink_filename)
File "/usr/lib64/python2.7/shutil.py", line 301, in move
copy2(src, real_dst)
File "/usr/lib64/python2.7/shutil.py", line 130, in copy2
copyfile(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml.tmp'
Build step 'Execute shell' marked build as failure
6 years, 9 months
[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1519575544-10808-170
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jir... ]
eyal edri reassigned OVIRT-1871:
--------------------------------
Assignee: Anton Marchukov (was: infra)
> Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
> ----------------------------------------------------------------------
>
> Key: OVIRT-1871
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Gerrit/git
> Reporter: sbonazzo
> Assignee: Anton Marchukov
>
> I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get:
> Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) https://gerrit.ovirt.org/#/c/86992/
> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that.
> When fixing this, please also include link to how to do that, I've other projects that will need similar change.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
------------=_1519575544-10808-170
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jir... ]</pre>
<h3>eyal edri reassigned OVIRT-1871:</h3>
<pre>Assignee: Anton Marchukov (was: infra)</pre>
<blockquote><h3>Wrong target milestone check on new 4.2 branches for ovirt-host-deploy</h3>
<pre> Key: OVIRT-1871
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Gerrit/git
Reporter: sbonazzo
Assignee: Anton Marchukov</pre>
<p>I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) <a href="https://gerrit.ovirt.org/#/c/86992/">https://gerrit.ovirt.org/#/c/86992/</a> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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>
------------=_1519575544-10808-170--
6 years, 9 months
[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1519573284-30715-140
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jir... ]
eyal edri reassigned OVIRT-1911:
--------------------------------
Assignee: Anton Marchukov (was: infra)
Anton, how much effort do you think this will need to add it to Gerrit Hooks?
[~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason.
We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start "spamming" the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches.
What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then?
We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward.
cc [~dfodor]
> RFE: Add relevant git commit messages as comments in the relevant Bugzillas
> ---------------------------------------------------------------------------
>
> Key: OVIRT-1911
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Gerrit/git
> Reporter: Yaniv Kaul
> Assignee: Anton Marchukov
>
> When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug?
> I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
------------=_1519573284-30715-140
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jir... ]</pre>
<h3>eyal edri reassigned OVIRT-1911:</h3>
<pre>Assignee: Anton Marchukov (was: infra)</pre>
<p>Anton, how much effort do you think this will need to add it to Gerrit Hooks?</p>
<p>[~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason.</p>
<p>We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start “spamming” the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches.</p>
<p>What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then?</p>
<p>We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward.</p>
<p>cc [~dfodor]</p>
<blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3>
<pre> Key: OVIRT-1911
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git
Reporter: Yaniv Kaul
Assignee: Anton Marchukov</pre>
<p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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>
------------=_1519573284-30715-140--
6 years, 9 months
[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1519571950-30813-109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Yaniv Kaul created OVIRT-1911:
---------------------------------
Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas
Key: OVIRT-1911
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git
Reporter: Yaniv Kaul
Assignee: infra
When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug?
I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
------------=_1519571950-30813-109
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Yaniv Kaul created OVIRT-1911:</h3>
<pre> Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas
Key: OVIRT-1911
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git
Reporter: Yaniv Kaul
Assignee: infra</pre>
<p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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>
------------=_1519571950-30813-109--
6 years, 9 months
[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1519571950-26090-115
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jir... ]
Yaniv Kaul updated OVIRT-1911:
------------------------------
Epic Link: OVIRT-411
> RFE: Add relevant git commit messages as comments in the relevant Bugzillas
> ---------------------------------------------------------------------------
>
> Key: OVIRT-1911
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Gerrit/git
> Reporter: Yaniv Kaul
> Assignee: infra
>
> When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug?
> I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
------------=_1519571950-26090-115
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jir... ]</pre>
<h3>Yaniv Kaul updated OVIRT-1911:</h3>
<pre>Epic Link: OVIRT-411</pre>
<blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3>
<pre> Key: OVIRT-1911
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Gerrit/git
Reporter: Yaniv Kaul
Assignee: infra</pre>
<p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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>
------------=_1519571950-26090-115--
6 years, 9 months
[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1910:
--------------------------------
Epic Link: OVIRT-400
> Strange Lago CI test failure
> ----------------------------
>
> Key: OVIRT-1910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Standard CI (Freestyle)
> Reporter: Yaniv Kaul
> Assignee: infra
>
> My patch[1] is failing, but I'm not sure why.
> See [2] for the job - the issues seems to be with the pusher - see its
> log[3]:
> 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1
> --pretty=format:%H'
> 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0
> 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ----
> 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ----
> 2018-02-23 12:42:16,230:DEBUG:__main__:
> c26adc01449d97899aac18406298374de0e7dd73
> 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git
> rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}'
> 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128
> 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ----
> 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument
> 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}':
> unknown revision or path not in the working tree.
> Any ideas?
> TIA,
> Y.
> [1] https://github.com/lago-project/lago/pull/695
> [2]
> http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/
> [3]
> http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/71...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
6 years, 9 months
[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1519559357-18891-124
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1910:
-----------------------------------
Assignee: Barak Korren (was: infra)
Component/s: Standard CI (Freestyle)
Epic Link: OVIRT-400
Issue Type: Bug (was: By-EMAIL)
Priority: Highest (was: Medium)
> Strange Lago CI test failure
> ----------------------------
>
> Key: OVIRT-1910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Standard CI (Freestyle)
> Reporter: Yaniv Kaul
> Assignee: Barak Korren
> Priority: Highest
>
> My patch[1] is failing, but I'm not sure why.
> See [2] for the job - the issues seems to be with the pusher - see its
> log[3]:
> 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1
> --pretty=format:%H'
> 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0
> 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ----
> 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ----
> 2018-02-23 12:42:16,230:DEBUG:__main__:
> c26adc01449d97899aac18406298374de0e7dd73
> 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git
> rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}'
> 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128
> 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ----
> 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument
> 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}':
> unknown revision or path not in the working tree.
> Any ideas?
> TIA,
> Y.
> [1] https://github.com/lago-project/lago/pull/695
> [2]
> http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/
> [3]
> http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/71...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
------------=_1519559357-18891-124
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren reassigned OVIRT-1910:</h3>
<pre> Assignee: Barak Korren (was: infra)
Component/s: Standard CI (Freestyle)
Epic Link: OVIRT-400
Issue Type: Bug (was: By-EMAIL)
Priority: Highest (was: Medium)</pre>
<blockquote><h3>Strange Lago CI test failure</h3>
<pre> Key: OVIRT-1910
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Standard CI (Freestyle)
Reporter: Yaniv Kaul
Assignee: Barak Korren
Priority: Highest</pre>
<p>My patch[1] is failing, but I'm not sure why. See [2] for the job – the issues seems to be with the pusher – see its log[3]: 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: ‘git log -1 --pretty=format:%H’ 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- 2018-02-23 12:42:16,230:DEBUG:__main__: c26adc01449d97899aac18406298374de0e7dd73 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: ‘git rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’ 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument ‘jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’: unknown revision or path not in the working tree. Any ideas? TIA, Y. [1] <a href="https://github.com/lago-project/lago/pull/695">https://github.com/lago-project/lago/pull/695</a> [2] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/</a> [3] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/71...">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/71...</a></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</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>
------------=_1519559357-18891-124--
6 years, 9 months
