December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12914) Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final; clean out unneeded provisioning boilerplate

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12914: --------------------------------------- Summary: Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final; clean out unneeded provisioning boilerplate Key: WFLY-12914 URL: https://issues.redhat.com/browse/WFLY-12914 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Upgrade Galleon to match the versions used in core. The current versions should allow trimming quite a bit of boilerplate from all the places where we provision servers: Alexey Loubyansky 5:07 PM I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final Alexey Loubyansky 5:07 PM also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025 5:08 PM upgrading doesn't affect anything, except the bug fixes contained in those versions 5:10 PM however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL 5:11 PM the benefit would be to avoid the universe resolver in maven builds 5:11 PM and also a simplified (mojo) provisioning config Brian Stansberry 5:14 PM good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :) Alexey Loubyansky 5:16 PM by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97 5:16 PM the only reason it is there is to avoid resolution from the universe 5:17 PM with GAVs for dependencies, it won't be necessary anymore Brian Stansberry 5:17 PM what about <inheritConfigs>false</inheritConfigs> ? Alexey Loubyansky 5:18 PM that was there to workaround a bug which was fixed in 4.2.0.Final Brian Stansberry 5:18 PM how about 5:18 PM <included-packages> <name>docs.examples.configs</name> </included-packages> 5:19 PM assuming that's not in the top level f-p Alexey Loubyansky 5:19 PM that should definitely stay, it's not in the selected block 5:19 PM ah, then you can have that 5:20 PM then there would be a real reason to mention the transitive dependency 5:20 PM i.e. you want something from it Brian Stansberry 5:20 PM could it be declared in the top level block, even though the package is in the transitive dep? 5:20 PM i'm going off on tangents, but first i should have said... 5:21 PM Nice! Alexey Loubyansky 5:21 PM (EDITED) unless the package is installed by default, it has to be included explicitly using transitive element -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2426) JChannel: remove stats

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2426?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2426: -------------------------------- Consider using {{MsgStats}} in {{STATS}} if both prots maintain (more or less) the same values. > JChannel: remove stats > ---------------------- > > Key: JGRP-2426 > URL: https://issues.redhat.com/browse/JGRP-2426 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 5.0 > > > Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). > For ForkChannels, these stats would be gone, too, and would not be maintained for each fork channel separately... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2426) JChannel: remove stats

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/JGRP-2426?page=com.atlassian.jira.plugin... ] Dan Berindei commented on JGRP-2426: ------------------------------------ Perhaps {{STATS}} could be added above {{FORK}} when separate stats for each fork channel are needed. But {{STATS}} also needs to be changed to use {{LongAdder}}. > JChannel: remove stats > ---------------------- > > Key: JGRP-2426 > URL: https://issues.redhat.com/browse/JGRP-2426 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 5.0 > > > Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). > For ForkChannels, these stats would be gone, too, and would not be maintained for each fork channel separately... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2426) JChannel: remove stats

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2426?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2426: --------------------------- Description: Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). For ForkChannels, these stats would be gone, too, and would not be maintained for each fork channel separately... was:Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). > JChannel: remove stats > ---------------------- > > Key: JGRP-2426 > URL: https://issues.redhat.com/browse/JGRP-2426 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 5.0 > > > Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). > For ForkChannels, these stats would be gone, too, and would not be maintained for each fork channel separately... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2426) JChannel: remove stats

by Bela Ban (Jira)

Bela Ban created JGRP-2426: ------------------------------ Summary: JChannel: remove stats Key: JGRP-2426 URL: https://issues.redhat.com/browse/JGRP-2426 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Remove stats such as {{sent_msgs, received_msgs, sent_bytes, received_bytes}} from JChannel. It may be costly to maintain those stats (e.g. {{Message.getLength()}} in 5.0), and they're already maintained by the transport (or {{STATS}}). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1019) Review maistra installation job

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1019?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1019: --------------------------------- Sprint: Kiali Sprint #32 > Review maistra installation job > ------------------------------- > > Key: SWSQE-1019 > URL: https://issues.redhat.com/browse/SWSQE-1019 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to use correct deployment template based on version for both downstream and upstream builds. This is partially done by https://issues.jboss.org/browse/SWSQE-1017 > Also we might want to consider not using those templates at all for downstream builds and always use OLM. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1018) Molecule Tests don't run on Jenkins Slaves

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1018?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1018. ---------------------------------- Resolution: Done New jenkins slave for molecule tests is prepared > Molecule Tests don't run on Jenkins Slaves > ------------------------------------------ > > Key: SWSQE-1018 > URL: https://issues.redhat.com/browse/SWSQE-1018 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Attachments: olm.log > > > Running a simple > {code:bash} > molecule test -s olm-test > {code} > inside kiali/operator/ folder doesn't work on Jenkins slaves. > Before updating from Ansible 2.8 to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... > After updating to Ansible 2.9: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/test-molecule/1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1006) First attempt to remove ocp 4.2 cluster sometimes fails

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1006?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1006. ---------------------------------- Resolution: Done This is working in both OCP 4.2 and 4.3 > First attempt to remove ocp 4.2 cluster sometimes fails > ------------------------------------------------------- > > Key: SWSQE-1006 > URL: https://issues.redhat.com/browse/SWSQE-1006 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > level=debug msg="Exiting deleting openstack subnets" > level=debug msg="Deleting Floating IP: a11294c5-a827-4dea-b7c0-f64048176efa" > level=fatal msg="Resource not found" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-912) Improve clean evn job to always clean all controll planes

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-912?page=com.atlassian.jira.plugin... ] Filip Brychta reassigned SWSQE-912: ----------------------------------- Assignee: Filip Brychta > Improve clean evn job to always clean all controll planes > --------------------------------------------------------- > > Key: SWSQE-912 > URL: https://issues.redhat.com/browse/SWSQE-912 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When we have cluster with more control planes and then we start upstream pipeline with just one control plane the clean env job is stuck on deleting operator. We need to clean everything before installing new control plane. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-912) Improve clean evn job to always clean all controll planes

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-912?page=com.atlassian.jira.plugin... ] Filip Brychta resolved SWSQE-912. --------------------------------- Resolution: Done > Improve clean evn job to always clean all controll planes > --------------------------------------------------------- > > Key: SWSQE-912 > URL: https://issues.redhat.com/browse/SWSQE-912 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When we have cluster with more control planes and then we start upstream pipeline with just one control plane the clean env job is stuck on deleting operator. We need to clean everything before installing new control plane. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019