[JBoss JIRA] (WFLY-12543) Subsystem metrics are missing from microprofile-metrics JSON output
by Richard DiCroce (Jira)
[ https://issues.jboss.org/browse/WFLY-12543?page=com.atlassian.jira.plugin... ]
Richard DiCroce commented on WFLY-12543:
----------------------------------------
This is now working in the latest nightly (665). Probably fixed by WFLY-12311.
> Subsystem metrics are missing from microprofile-metrics JSON output
> -------------------------------------------------------------------
>
> Key: WFLY-12543
> URL: https://issues.jboss.org/browse/WFLY-12543
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 17.0.1.Final, 18.0.0.Beta1
> Reporter: Richard DiCroce
> Assignee: Jeff Mesnil
> Priority: Major
>
> Calling /metrics with Accept = application/json results in much fewer metrics being returned than when it is called without Accept (and thus returns data in the OpenMetrics format). Specifically, all the subsystem metrics (anything affected by the prefix configured in the microprofile-metrics subsystem) are missing.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-4671) Upgrade Elytron from 1.10.1.Final to 1.10.2.Final
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4671?page=com.atlassian.jira.plugi... ]
James Perkins moved JBEAP-17592 to WFCORE-4671:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4671 (was: JBEAP-17592)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security Manager)
Target Release: (was: 7.backlog.GA)
> Upgrade Elytron from 1.10.1.Final to 1.10.2.Final
> -------------------------------------------------
>
> Key: WFCORE-4671
> URL: https://issues.jboss.org/browse/WFCORE-4671
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Security
> Reporter: James Perkins
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> Upgrade Elytron from 1.10.1.Final to 1.10.2.Final.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (SWSQE-838) Investigate how we could use git-crypt
by praneeth bajjuri (Jira)
[ https://issues.jboss.org/browse/SWSQE-838?page=com.atlassian.jira.plugin.... ]
praneeth bajjuri commented on SWSQE-838:
----------------------------------------
I went to through git crypt, using git crypt we can store our secret information in a file by encrypting it and we push this file into git when we want that information we can decrypt using bash script then we can use all the data in groovy Jenkins files.
for reference see the link : https://www.chrissearle.org/2019/02/23/using-git-crypt/
> Investigate how we could use git-crypt
> --------------------------------------
>
> Key: SWSQE-838
> URL: https://issues.jboss.org/browse/SWSQE-838
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Prachi Yadav
> Priority: Minor
> Labels: infrastructure
>
> Do we want to use git-crypt to store credentials?
> Problem is how to safely share credentials among team members, how to use them in jenkins jobs and automation, etc.
> # check how other teams are doing it
> # suggest improvements for kiali team
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFCORE-4631) Create tests for Elytron syslog reconnect attempts
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4631?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4631:
---------------------------------------
I'm going to handle this differently than I had originally planned. There are tests in Elytron already that test this functionality. I'll be removing the unit tests as there is not a good way to ensure logging happens in a unit test that I'm aware of.
If in the future we do think there should be testing on WildFly Core, these likely should be integration tests. We'd need a way to ensure some audit logs are being invoked and then test would need to determine if the messages have NOT been logged. These types of tests are not by favorite as it's a negative assumption with a syslog server in the mix.
> Create tests for Elytron syslog reconnect attempts
> --------------------------------------------------
>
> Key: WFCORE-4631
> URL: https://issues.jboss.org/browse/WFCORE-4631
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> WFCORE-4394 currently has some tests which will be disabled for this. It's likely some integration tests will need to be done instead of unit tests. ELY-1864 is going to change the way the reconnect attempts are done resulting in the current unit tests failing.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12522) Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12522?page=com.atlassian.jira.plugin... ]
James Perkins resolved WFLY-12522.
----------------------------------
Resolution: Done
> Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12522
> URL: https://issues.jboss.org/browse/WFLY-12522
> Project: WildFly
> Issue Type: Bug
> Components: CLI, Remoting, Web (Undertow)
> Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final
> Reporter: super 6349
> Assignee: Flavia Rainone
> Priority: Blocker
> Fix For: 18.0.0.Final
>
>
> When the user executes jboss-cli commands on a fresh installation of wildfly, RemoteConnectionHandler objects are created but never released.
> We identified this problem when we configured a readiness probe on openshift using jboss-cli (repeating every 15 seconds) and the memory started to increase along the days. The application was in development and nobody was accessing it, but the memory increased nonetheless.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months