[JIRA] (OVIRT-1804) OST Networking suite -- missing logs
by eyal edri (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1513252555-26666-266
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1804?page=com.atlassian.jir... ]
eyal edri reassigned OVIRT-1804:
--------------------------------
Assignee: Gal Ben Haim (was: infra)
> OST Networking suite -- missing logs
> ------------------------------------
>
> Key: OVIRT-1804
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1804
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: OST
> Reporter: Leon Goldberg
> Assignee: Gal Ben Haim
>
> Hey guys,
> I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected.
> Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not.
> I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both.
> Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct.
> Another oddity is that I've seen the logs present in a couple of runs. So, for what it's worth, it doesn't fail at all times (but very much close to it).
> Thanks for any help!
> [1] https://gerrit.ovirt.org/#/c/85174/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
------------=_1513252555-26666-266
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1804?page=com.atlassian.jir... ]</pre>
<h3>eyal edri reassigned OVIRT-1804:</h3>
<pre>Assignee: Gal Ben Haim (was: infra)</pre>
<blockquote><h3>OST Networking suite — missing logs</h3>
<pre> Key: OVIRT-1804
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1804
Project: oVirt - virtualization made easy
Issue Type: Task
Components: OST
Reporter: Leon Goldberg
Assignee: Gal Ben Haim</pre>
<p>Hey guys, I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected. Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not. I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both. Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct. Another oddity is that I've seen the logs present in a couple of runs. So, for what it's worth, it doesn't fail at all times (but very much close to it). Thanks for any help! [1] <a href="https://gerrit.ovirt.org/#/c/85174/">https://gerrit.ovirt.org/#/c/85174/</a></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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>
------------=_1513252555-26666-266--
7 years
[JIRA] (OVIRT-1804) OST Networking suite -- missing logs
by Leon Goldberg (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1513252097-16012-269
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Leon Goldberg created OVIRT-1804:
------------------------------------
Summary: OST Networking suite -- missing logs
Key: OVIRT-1804
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1804
Project: oVirt - virtualization made easy
Issue Type: Task
Components: OST
Reporter: Leon Goldberg
Assignee: infra
Hey guys,
I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected.
Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not.
I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both.
Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct.
Another oddity is that I've seen the logs present in a couple of runs. So, for what it's worth, it doesn't fail at all times (but very much close to it).
Thanks for any help!
[1] https://gerrit.ovirt.org/#/c/85174/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
------------=_1513252097-16012-269
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Leon Goldberg created OVIRT-1804:</h3>
<pre> Summary: OST Networking suite -- missing logs
Key: OVIRT-1804
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1804
Project: oVirt - virtualization made easy
Issue Type: Task
Components: OST
Reporter: Leon Goldberg
Assignee: infra</pre>
<p>Hey guys,</p>
<p>I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected.</p>
<p>Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not.</p>
<p>I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both.</p>
<p>Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct.</p>
<p>Another oddity is that I've seen the logs present in a couple of runs. So, for what it's worth, it doesn't fail at all times (but very much close to it).</p>
<p>Thanks for any help!</p>
<p>[1] <a href="https://gerrit.ovirt.org/#/c/85174/">https://gerrit.ovirt.org/#/c/85174/</a></p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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>
------------=_1513252097-16012-269--
7 years
[JIRA] (OVIRT-1804) OST Networking suite -- missing logs
by Leon Goldberg (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1804?page=com.atlassian.jir... ]
Leon Goldberg updated OVIRT-1804:
---------------------------------
Epic Link: OVIRT-400
> OST Networking suite -- missing logs
> ------------------------------------
>
> Key: OVIRT-1804
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1804
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: OST
> Reporter: Leon Goldberg
> Assignee: infra
>
> Hey guys,
> I have a weird problem with our new OST suite. Although I copy certain directories to ../ovirt-system-tests/exported-artifacts (i.e. root dir/exported-artifacts), they are not being collected.
> Running the suite via mock, I can see that the directory is present with the logs (plus some other files/directories), however in CI they are not.
> I've tried running both run_suite.sh and check-patch.sh. Locally I see the artifacts in both.
> Here's the patch [1]. It's unfinished work. I am familiar with lago's abstraction, and although is super ugly, the relative path in _collect_artifacts seems correct.
> Another oddity is that I've seen the logs present in a couple of runs. So, for what it's worth, it doesn't fail at all times (but very much close to it).
> Thanks for any help!
> [1] https://gerrit.ovirt.org/#/c/85174/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
7 years
[JIRA] (OVIRT-1803) Please deploy manageiq on phoenix datacenter
by sbonazzo (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1513243296-15267-322
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1803?page=com.atlassian.jir... ]
sbonazzo reassigned OVIRT-1803:
-------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> Please deploy manageiq on phoenix datacenter
> --------------------------------------------
>
> Key: OVIRT-1803
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1803
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: General
> Reporter: sbonazzo
> Assignee: Evgheni Dereveanchin
>
> We have now an oVirt and an OpenShift instance running on PHX, let's install ManageIQ too for managing both.
> Please deploy ManageIQ on top of oVirt :-)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
------------=_1513243296-15267-322
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1803?page=com.atlassian.jir... ]</pre>
<h3>sbonazzo reassigned OVIRT-1803:</h3>
<pre>Assignee: Evgheni Dereveanchin (was: infra)</pre>
<blockquote><h3>Please deploy manageiq on phoenix datacenter</h3>
<pre> Key: OVIRT-1803
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1803
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: General
Reporter: sbonazzo
Assignee: Evgheni Dereveanchin</pre>
<p>We have now an oVirt and an OpenShift instance running on PHX, let's install ManageIQ too for managing both. Please deploy ManageIQ on top of oVirt <span class="smiley-happy">:-)</span></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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>
------------=_1513243296-15267-322--
7 years
[JIRA] (OVIRT-1803) Please deploy manageiq on phoenix datacenter
by sbonazzo (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1513243276-23902-225
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1803?page=com.atlassian.jir... ]
sbonazzo updated OVIRT-1803:
----------------------------
Epic Link: OVIRT-403
> Please deploy manageiq on phoenix datacenter
> --------------------------------------------
>
> Key: OVIRT-1803
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1803
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: General
> Reporter: sbonazzo
> Assignee: infra
>
> We have now an oVirt and an OpenShift instance running on PHX, let's install ManageIQ too for managing both.
> Please deploy ManageIQ on top of oVirt :-)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
------------=_1513243276-23902-225
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1803?page=com.atlassian.jir... ]</pre>
<h3>sbonazzo updated OVIRT-1803:</h3>
<pre>Epic Link: OVIRT-403</pre>
<blockquote><h3>Please deploy manageiq on phoenix datacenter</h3>
<pre> Key: OVIRT-1803
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1803
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: General
Reporter: sbonazzo
Assignee: infra</pre>
<p>We have now an oVirt and an OpenShift instance running on PHX, let's install ManageIQ too for managing both. Please deploy ManageIQ on top of oVirt <span class="smiley-happy">:-)</span></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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>
------------=_1513243276-23902-225--
7 years
[JIRA] (OVIRT-1803) Please deploy manageiq on phoenix datacenter
by sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-1803:
-------------------------------
Summary: Please deploy manageiq on phoenix datacenter
Key: OVIRT-1803
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1803
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: General
Reporter: sbonazzo
Assignee: infra
We have now an oVirt and an OpenShift instance running on PHX, let's install ManageIQ too for managing both.
Please deploy ManageIQ on top of oVirt :-)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100074)
7 years
engine-phx.ovirt.org upgraded to 4.2.0 RC
by Evgheni Dereveanchin
Hi everyone,
I wanted to share the good news: our main oVirt instance in PHX is now
running the latest 4.2.0 release candidate. This is a Hosted Engine setup
that went through lots of updates and hosts most of the services for the
project such as the entire CI setup, package repositories, mailing lists
and lots of other stuff across hundreds of VMs and a dozen of hosts.
During this upgrade we've tested multiple components since our setup uses
many of the customization options offered by oVirt: unusual network
configurations, resource quotas, local and shared storage domains and even
uncommon hardware architectures such as POWER8.
We faced some problems with Hosted Engine during the upgrade since our
environment was deployed way back as 3.4 and HE changed a lot since. Short
upgrade guidance:
1) no HE -> just upgrade and enjoy
2) HE on a system that was initially deployed as 4.0 or 4.1 -> upgrade HE
hosts, then - the engine
3) HE on a system that was initially deployed before 4.0 -> check out [1]
to confirm if HE configs are OK, then upgrade HE hosts, then - the engine
I've reported several bugs during the course of this upgrade and most of
them are fixed by now. Hopefully this effort will make your upgrades go
smoothly. If you hit any issues with 4.2 - please file bugs as well or
start a discussion on the list.
--
Regards,
Evgheni Dereveanchin
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1521011
7 years
