[JIRA] (OVIRT-2311) ovirt-master vdsm failure - extend disk test
times out
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2311?page=com.atlassian.jir... ]
Dafna Ron reassigned OVIRT-2311:
--------------------------------
Assignee: danken (was: infra)
> ovirt-master vdsm failure - extend disk test times out
> -------------------------------------------------------
>
> Key: OVIRT-2311
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2311
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: danken
> Labels: ost_failures
>
> There is no failure of a test but we can see a gap of an hour from start of extend_disk1 until unhanded exception is thrown.
> Although the error is reported on 004_basic_sanity the logs stop on post-003_basic_networking.py.
> looking at the available logs it may be a task that is not cleared.
> I do not see a connection between the patch and the timeout unless something in the tests is looking ERROR: InterpreterNotFound: python3.6 errors in order to exit.
> patch that failed: https://gerrit.ovirt.org/#/c/92847/
> job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8648/
> Error I can see in the logs is:
> 2018-07-12 01:23:14,863-04 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-1) [] An error occurred while fetching unregistered disks from Storage Domain id '597bfe1f-d88c-4961-b1dc-f6c771af9
> fff'
> but I can't see an error in vdsm that would suggest we had a failure.
> you can see the gap in the job:
> 05:31:45 [basic-suit] # extend_disk1:
> 06:31:56 [basic-suit] * Unhandled exception in <function <lambda> at 0x7f5dd403c5f0>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months
[JIRA] (OVIRT-2344) Re-engineer the oVirt resources server
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-2344:
-----------------------------------
Summary: Re-engineer the oVirt resources server
Key: OVIRT-2344
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2344
Project: oVirt - virtualization made easy
Issue Type: Epic
Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra
resources.ovirt.org is one of the most important servers in our infrastructure, but its current configuration is quite fragile and prone to fialure.
This EPIC is eant to consolidate and track work we do to make resources.ovirt.org more reliable, and maintainable.
Among the things we can try to do:
# Have multiple redundant front-ends serving package content to users
# Separate test and production package serving
# Separate package serving and backed repository building
# Host resources on 3rd party infrastructure.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months
[JIRA] (OVIRT-2343) Make STDCI reporting UI configurable fir GitHub
jobs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2343?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-2343:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Make STDCI reporting UI configurable fir GitHub jobs
> ----------------------------------------------------
>
> Key: OVIRT-2343
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2343
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Standard CI (Pipelines), STDCI Build Report, STDCI DSL
> Reporter: Barak Korren
> Assignee: Barak Korren
> Priority: High
>
> Make it so developers in GitHub projects can select the UI the see build results in from the STDCI DSL.
> h3. Acceptance Criteria
> # The is a "reporting" option in the STDCI DSL
> # The reporting option is a dictionary for which we now support only the "style" key
> # The style key can have one of 3 values - "classic", "blue ocean" or "stdci" mapping to appropriate UIs.
> # The default value for the style key is "default" which keeps existing behaviour.
> # Setting the reporting style makes "details" links from GitHub point to the the selected UI.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months
[JIRA] (OVIRT-2343) Make STDCI reporting UI configurable fir GitHub
jobs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2343?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2343:
--------------------------------
Epic Link: OVIRT-2339
> Make STDCI reporting UI configurable fir GitHub jobs
> ----------------------------------------------------
>
> Key: OVIRT-2343
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2343
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Standard CI (Pipelines), STDCI Build Report, STDCI DSL
> Reporter: Barak Korren
> Assignee: infra
> Priority: High
>
> Make it so developers in GitHub projects can select the UI the see build results in from the STDCI DSL.
> h3. Acceptance Criteria
> # The is a "reporting" option in the STDCI DSL
> # The reporting option is a dictionary for which we now support only the "style" key
> # The style key can have one of 3 values - "classic", "blue ocean" or "stdci" mapping to appropriate UIs.
> # The default value for the style key is "default" which keeps existing behaviour.
> # Setting the reporting style makes "details" links from GitHub point to the the selected UI.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months