[jira] [Updated] (AMBARI-24408) Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues
[ https://issues.apache.org/jira/browse/AMBARI-24408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24408: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues > > > Key: AMBARI-24408 > URL: https://issues.apache.org/jira/browse/AMBARI-24408 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: cleanup, pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > > Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues. > See https://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00123.html for > reported issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24187:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Ask users to select ldap type ( AD, IPA, generic ldap) and provide inteligent
> defaults based on their choice:
> Active Directory
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (ou=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (ou=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
> IPA (very similar to generic ldap, but needs explicit search customization
> into cn=accounts (or cn=compat) else it returns 2 search results which tends
> to cause problems)
> {code:java}
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ipa.ambari.apache.org):
> Primary LDAP Port (636):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (true):
> Do you want to provide custom TrustStore for Ambari [y/n] (y)?
> TrustStore type [jks/jceks/pkcs12] (jks):
> Path to TrustStore file (/etc/pki/java/cacerts):
> Password for TrustStore (changeit):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,cn=accounts,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
> Generic LDAP (defaults here need validation, i'm not as familiar with this
> one)
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ldap.ambari.apache.org):
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> Do you want to provide custom TrustStore for Ambari [y/n] (n)?
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24335) Update service metainfo to declare Kerberos is required for SSO integration support
[
https://issues.apache.org/jira/browse/AMBARI-24335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24335.
---
Resolution: Fixed
> Update service metainfo to declare Kerberos is required for SSO integration
> support
> ---
>
> Key: AMBARI-24335
> URL: https://issues.apache.org/jira/browse/AMBARI-24335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Update service metainfo to declare Kerberos is required for SSO integration
> support.
> The metainfo file allow for a service to indicate that is supports SSO
> integration.
> {code:java|title=Example}
>
> true
>
> service-site/knox.sso.enabled
>
> {code}
> However, some services required that Kerberos is enabled to support SSO. This
> needs to be indicated in the metainfo so that Ambari knows how to behave
> properly.
> {code:java|title=Example}
>
> true
>
> service-site/knox.sso.enabled
> true
>
> {code}
> Along with this change, the following API request needs to be updated to
> supply the relevant data:
> {noformat:title=Get stack service details}
> GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
> {
> "href" : ":URL",
> "StackServices" : {
> ...
> "sso_integration_supported": "true",
> "sso_integration_requires_kerberos": "true",
> ...
> },
> ...
> {noformat}
> {noformat:title=Get installed service information}
> GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
> {
> "href" : ":URL",
> "ServiceInfo" : {
> "cluster_name" : ":CLUSTER_NAME",
> ...
> "sso_integration_supported": "true",
> "sso_integration_requires_kerberos": "true",
> "sso_integration_enabled": "false",
> "sso_integration_desired": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=List installed services that support SSO integration only
> when Kerberos to be enabled}
> GET
> /api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true&ServiceInfo/sso_integration_requires_kerberos=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
> {noformat:title=List stack services that support SSO integration only when
> Kerberos is enabed}
> GET
> /api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/sso_integration_supported=true&StackServices/sso_integration_requires_kerberos=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24319) Multiple alerts after HDFS service only regenerate keytabs, as keytabs are out of sync
[ https://issues.apache.org/jira/browse/AMBARI-24319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24319: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Multiple alerts after HDFS service only regenerate keytabs, as keytabs are > out of sync > -- > > Key: AMBARI-24319 > URL: https://issues.apache.org/jira/browse/AMBARI-24319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Robert Levas >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > *STR* > # Install Ambari 2.7.0 > # Deploy a cluster with some services > # Execute to HDFS / Actions / Regenerate Keytabs > # Restart all required components > *Result* > Multiple alerts have been shown saying they receive 403 when trying to > connect to different web UIs > *Expected result* > No alerts; everything should work as expected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24451) ambari.ldap.advanced.group_mapping_rules does not work, LDAP sync does not add admin roles for configured group(s)
[ https://issues.apache.org/jira/browse/AMBARI-24451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24451: -- Resolution: Fixed Status: Resolved (was: Patch Available) > ambari.ldap.advanced.group_mapping_rules does not work, LDAP sync does not > add admin roles for configured group(s) > -- > > Key: AMBARI-24451 > URL: https://issues.apache.org/jira/browse/AMBARI-24451 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > If I configure ambari.ldap.advanced.group_mapping_rules, it does not add > ambari admin roles to the configured role. I did some debug and the > AmbariLdapConfiguration is uninitialized in Users.java class, so the > adminGroupMappings value is the default "Ambari Administrators" not the one I > configured before. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24495) ambari-server setup fails with postgresql >= 9.3
[ https://issues.apache.org/jira/browse/AMBARI-24495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24495: -- Resolution: Fixed Status: Resolved (was: Patch Available) > ambari-server setup fails with postgresql >= 9.3 > - > > Key: AMBARI-24495 > URL: https://issues.apache.org/jira/browse/AMBARI-24495 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24495.patch > > Time Spent: 1h > Remaining Estimate: 0h > > ambari-server setup with default postgres has been failing with > > > OSError: [Errno 2] No such file or directory: '/usr/bin/postgresql-setup' > > Looks like postgres packages/dependencies are not installed along with > installing ambari server install. > below is output from ambari-server install from ambari-2.7.1 cluster > > > 2018-08-07 > 11:17:56,106|executor.py.167|INFO|14260|MainThread|172.27.25.203|executing > the command='yum -y install ambari-server' > 2018-08-07 11:17:56,432|executor.py.167|INFO|14260|Thread-191|stdout: > Loaded plugins: ovl, priorities > 2018-08-07 11:17:57,971|executor.py.167|INFO|14260|Thread-191|stdout: > 12711 packages excluded due to repository priority protections > 2018-08-07 11:17:58,754|executor.py.167|INFO|14260|Thread-191|stdout: > Resolving Dependencies > 2018-08-07 11:17:58,754|executor.py.167|INFO|14260|Thread-191|stdout: --> > Running transaction check > 2018-08-07 11:17:58,755|executor.py.167|INFO|14260|Thread-191|stdout: > ---> Package ambari-server.x86_64 0:2.7.1.0-63 will be installed > 2018-08-07 11:17:58,974|executor.py.167|INFO|14260|Thread-191|stdout: --> > Finished Dependency Resolution > 2018-08-07 11:17:59,146|executor.py.167|INFO|14260|Thread-191|stdout: > 2018-08-07 11:17:59,146|executor.py.167|INFO|14260|Thread-191|stdout: > Dependencies Resolved > 2018-08-07 11:17:59,147|executor.py.167|INFO|14260|Thread-191|stdout: > 2018-08-07 11:17:59,147|executor.py.167|INFO|14260|Thread-191|stdout: > > 2018-08-07 11:17:59,147|executor.py.167|INFO|14260|Thread-191|stdout: > PackageArchVersionRepository Size > 2018-08-07 11:17:59,147|executor.py.167|INFO|14260|Thread-191|stdout: > > 2018-08-07 11:17:59,147|executor.py.167|INFO|14260|Thread-191|stdout: > Installing: > 2018-08-07 11:17:59,148|executor.py.167|INFO|14260|Thread-191|stdout: > ambari-server x86_64 2.7.1.0-63 ambari-2.7.1.0-63 366 M > 2018-08-07 11:17:59,148|executor.py.167|INFO|14260|Thread-191|stdout: > 2018-08-07 11:17:59,148|executor.py.167|INFO|14260|Thread-191|stdout: > Transaction Summary > 2018-08-07 11:17:59,148|executor.py.167|INFO|14260|Thread-191|stdout: > > 2018-08-07 11:17:59,148|executor.py.167|INFO|14260|Thread-191|stdout: > Install 1 Package > 2018-08-07 11:17:59,149|executor.py.167|INFO|14260|Thread-191|stdout: > 2018-08-07 11:17:59,149|executor.py.167|INFO|14260|Thread-191|stdout: > Total download size: 366 M > 2018-08-07 11:17:59,149|executor.py.167|INFO|14260|Thread-191|stdout: > Installed size: 434 M > 2018-08-07 11:17:59,152|executor.py.167|INFO|14260|Thread-191|stdout: > Downloading packages: > 2018-08-07 11:18:03,735|executor.py.167|INFO|14260|Thread-191|stdout: > Running transaction check > 2018-08-07 11:18:03,736|executor.py.167|INFO|14260|Thread-191|stdout: > Running transaction test > 2018-08-07 11:18:04,048|executor.py.167|INFO|14260|Thread-191|stdout: > Transaction test succeeded > 2018-08-07 11:18:04,049|executor.py.167|INFO|14260|Thread-191|stdout: > Running transaction > 2018-08-07 11:18:21,843|executor.py.167|INFO|14260|Thread-191|stdout: > Installing : ambari-server-2.7.1.0-63.x86_64 1/1 > 2018-08-07 11:18:22,568|executor.py.167|INFO|14260|Thread-191|stdout: > 2018-08-07 11:18:22,569|executor.py.167|INFO|14260|Thread-191|stdout: > Verifying : ambari-server-2.7.1.0-63.x86_64 1/1 > 2018-08-07 11:18:22,676|ex
[jira] [Updated] (AMBARI-24488) Ambari Server Upgrade is failing with IndexError: tuple index out of range while running ambari-server upgrade command.
[ https://issues.apache.org/jira/browse/AMBARI-24488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24488: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari Server Upgrade is failing with IndexError: tuple index out of range > while running ambari-server upgrade command. > --- > > Key: AMBARI-24488 > URL: https://issues.apache.org/jira/browse/AMBARI-24488 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24488.patch, AMBARI-24488.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24477) ambair-agent floods data directory with files created for status commands
[ https://issues.apache.org/jira/browse/AMBARI-24477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24477: -- Resolution: Fixed Status: Resolved (was: Patch Available) > ambair-agent floods data directory with files created for status commands > - > > Key: AMBARI-24477 > URL: https://issues.apache.org/jira/browse/AMBARI-24477 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24477.patch, AMBARI-24477.patch, > AMBARI-24477.patch > > Time Spent: 1h > Remaining Estimate: 0h > > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-001de461-9c2f-417a-b323-6233ed86eb37.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00209852-ad33-4026-90a0-4da2aac71403.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00333009-87b2-4649-80d1-c97b639a31f0.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-0042da27-dae6-4e9b-9ffb-336cd17787c5.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-005b6b80-baf7-43a5-aa7f-2e4695b3f478.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-0066dcd4-9406-49c7-a2b3-effd9a3a4f2b.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-006a1999-d33d-4d48-a74f-8a7830b449ec.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-0094b368-c5e1-496e-ba5b-b5080767dbc0.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-00b2a497-0088-464c-a4e4-855534d082ed.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00bbd469-370f-4eca-aee9-109db61edd75.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00bbe2f2-aeb2-4eb7-9bfb-6ce5fe9950b0.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00c341b7-5c4c-4dc5-a5ba-a550b0cabf67.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00d80541-e6a5-4bc4-9020-c018a928c6b9.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00da8bca-ac68-4d47-b492-2a978f368a1c.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00ed37ff-a9b8-4fe6-a46d-7d792586ac62.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00f49f50-cd1e-498f-ac97-5cc9724adf56.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-00f74fcb-8cc1-46f8-b74a-6ea3089e19d9.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-010174eb-dee9-41a7-9afb-25c5b16e185e.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-01024c7d-beb5-40b2-914c-aece83011cea.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-0106b69f-9343-40d1-a225-65112470f884.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-0109e024-4cbf-49a8-8496-9d05787ed58d.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-011e9c15-5531-43c9-aabf-a9efa5123d2f.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-012f2630-46ad-4608-b7ac-971d3ee35f59.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-0130258e-5c15-4147-a348-c86fa0ae5a1c.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-01357110-1577-4d4f-908d-7956232ecd73.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-013a04e5-d2e8-4d9e-8cb6-3fe3ac6f75ca.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-01456ca3-f135-4fd8-8b58-83ea513f7c06.json > 2018-08-13T21:47:09.000Z0.1 kB > status_structured-out-01473538-7a02-4df9-92c4-728d158d3e0f.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-014bdd5a-899d-43f6-a375-d65e30e0a2c3.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-014e0a58-fdc5-4d0a-8b0c-ac62129ba0ce.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-015c87f3-cdaa-4cf5-91ee-bf9af09e4262.json > 2018-08-13T21:27:31.000Z0.1 kB > status_structured-out-015c972a-9210-4854-a49b-a1d591f7
[jira] [Updated] (AMBARI-24349) Rescheduled and canceled tasks stay in progress forever
[ https://issues.apache.org/jira/browse/AMBARI-24349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24349: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Rescheduled and canceled tasks stay in progress forever > --- > > Key: AMBARI-24349 > URL: https://issues.apache.org/jira/browse/AMBARI-24349 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24349.patch, AMBARI-24349.patch > > Time Spent: 3h > Remaining Estimate: 0h > > 1\. Ambari-server reschedules task (timeout #1) > 2\. Task did yet got rescheduled (due to something else being in queue) > 3\. but, ambari-server cancels it (timeout #2) > 4\. The tasks keeps reprorting that's it's in progess forever, however being > canceled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24456) Ambari server can not start on latest Amazon Linux 2
[
https://issues.apache.org/jira/browse/AMBARI-24456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24456:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari server can not start on latest Amazon Linux 2
>
>
> Key: AMBARI-24456
> URL: https://issues.apache.org/jira/browse/AMBARI-24456
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24456.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> On latest Amazon Linux 2 ambari-server cannot start with error message:
>
>
> [root@ip-10-0-222-155 cloudbreak]# ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 37, in
> from ambari_server.dbConfiguration import DATABASE_NAMES,
> LINUX_DBMS_KEYS_LIST
> File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration.py",
> line 30, in
> from ambari_server.serverConfiguration import
> decrypt_password_for_alias, get_ambari_properties, get_is_secure, \
> File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py",
> line 46, in
> OS_VERSION = OSCheck().get_os_major_version()
> File "/usr/lib/ambari-server/lib/ambari_commons/os_check.py", line 322,
> in get_os_major_version
> return OSCheck.get_os_version().split('.')[0]
> File "/usr/lib/ambari-server/lib/ambari_commons/os_check.py", line 301,
> in get_os_version
> return OSCheck.get_alias(OSCheck._get_os_type(),
> OSCheck._get_os_version())[1]
> File "/usr/lib/ambari-server/lib/ambari_commons/os_check.py", line 313,
> in _get_os_version
> raise Exception("Cannot detect os version. Exiting...")
> Exception: Cannot detect os version. Exiting...
>
> Additional infos from the machine:
>
>
> [root@ip-10-0-222-155 cloudbreak]# cat /etc/system-release
> Amazon Linux 2
> [root@ip-10-0-222-155 cloudbreak]# cat /etc/*release
> NAME="Amazon Linux"
> VERSION="2"
> ID="amzn"
> ID_LIKE="centos rhel fedora"
> VERSION_ID="2"
> PRETTY_NAME="Amazon Linux 2"
> ANSI_COLOR="0;33"
> CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
> HOME_URL="https://amazonlinux.com/";
> Amazon Linux 2
> [root@ip-10-0-222-155 cloudbreak]#
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24453) Ambari stack hook changes to create HDFS users and groups in workload cluster that has only HDFS client
[ https://issues.apache.org/jira/browse/AMBARI-24453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24453: -- Resolution: Fixed Status: Resolved (was: Patch Available) i see its merged in 2.7 so im closing this. if it needs to be in trunk as well (if its not already there), you can reopen it and moving out the fix version to 2.7.2 > Ambari stack hook changes to create HDFS users and groups in workload cluster > that has only HDFS client > --- > > Key: AMBARI-24453 > URL: https://issues.apache.org/jira/browse/AMBARI-24453 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23077) LogFeeder: create socket input
[ https://issues.apache.org/jira/browse/AMBARI-23077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23077: -- Fix Version/s: (was: 2.7.1) 3.0.0 > LogFeeder: create socket input > -- > > Key: AMBARI-23077 > URL: https://issues.apache.org/jira/browse/AMBARI-23077 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23965) Unable to add new members to LDAP Group via UI
[ https://issues.apache.org/jira/browse/AMBARI-23965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23965. --- Resolution: Won't Fix i see the PR was closed/rejected so im closing this > Unable to add new members to LDAP Group via UI > -- > > Key: AMBARI-23965 > URL: https://issues.apache.org/jira/browse/AMBARI-23965 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24309) Hadoop Metrics Sink Precheck takes 5 minutes to complete - failing the prechecks API call due to timeout.
[ https://issues.apache.org/jira/browse/AMBARI-24309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24309: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Hadoop Metrics Sink Precheck takes 5 minutes to complete - failing the > prechecks API call due to timeout. > - > > Key: AMBARI-24309 > URL: https://issues.apache.org/jira/browse/AMBARI-24309 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24309.patch, AMBARI-24309.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24416) Component Versions Are Not Reported On Initial Status Commands Anymore
[ https://issues.apache.org/jira/browse/AMBARI-24416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24416: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Component Versions Are Not Reported On Initial Status Commands Anymore > -- > > Key: AMBARI-24416 > URL: https://issues.apache.org/jira/browse/AMBARI-24416 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24416.patch > > Time Spent: 1h > Remaining Estimate: 0h > > In Ambari 2.6, some status commands were able to supply the version of the > component they were running for. This was needed especially during upgrades to > correct situations where components would fail to start but the processes were > actually running and reporting. > * During heartbeat registration, Ambari asked the agent to get the version > in the next status command: > <https://github.com/apache/ambari/blob/branch-2.6/ambari- > server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java#L416-L419> > * The status command would place the version information from the > structured out into the "extra" mapping, which would then be handled here via > an event: > <https://github.com/apache/ambari/blob/trunk/ambari- > server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java#L599-L603> > We need to replace this functionality so that component versions are reported > on registration of agents. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24324) install tasks sometimes fail
[
https://issues.apache.org/jira/browse/AMBARI-24324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24324:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> install tasks sometimes fail
>
>
> Key: AMBARI-24324
> URL: https://issues.apache.org/jira/browse/AMBARI-24324
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24324.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/ZOOKEEPER/package/scripts/zookeeper_client.py",
> line 81, in
> ZookeeperClient().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/ZOOKEEPER/package/scripts/zookeeper_client.py",
> line 61, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 836, in install_packages
> retry_count=agent_stack_retry_count)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py",
> line 30, in action_install
> self._pkg_manager.install_package(package_name,
> self.__create_context())
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line
> 219, in install_package
> shell.repository_manager_executor(cmd, self.properties, context)
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 742, in
> repository_manager_executor
> call_result = subprocess_executor(cmd, timeout=-1, env=env)
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 446, in
> subprocess_executor
> lines = [line for line in output]
> File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__
> self.gen.next()
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 528, in
> process_executor
> kill_timer.join()
> File "/usr/lib64/python2.7/threading.py", line 940, in join
> raise RuntimeError("cannot join thread before it is started")
> RuntimeError: cannot join thread before it is started
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24399) Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have any open files' while adding Namespace
[
https://issues.apache.org/jira/browse/AMBARI-24399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó reassigned AMBARI-24399:
-
Assignee: Andrew Onischuk
> Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have
> any open files' while adding Namespace
> --
>
> Key: AMBARI-24399
> URL: https://issues.apache.org/jira/browse/AMBARI-24399
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Vivek Rathod
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24399.patch, AMBARI-24399.patch
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> STR:
> Add a namespace from UI. In the last step restart required services,
> hiveserver2 restart fails. Although on retrying it comes back up
> {code}
> Traceback (most recent call last):
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 982, in restart
> self.status(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 79, in status
> check_process_status(status_params.hive_pid)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/check_process_status.py",
> line 43, in check_process_status
> raise ComponentIsNotRunning()
> ComponentIsNotRunning
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 137, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 993, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 50, in start
> self.configure(env) # FOR SECURITY
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 45, in configure
> hive(name='hiveserver2')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 119, in hive
> setup_hiveserver2()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 167, in setup_hiveserver2
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/copy_tarball.py",
> line 516, in copy_to_hdfs
> replace_existing_files=replace_existing_files,
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
> in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 654, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 651, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 354, in action_delayed
> self.action_delayed_for_nameservice(nameservice, action_name, main_resource)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 380, in action_delayed_for_nameservice
> self._create_resource()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 396, in _create_resource
> self._create_file(self.main_resource.resource.target,
> source=self.main_resource.resource.source, mode=self.mode)
> File
> "/usr/lib/ambari-agent/lib/resource_management/librarie
[jira] [Updated] (AMBARI-24399) Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have any open files' while adding Namespace
[
https://issues.apache.org/jira/browse/AMBARI-24399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24399:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Components start failing with 'Holder DFSClient_NONMAPREDUCE does not have
> any open files' while adding Namespace
> --
>
> Key: AMBARI-24399
> URL: https://issues.apache.org/jira/browse/AMBARI-24399
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Vivek Rathod
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24399.patch, AMBARI-24399.patch
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> STR:
> Add a namespace from UI. In the last step restart required services,
> hiveserver2 restart fails. Although on retrying it comes back up
> {code}
> Traceback (most recent call last):
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 982, in restart
> self.status(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 79, in status
> check_process_status(status_params.hive_pid)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/check_process_status.py",
> line 43, in check_process_status
> raise ComponentIsNotRunning()
> ComponentIsNotRunning
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 137, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 993, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 50, in start
> self.configure(env) # FOR SECURITY
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 45, in configure
> hive(name='hiveserver2')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 119, in hive
> setup_hiveserver2()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive.py",
> line 167, in setup_hiveserver2
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/copy_tarball.py",
> line 516, in copy_to_hdfs
> replace_existing_files=replace_existing_files,
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
> in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 654, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 651, in action_delayed
> self.get_hdfs_resource_executor().action_delayed(action_name, self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 354, in action_delayed
> self.action_delayed_for_nameservice(nameservice, action_name, main_resource)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 380, in action_delayed_for_nameservice
> self._create_resource()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 396, in _create_resource
> self._create_file(self.main_resource.resource.target,
> source=self.main_resource.resource.source, mode=self.mode)
> File
> "/usr/lib/ambari-agent/lib/resourc
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24323: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24498) Upgrade History page is blank after cluster is upgraded multiple times
[ https://issues.apache.org/jira/browse/AMBARI-24498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24498. --- Resolution: Duplicate duplicate of AMBARI-24506 > Upgrade History page is blank after cluster is upgraded multiple times > -- > > Key: AMBARI-24498 > URL: https://issues.apache.org/jira/browse/AMBARI-24498 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > *STR* > # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version: > 2.6.2.14-5 > # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0 > # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0 > # Go to Upgrade history page > Upgrade history page shows empty (see attached for js error) > > Looks like an error while getting services info from older version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24506) Upgrade: Infra Solr service is not renamed in Upgrade History table
[ https://issues.apache.org/jira/browse/AMBARI-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24506: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade: Infra Solr service is not renamed in Upgrade History table > --- > > Key: AMBARI-24506 > URL: https://issues.apache.org/jira/browse/AMBARI-24506 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24506) Upgrade: Infra Solr service is not renamed in Upgrade History table
[
https://issues.apache.org/jira/browse/AMBARI-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24506:
--
Description:
*STR*
# Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version: 2.6.2.14-5
# Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
# Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
# Go to Upgrade history page
Upgrade history page shows empty (see attached for js error)
Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
workaround (before 2.7.1):
{code:java}
UPDATE upgrade_history
SET service_name = 'AMBARI_INFRA_SOLR'
WHERE service_name = 'AMBARI_INFRA'
{code}
> Upgrade: Infra Solr service is not renamed in Upgrade History table
> ---
>
> Key: AMBARI-24506
> URL: https://issues.apache.org/jira/browse/AMBARI-24506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.14-5
> # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
> # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
> # Go to Upgrade history page
> Upgrade history page shows empty (see attached for js error)
> Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
> workaround (before 2.7.1):
> {code:java}
> UPDATE upgrade_history
> SET service_name = 'AMBARI_INFRA_SOLR'
> WHERE service_name = 'AMBARI_INFRA'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24506) Upgrade: Infra Solr service is not renamed in Upgrade History table
[
https://issues.apache.org/jira/browse/AMBARI-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24506:
--
Description:
*STR*
# Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version: 2.6.2.14-5
# Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
# Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
# Go to Upgrade history page
Upgrade history page shows empty (see attached for js error)
Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
*Workaround* (before 2.7.1):
{code:java}
UPDATE upgrade_history
SET service_name = 'AMBARI_INFRA_SOLR'
WHERE service_name = 'AMBARI_INFRA'
{code}
was:
*STR*
# Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version: 2.6.2.14-5
# Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
# Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
# Go to Upgrade history page
Upgrade history page shows empty (see attached for js error)
Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
workaround (before 2.7.1):
{code:java}
UPDATE upgrade_history
SET service_name = 'AMBARI_INFRA_SOLR'
WHERE service_name = 'AMBARI_INFRA'
{code}
> Upgrade: Infra Solr service is not renamed in Upgrade History table
> ---
>
> Key: AMBARI-24506
> URL: https://issues.apache.org/jira/browse/AMBARI-24506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Deployed cluster with Ambari version: 2.5.2.0-298 and HDP version:
> 2.6.2.14-5
> # Upgrade Ambari to 2.6.2.0, HDP to 2.6.5.0
> # Upgrade Ambari to 2.7.0, HDP to 3.0.1.0
> # Go to Upgrade history page
> Upgrade history page shows empty (see attached for js error)
> Reason: upgrade_history record is not upgarade during ambari 2.7.0 upgrade
> *Workaround* (before 2.7.1):
> {code:java}
> UPDATE upgrade_history
> SET service_name = 'AMBARI_INFRA_SOLR'
> WHERE service_name = 'AMBARI_INFRA'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24507) Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24507:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server
> ---
>
> Key: AMBARI-24507
> URL: https://issues.apache.org/jira/browse/AMBARI-24507
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Remove dependency on org.bouncycastle bcprov-jdk15on before version 1.6.0 for
> Ambari Server security concerns. See
> * CVE-2018-1000180 - https://nvd.nist.gov/vuln/detail/CVE-2018-1000180
> This dependency is compiled into the apacheds-all.jar from
> {code}
>
> org.apache.directory.server
> apacheds-all
> 2.0.0-M24
>
> {code}
> The relevant parts of this need to be broken out and the offending bouncy
> castle JAR needs to be excluded as needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24514) conf-select/stack-select operations can yield incorrect result with parallel_execution=1
[ https://issues.apache.org/jira/browse/AMBARI-24514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24514: -- Resolution: Fixed Status: Resolved (was: Patch Available) > conf-select/stack-select operations can yield incorrect result with > parallel_execution=1 > > > Key: AMBARI-24514 > URL: https://issues.apache.org/jira/browse/AMBARI-24514 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24514.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24516) Default value for LDAP type
[ https://issues.apache.org/jira/browse/AMBARI-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24516: -- Fix Version/s: (was: 2.7.1) 2.7.2 > Default value for LDAP type > --- > > Key: AMBARI-24516 > URL: https://issues.apache.org/jira/browse/AMBARI-24516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.2 > > > 1. Set default value for ldap type 'Generic' > 2. command line option for configuring the ldap type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24516) Default value for LDAP type
[ https://issues.apache.org/jira/browse/AMBARI-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587224#comment-16587224 ] Olivér Szabó commented on AMBARI-24516: --- moving it out to 2.7.2 > Default value for LDAP type > --- > > Key: AMBARI-24516 > URL: https://issues.apache.org/jira/browse/AMBARI-24516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.2 > > > 1. Set default value for ldap type 'Generic' > 2. command line option for configuring the ldap type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24513) NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
[
https://issues.apache.org/jira/browse/AMBARI-24513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24513.
---
Resolution: Fixed
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB
>
>
> Key: AMBARI-24513
> URL: https://issues.apache.org/jira/browse/AMBARI-24513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> NPE when migrating users table during upgrade to Ambari 2.7.0 with Oracle DB:
> {noformat}
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:207 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> 2018-08-20 11:36:46,395 ERROR [main] SchemaUpgradeHelper:473 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:208)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:448)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.convertUserCreationTimeToLong(UpgradeCatalog270.java:595)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.upgradeUserTables(UpgradeCatalog270.java:342)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:318)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:205)
> ... 1 more
> {noformat}
> *Cause*
> This is caused by one or more records with a {{NULL}} value in the
> {{create_time}} field.
> For example:
> ||user_id||user_name||user_type||create_time||
> |1|admin|LOCAL|NULL|
> *Workaround*
> Update the relevant records to not have a {{NULL}} in the {{create_time}}
> column.
> For example:
> {noformat}
> UPDATE users SET create_time=systimestamp WHERE create_time IS NULL;
> {noformat}
> *Solution*
> During upgrade, protect against a {{null}} value for
> {{currentUserCreateTime.getValue()}} at:
> {code:java|title=org/apache/ambari/server/upgrade/UpgradeCatalog270.java:595}
> dbAccessor.updateTable(USERS_TABLE, temporaryColumnName,
> currentUserCreateTime.getValue().getTime(),
> "WHERE " + USERS_USER_ID_COLUMN + "=" +
> currentUserCreateTime.getKey());
> {code}
> If {{currentUserCreateTime.getValue()}} is null, the current timestamp should
> be used.
> *Note:* This may be a reoccurring issue since there is no provision to ensure
> that {{create_time}} is not {{NULL}} when initializing the Ambari database:
> {code:java}
> insert into users(user_id, principal_id, user_name, user_password)
> select
> 1,1,'admin','538916f8943ec225d97a9a86a2c6ec0818c1cd400e09e03b660fdaaec4af29ddbb6f2b1033b81b00'
> from dual;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári updated AMBARI-24499:
---
Status: Patch Available (was: In Progress)
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24499) Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
[
https://issues.apache.org/jira/browse/AMBARI-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24499:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Blueprint deployments fail with multiple TIMELINE_READER instances
> -
>
> Key: AMBARI-24499
> URL: https://issues.apache.org/jira/browse/AMBARI-24499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Nettleton
>Assignee: Balázs Bence Sári
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The BlueprintConfigurationProcessor does not current handle the case of
> multiple Yarn TIMELINE_READER instances properly.
> Generally, only a singleton instance of the TIMELINE_READER instance is
> deployed, but there might be scenarios in which customers will choose to
> deploy more than one instance, with just one instance running at a given
> time.
> Currently, deploying a Blueprint with multiple TIMELINE_READER instances
> fails with the following exception:
> {code:java}
> java.lang.IllegalArgumentException: Unable to update configuration property
> 'yarn.timeline-service.reader.webapp.address' with topology information.
> Component 'TIMELINE_READER' is mapped to an invalid number of hosts '2'.
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$SingleHostTopologyUpdater.updateForClusterCreate(BlueprintConfigurationProcessor.java:1945)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.updateValue(BlueprintConfigurationProcessor.java:739)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doGeneralPropertyUpdatesForClusterCreate(BlueprintConfigurationProcessor.java:641)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:443)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:152)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:80)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at
> org.apache.ambari.server.topology.tasks.ConfigureClusterTask.call(ConfigureClusterTask.java:45)
> at
> org.apache.ambari.server.security.authorization.internal.InternalAuthenticationInterceptor.invoke(InternalAuthenticationInterceptor.java:45)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> The BlueprintConfiguration processor should be updated to allow for more than
> one TIMELINE_READER instance to be deployed. This assumes that the Blueprint
> developer will set any Yarn properties required that point towards the
> TIMELINE_READER instance, including the usage of HOSTGROUP properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24558) Add setup.py for ambari-commons (for pip)
Olivér Szabó created AMBARI-24558: - Summary: Add setup.py for ambari-commons (for pip) Key: AMBARI-24558 URL: https://issues.apache.org/jira/browse/AMBARI-24558 Project: Ambari Issue Type: Bug Components: ambari-agent, ambari-server Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24558) Add setup.py for ambari-commons (for pip)
[ https://issues.apache.org/jira/browse/AMBARI-24558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24558. --- Resolution: Fixed > Add setup.py for ambari-commons (for pip) > - > > Key: AMBARI-24558 > URL: https://issues.apache.org/jira/browse/AMBARI-24558 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
[ https://issues.apache.org/jira/browse/AMBARI-24435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24435: -- Fix Version/s: (was: 2.7.2) 2.7.1 > [Log Search UI] Remove underline text decoration from dropdowns on hover > > > Key: AMBARI-24435 > URL: https://issues.apache.org/jira/browse/AMBARI-24435 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 2h > Time Spent: 3h > Remaining Estimate: 0h > > The dropdown buttons have underline text decoration on mouse hover, it should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
[ https://issues.apache.org/jira/browse/AMBARI-24435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24435: -- Fix Version/s: (was: 2.7.1) 2.7.2 > [Log Search UI] Remove underline text decoration from dropdowns on hover > > > Key: AMBARI-24435 > URL: https://issues.apache.org/jira/browse/AMBARI-24435 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.2 > > Original Estimate: 2h > Time Spent: 3h > Remaining Estimate: 0h > > The dropdown buttons have underline text decoration on mouse hover, it should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24592) Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart
Balázs Bence Sári created AMBARI-24592: -- Summary: Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart Key: AMBARI-24592 URL: https://issues.apache.org/jira/browse/AMBARI-24592 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0, 2.7.1 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 2.7.2 The issue occurs with exported blueprints. These blueprints contain the stack defaults. When a new cluster is installed from such blueprint the *BlueprintConfigurationProcessor* falsely thinks it updates _cluster-env_ when setting the stack defaults. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24592) Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart
[ https://issues.apache.org/jira/browse/AMBARI-24592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári resolved AMBARI-24592. Resolution: Fixed > Blueprint installation stuck (cannot resolve cluster-env), continues after > ambari-server restart > > > Key: AMBARI-24592 > URL: https://issues.apache.org/jira/browse/AMBARI-24592 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0, 2.7.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > > The issue occurs with exported blueprints. These blueprints contain the stack > defaults. When a new cluster is installed from such blueprint the > *BlueprintConfigurationProcessor* falsely thinks it updates _cluster-env_ > when setting the stack defaults. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24355) Logfeeder: include log type in checkpoint file names
[ https://issues.apache.org/jira/browse/AMBARI-24355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24355: -- Summary: Logfeeder: include log type in checkpoint file names (was: Logfeeder: use 1 file / db to store checkpoints) > Logfeeder: include log type in checkpoint file names > > > Key: AMBARI-24355 > URL: https://issues.apache.org/jira/browse/AMBARI-24355 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-13038) Define ephemeral port range for Ambari agents
[ https://issues.apache.org/jira/browse/AMBARI-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-13038: -- Resolution: Won't Fix Status: Resolved (was: Patch Available) I'm setting this as won't fix. if this will has high priority we can re-open this > Define ephemeral port range for Ambari agents > - > > Key: AMBARI-13038 > URL: https://issues.apache.org/jira/browse/AMBARI-13038 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.1.0 > Environment: All >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-13038.patch, EphemeralPortRange.pdf > > > Problem: > When Ambari agent starts,it tries to use an ephemeral port that is already in > use by another component. > Steps to Reproduce: > 1. Install a cluster with Ambari > 2. Restart the Ambari agent until it takes a port in use by another service > Solution: > Range of ephemeral ports used by Ambari should be narrowed. (configurable) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24355) Logfeeder: create CLI for checkpoints and include log type in checkpoint file names
[ https://issues.apache.org/jira/browse/AMBARI-24355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24355: -- Summary: Logfeeder: create CLI for checkpoints and include log type in checkpoint file names (was: Logfeeder: include log type in checkpoint file names) > Logfeeder: create CLI for checkpoints and include log type in checkpoint file > names > --- > > Key: AMBARI-24355 > URL: https://issues.apache.org/jira/browse/AMBARI-24355 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24355) Logfeeder: create CLI for checkpoints and include log type in checkpoint file names
[ https://issues.apache.org/jira/browse/AMBARI-24355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24355. --- Resolution: Fixed > Logfeeder: create CLI for checkpoints and include log type in checkpoint file > names > --- > > Key: AMBARI-24355 > URL: https://issues.apache.org/jira/browse/AMBARI-24355 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23077) LogFeeder: create socket input
[ https://issues.apache.org/jira/browse/AMBARI-23077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23077: -- Status: Patch Available (was: In Progress) > LogFeeder: create socket input > -- > > Key: AMBARI-23077 > URL: https://issues.apache.org/jira/browse/AMBARI-23077 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23077) LogFeeder: create socket input
[ https://issues.apache.org/jira/browse/AMBARI-23077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23077: -- Resolution: Fixed Status: Resolved (was: Patch Available) > LogFeeder: create socket input > -- > > Key: AMBARI-23077 > URL: https://issues.apache.org/jira/browse/AMBARI-23077 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24609) Install common ambari python libraries to maven repository (local / remote)
Olivér Szabó created AMBARI-24609: - Summary: Install common ambari python libraries to maven repository (local / remote) Key: AMBARI-24609 URL: https://issues.apache.org/jira/browse/AMBARI-24609 Project: Ambari Issue Type: Bug Components: ambari-agent, ambari-server Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24609) Ability to install common ambari python libraries to maven repository (local / remote)
[ https://issues.apache.org/jira/browse/AMBARI-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24609: -- Summary: Ability to install common ambari python libraries to maven repository (local / remote) (was: Install common ambari python libraries to maven repository (local / remote)) > Ability to install common ambari python libraries to maven repository (local > / remote) > -- > > Key: AMBARI-24609 > URL: https://issues.apache.org/jira/browse/AMBARI-24609 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24609) Ability to install common ambari python libraries to maven repository (local / remote)
[
https://issues.apache.org/jira/browse/AMBARI-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24609:
--
Description:
New cli script to create a maven tar.gz artifact:
- `--clean` option to just delete dist directories
- by default it uses `mvn install` on the generated tar.gz, that install the
artifact into local maven repository
- `--deploy` option to use `mvn deploy` for uploading generated tar.gz
artifact to remote maven repository
- `--version` option to provide the artifact and generated python dist version
- update setup.py script to read the version from pom.xml during dist
building, otherwise it uses PKG-INFO to get the right version, therefore if you
are overriding the version during the build, it will always use the right
version with pip or setup.py
How it works:
with setup.py an installable distribution created, with pip the packages are
installed locally, then the install-ambari-python script creates a tar.gz from
the installd packages and upload it to a maven repo (tar.gz content is the
site-packages, the python version before that is not included)
after the artifacts are installed to maven repos, these could be provided in
external projects (to use to extend PYTHONPATH variable, in order to run tests
against any stack code, like in MPacks);
Maven example:
{code:xml}
org.apache.ambari
ambari-python
2.0.0.0-SNAPSHOT
test
{code}
Gradle example:
{code:groovy}
testCompile "org.apache.ambari:ambari-python:2.0.0.0-snaps...@tar.gz"
{code}
So in an external project, the ambari python files can be extracted during
build time, and add them to the PYTHONPATH
Usage examples:
Install to maven local repo
{code:bash}
./install-ambari-python.sh
{code}
Deploy to maven remote repo
{code:bash}
./install-ambari-python.sh --deploy -i -r
{code}
> Ability to install common ambari python libraries to maven repository (local
> / remote)
> --
>
> Key: AMBARI-24609
> URL: https://issues.apache.org/jira/browse/AMBARI-24609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> New cli script to create a maven tar.gz artifact:
> - `--clean` option to just delete dist directories
> - by default it uses `mvn install` on the generated tar.gz, that install the
> artifact into local maven repository
> - `--deploy` option to use `mvn deploy` for uploading generated tar.gz
> artifact to remote maven repository
> - `--version` option to provide the artifact and generated python dist
> version
> - update setup.py script to read the version from pom.xml during dist
> building, otherwise it uses PKG-INFO to get the right version, therefore if
> you are overriding the version during the build, it will always use the right
> version with pip or setup.py
> How it works:
> with setup.py an installable distribution created, with pip the packages are
> installed locally, then the install-ambari-python script creates a tar.gz
> from the installd packages and upload it to a maven repo (tar.gz content is
> the site-packages, the python version before that is not included)
> after the artifacts are installed to maven repos, these could be provided in
> external projects (to use to extend PYTHONPATH variable, in order to run
> tests against any stack code, like in MPacks);
> Maven example:
> {code:xml}
>
> org.apache.ambari
> ambari-python
> 2.0.0.0-SNAPSHOT
> test
>
> {code}
> Gradle example:
> {code:groovy}
> testCompile "org.apache.ambari:ambari-python:2.0.0.0-snaps...@tar.gz"
> {code}
> So in an external project, the ambari python files can be extracted during
> build time, and add them to the PYTHONPATH
> Usage examples:
> Install to maven local repo
> {code:bash}
> ./install-ambari-python.sh
> {code}
> Deploy to maven remote repo
> {code:bash}
> ./install-ambari-python.sh --deploy -i -r
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24609) Ability to install common ambari python libraries to maven repository (local / remote)
[
https://issues.apache.org/jira/browse/AMBARI-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24609.
---
Resolution: Fixed
> Ability to install common ambari python libraries to maven repository (local
> / remote)
> --
>
> Key: AMBARI-24609
> URL: https://issues.apache.org/jira/browse/AMBARI-24609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> New cli script to create a maven tar.gz artifact:
> - `--clean` option to just delete dist directories
> - by default it uses `mvn install` on the generated tar.gz, that install the
> artifact into local maven repository
> - `--deploy` option to use `mvn deploy` for uploading generated tar.gz
> artifact to remote maven repository
> - `--version` option to provide the artifact and generated python dist
> version
> - update setup.py script to read the version from pom.xml during dist
> building, otherwise it uses PKG-INFO to get the right version, therefore if
> you are overriding the version during the build, it will always use the right
> version with pip or setup.py
> How it works:
> with setup.py an installable distribution created, with pip the packages are
> installed locally, then the install-ambari-python script creates a tar.gz
> from the installd packages and upload it to a maven repo (tar.gz content is
> the site-packages, the python version before that is not included)
> after the artifacts are installed to maven repos, these could be provided in
> external projects (to use to extend PYTHONPATH variable, in order to run
> tests against any stack code, like in MPacks);
> Maven example:
> {code:xml}
>
> org.apache.ambari
> ambari-python
> 2.0.0.0-SNAPSHOT
> test
>
> {code}
> Gradle example:
> {code:groovy}
> testCompile "org.apache.ambari:ambari-python:2.0.0.0-snaps...@tar.gz"
> {code}
> So in an external project, the ambari python files can be extracted during
> build time, and add them to the PYTHONPATH
> Usage examples:
> Install to maven local repo
> {code:bash}
> ./install-ambari-python.sh
> {code}
> Deploy to maven remote repo
> {code:bash}
> ./install-ambari-python.sh --deploy -i -r
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24624) Log Search: Field type 'key_lower_case' not found - in Solr
Olivér Szabó created AMBARI-24624: - Summary: Log Search: Field type 'key_lower_case' not found - in Solr Key: AMBARI-24624 URL: https://issues.apache.org/jira/browse/AMBARI-24624 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24624) Log Search: Field type 'key_lower_case' not found - in Solr
[
https://issues.apache.org/jira/browse/AMBARI-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24624:
--
Description: in managed-schema of the service logs, key_lower_case was
removed as a type, but there are references for that in the solrconfig.xml ->
workaround, it can be changed to {{lowercase}} from {{key_lower_case}} in
lgosearch-service_logs-solrconfig content, and restart Log Search (after that:
restart solr)
> Log Search: Field type 'key_lower_case' not found - in Solr
> ---
>
> Key: AMBARI-24624
> URL: https://issues.apache.org/jira/browse/AMBARI-24624
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.7.2
>
>
> in managed-schema of the service logs, key_lower_case was removed as a type,
> but there are references for that in the solrconfig.xml -> workaround, it can
> be changed to {{lowercase}} from {{key_lower_case}} in
> lgosearch-service_logs-solrconfig content, and restart Log Search (after
> that: restart solr)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22842) Provide field / component UI metadata from backend
[
https://issues.apache.org/jira/browse/AMBARI-22842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-22842:
--
Description:
Adding new options for the backend to get field / component metadata:
{code:java}
logsearch.web.service_logs.group.labels=k1:v1,k2:v2
logsearch.web.service_logs.component.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.excludes=v1,v2,v3
logsearch.web.service_logs.field.visible=v1,v2,v3
logsearch.web.service_logs.field.filterable.excludes=v1,v2
logsearch.web.audit_logs.component.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.labels=K1#k1:v1,k2:v2;K2#k1:v1,k3:v3
logsearch.web.audit_logs.field.common.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.visible=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.visible=v1,v2,v3
logsearch.web.audit_logs.field.excludes=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.excludes=v1,v2,v3
logsearch.web.audit_logs.field.filterable.excludes==k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.filterable.common.excludes=v1,v2,v3
logsearch.web.labels.fallback.enabled=true
logsearch.web.labels.service_logs.field.fallback.prefixes=ws_,std_,sdi_
{code}
Field metadata:
- name: real field name
- label (visible name on the UI for the field)
- visible (by default it should be visible in tables)
- filterable (it can be filterable from the searchbox) - always true by
default, if not set, contains everything which is not excluded
(audit field metadata has common values, because different metadata can be used
for different audit types)
with exclude properties you can remove fields from the response, those are also
not filtered, but you can set fields to non-filtered if they are in the
response with filterable.exclude options
Component metadata:
- name - label map: real component name with the name that should be seen on
the UI
for service component there is an additional field: group, different components
can be grouped together (like: metrics_collector and metrics_grafana can be in
the same AMS group)
`api/v1/service/logs/schema/fields` and `api/v1/audit/logs/schema/fields` will
contain field metadata
`api/v1/service/logs/components` and `api/v1/audit/logs/components` will
contain component metadata
was:
Adding new options for the backend to get field / component metadata:
{code:java}
logsearch.web.service_logs.group.labels=k1:v1,k2:v2
logsearch.web.service_logs.component.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.excludes=v1,v2,v3
logsearch.web.service_logs.field.visible=v1,v2,v3
logsearch.web.service_logs.field.filterable.excludes=v1,v2
logsearch.web.audit_logs.component.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.labels=K1#k1:v1,k2:v2;K2#k1:v1,k3:v3
logsearch.web.audit_logs.field.common.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.visible=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.visible=v1,v2,v3
logsearch.web.audit_logs.field.excludes=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.excludes=v1,v2,v3
logsearch.web.audit_logs.field.filterable.excludes==k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.filterable.common.excludes=v1,v2,v3
logsearch.web.labels.fallback.enabled=true
logsearch.web.labels.service_logs.field.fallback.prefixes=ws_,std_
logsearch.web.labels.service_logs.field.fallback.prefixes=sdi_
{code}
Field metadata:
- name: real field name
- label (visible name on the UI for the field)
- visible (by default it should be visible in tables)
- filterable (it can be filterable from the searchbox) - always true by
default, if not set, contains everything which is not excluded
(audit field metadata has common values, because different metadata can be used
for different audit types)
with exclude properties you can remove fields from the response, those are also
not filtered, but you can set fields to non-filtered if they are in the
response with filterable.exclude options
Component metadata:
- name - label map: real component name with the name that should be seen on
the UI
for service component there is an additional field: group, different components
can be grouped together (like: metrics_collector and metrics_grafana can be in
the same AMS group)
`api/v1/service/logs/schema/fields` and `api/v1/audit/logs/schema/fields` will
contain field metadata
`api/v1/service/logs/components` and `api/v1/audit/logs/components` will
contain component metadata
> Provide field / component UI metadata from backend
> --
>
> Key: AMBARI-22842
> URL: https://issues.apache.org/jira/browse/AMBARI-22842
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>
[jira] [Updated] (AMBARI-24624) Log Search: Field type 'key_lower_case' not found - in Solr
[
https://issues.apache.org/jira/browse/AMBARI-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24624:
--
Description: in managed-schema of the service logs, key_lower_case was
removed as a type, but there are references for that in the solrconfig.xml ->
workaround, it can be changed to {{lowercase}} from {{key_lower_case}} in
logsearch-service_logs-solrconfig content, and restart Log Search (after that:
restart solr) (was: in managed-schema of the service logs, key_lower_case was
removed as a type, but there are references for that in the solrconfig.xml ->
workaround, it can be changed to {{lowercase}} from {{key_lower_case}} in
lgosearch-service_logs-solrconfig content, and restart Log Search (after that:
restart solr))
> Log Search: Field type 'key_lower_case' not found - in Solr
> ---
>
> Key: AMBARI-24624
> URL: https://issues.apache.org/jira/browse/AMBARI-24624
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.7.2
>
>
> in managed-schema of the service logs, key_lower_case was removed as a type,
> but there are references for that in the solrconfig.xml -> workaround, it can
> be changed to {{lowercase}} from {{key_lower_case}} in
> logsearch-service_logs-solrconfig content, and restart Log Search (after
> that: restart solr)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24624) Log Search: Field type 'key_lower_case' not found - in Solr
[
https://issues.apache.org/jira/browse/AMBARI-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24624.
---
Resolution: Fixed
> Log Search: Field type 'key_lower_case' not found - in Solr
> ---
>
> Key: AMBARI-24624
> URL: https://issues.apache.org/jira/browse/AMBARI-24624
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> in managed-schema of the service logs, key_lower_case was removed as a type,
> but there are references for that in the solrconfig.xml -> workaround, it can
> be changed to {{lowercase}} from {{key_lower_case}} in
> logsearch-service_logs-solrconfig content, and restart Log Search (after
> that: restart solr)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24626) Log Search: some solr fields are missing for service log / audit log response
Olivér Szabó created AMBARI-24626: - Summary: Log Search: some solr fields are missing for service log / audit log response Key: AMBARI-24626 URL: https://issues.apache.org/jira/browse/AMBARI-24626 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24626) Log Search: some solr fields are missing from service log / audit log response
[ https://issues.apache.org/jira/browse/AMBARI-24626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24626: -- Summary: Log Search: some solr fields are missing from service log / audit log response (was: Log Search: some solr fields are missing for service log / audit log response) > Log Search: some solr fields are missing from service log / audit log response > -- > > Key: AMBARI-24626 > URL: https://issues.apache.org/jira/browse/AMBARI-24626 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Fix For: 2.7.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24626) Log Search: some solr fields are missing from service log / audit log response
[ https://issues.apache.org/jira/browse/AMBARI-24626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24626. --- Resolution: Fixed > Log Search: some solr fields are missing from service log / audit log response > -- > > Key: AMBARI-24626 > URL: https://issues.apache.org/jira/browse/AMBARI-24626 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names mapping
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Description:
new available properties to remove suffixes:
{{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
{{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
was:
new available properties to remove suffixes:
{{ logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i }}
{{ logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> Log Search: support to remove suffixes from field names mapping
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.7.2
>
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24640) Log Search: support to remove suffixes from field names mapping
Olivér Szabó created AMBARI-24640:
-
Summary: Log Search: support to remove suffixes from field names
mapping
Key: AMBARI-24640
URL: https://issues.apache.org/jira/browse/AMBARI-24640
Project: Ambari
Issue Type: Bug
Components: ambari-logsearch
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
Fix For: 2.7.2
new available properties to remove suffixes:
{{ logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i }}
{{ logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Summary: Log Search: support to remove suffixes from field names (was: Log
Search: support to remove suffixes from field names mapping)
> Log Search: support to remove suffixes from field names
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Fix For: 2.7.2
>
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24644) Log Search: support trusted knox proxy
Olivér Szabó created AMBARI-24644: - Summary: Log Search: support trusted knox proxy Key: AMBARI-24644 URL: https://issues.apache.org/jira/browse/AMBARI-24644 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.1 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Status: Patch Available (was: In Progress)
> Log Search: support to remove suffixes from field names
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Log Search: support to remove suffixes from field names
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24648) Log Search: add simple authorization
Olivér Szabó created AMBARI-24648: - Summary: Log Search: add simple authorization Key: AMBARI-24648 URL: https://issues.apache.org/jira/browse/AMBARI-24648 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Description: Make a simple way to authorize users. At fist just create a simple one where you can list to users (who can be admin or simple user) > Log Search: add simple authorization > - > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24644: -- Fix Version/s: (was: 2.7.2) 3.0.0 > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24644. --- Resolution: Fixed > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Component/s: ambari-logsearch > Log Search: add simple authorization > - > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple file based authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Summary: Log Search: add simple file based authorization (was: Log Search: add simple authorization ) > Log Search: add simple file based authorization > > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24657) Blueprint cluster installation with host group configuration throws exception
Balázs Bence Sári created AMBARI-24657: -- Summary: Blueprint cluster installation with host group configuration throws exception Key: AMBARI-24657 URL: https://issues.apache.org/jira/browse/AMBARI-24657 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 RegisterWithConfigGroupTask throws an exception during blueprint installation in case host group configs are defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24648) Log Search: add simple file based authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24648. --- Resolution: Fixed > Log Search: add simple file based authorization > > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24662) Log Search: add simple LDAP authentication support
Olivér Szabó created AMBARI-24662: - Summary: Log Search: add simple LDAP authentication support Key: AMBARI-24662 URL: https://issues.apache.org/jira/browse/AMBARI-24662 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24662) Log Search: add simple LDAP authentication support
[ https://issues.apache.org/jira/browse/AMBARI-24662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24662. --- Resolution: Fixed > Log Search: add simple LDAP authentication support > -- > > Key: AMBARI-24662 > URL: https://issues.apache.org/jira/browse/AMBARI-24662 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24678) Config group mapping should allow multiple service instances
Balázs Bence Sári created AMBARI-24678:
--
Summary: Config group mapping should allow multiple service
instances
Key: AMBARI-24678
URL: https://issues.apache.org/jira/browse/AMBARI-24678
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Balázs Bence Sári
Assignee: Balázs Bence Sári
Unique constraints in {{clusterconfig}} do not allow multiple service instances:
{noformat:title=clusterconfig}
CONSTRAINT UQ_config_type_tag UNIQUE (cluster_id, type_name, version_tag),
CONSTRAINT UQ_config_type_version UNIQUE (cluster_id, type_name, version));
{noformat}
Adding {{service_id}} would be trivial, but {{confgroupclusterconfigmapping}}
references the first one in a foreign key:
{noformat:title=confgroupclusterconfigmapping}
CONSTRAINT FK_confg FOREIGN KEY (version_tag, config_type, cluster_id)
REFERENCES clusterconfig (version_tag, type_name, cluster_id))
{noformat}
I think it should reference {{clusterconfig}} by its surrogate key
({{config_id}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24692) JDK 11 support for Log Search
Olivér Szabó created AMBARI-24692: - Summary: JDK 11 support for Log Search Key: AMBARI-24692 URL: https://issues.apache.org/jira/browse/AMBARI-24692 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24693) Remove ambari-infra and ambari-logsearch from ambari repository
Olivér Szabó created AMBARI-24693: - Summary: Remove ambari-infra and ambari-logsearch from ambari repository Key: AMBARI-24693 URL: https://issues.apache.org/jira/browse/AMBARI-24693 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-logsearch Affects Versions: 2.7.2 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24678) Config group mapping should allow multiple service instances
[
https://issues.apache.org/jira/browse/AMBARI-24678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balázs Bence Sári resolved AMBARI-24678.
Resolution: Fixed
Fix Version/s: 3.0.0
> Config group mapping should allow multiple service instances
>
>
> Key: AMBARI-24678
> URL: https://issues.apache.org/jira/browse/AMBARI-24678
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 3.0.0
>
>
> Unique constraints in {{clusterconfig}} do not allow multiple service
> instances:
> {noformat:title=clusterconfig}
> CONSTRAINT UQ_config_type_tag UNIQUE (cluster_id, type_name, version_tag),
> CONSTRAINT UQ_config_type_version UNIQUE (cluster_id, type_name, version));
> {noformat}
> Adding {{service_id}} would be trivial, but {{confgroupclusterconfigmapping}}
> references the first one in a foreign key:
> {noformat:title=confgroupclusterconfigmapping}
> CONSTRAINT FK_confg FOREIGN KEY (version_tag, config_type, cluster_id)
> REFERENCES clusterconfig (version_tag, type_name, cluster_id))
> {noformat}
> I think it should reference {{clusterconfig}} by its surrogate key
> ({{config_id}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24692) JDK 11 support for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629259#comment-16629259 ] Olivér Szabó commented on AMBARI-24692: --- see: https://github.com/apache/ambari-logsearch/commit/01162a04d70d9173ede408372bbb14eeddbc3229 > JDK 11 support for Log Search > - > > Key: AMBARI-24692 > URL: https://issues.apache.org/jira/browse/AMBARI-24692 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24692) JDK 11 support for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629259#comment-16629259 ] Olivér Szabó edited comment on AMBARI-24692 at 9/26/18 8:29 PM: see: https://github.com/apache/ambari-logsearch/commit/f6468c8fad122d6fe29652ad484d2db4383151dc was (Author: oleewere): see: https://github.com/apache/ambari-logsearch/commit/01162a04d70d9173ede408372bbb14eeddbc3229 > JDK 11 support for Log Search > - > > Key: AMBARI-24692 > URL: https://issues.apache.org/jira/browse/AMBARI-24692 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24698) Use service instance level configs instead of cluster level configs
Balázs Bence Sári created AMBARI-24698: -- Summary: Use service instance level configs instead of cluster level configs Key: AMBARI-24698 URL: https://issues.apache.org/jira/browse/AMBARI-24698 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 *Service instance level* configs are the ones that are associated with a *serviceId* while *cluster level* configurations are those which are not. Historically all configs were *cluster level* as there were no service instances. In the future all configs will be service instance level with the temporary exception of _cluster-env_. Ambari code uses *Cluster.getConfig(String configType)* method almost everywhere which returns *cluster level* configurations only. Luckily, all configs on *service instance level* are also stored as *cluster level* configs in memory in *ClusterImpl*, this is why it has worked so far. Double-storing *service instance level* configs on the *cluster level* will not work once multiple service instances will be enabled as ambiguity would occur. The *Cluster.getConfig(String configType)* method should be eliminated and the *Cluster.getConfig(String configType, Optional serviceId)* method used instead. *serviceId* should be given in all cases except when not applicable (_cluster-env_) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24692) JDK 11 support for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24692. --- Resolution: Fixed > JDK 11 support for Log Search > - > > Key: AMBARI-24692 > URL: https://issues.apache.org/jira/browse/AMBARI-24692 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24466) Add README.md for Ambari project
[ https://issues.apache.org/jira/browse/AMBARI-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24466: -- Fix Version/s: (was: 3.0.0) 2.8.0 > Add README.md for Ambari project > > > Key: AMBARI-24466 > URL: https://issues.apache.org/jira/browse/AMBARI-24466 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add README.md for Ambari project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24466) Add README.md for Ambari project
[ https://issues.apache.org/jira/browse/AMBARI-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24466. --- Resolution: Fixed > Add README.md for Ambari project > > > Key: AMBARI-24466 > URL: https://issues.apache.org/jira/browse/AMBARI-24466 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add README.md for Ambari project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24466) Add README.md for Ambari project
[ https://issues.apache.org/jira/browse/AMBARI-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24466: -- Affects Version/s: (was: 2.7.2) 2.7.1 > Add README.md for Ambari project > > > Key: AMBARI-24466 > URL: https://issues.apache.org/jira/browse/AMBARI-24466 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add README.md for Ambari project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24466) Add README.md for Ambari project
[ https://issues.apache.org/jira/browse/AMBARI-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24466: -- Affects Version/s: 2.7.2 > Add README.md for Ambari project > > > Key: AMBARI-24466 > URL: https://issues.apache.org/jira/browse/AMBARI-24466 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.7.1 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add README.md for Ambari project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24693) Remove ambari-infra and ambari-logsearch from ambari repository
[ https://issues.apache.org/jira/browse/AMBARI-24693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24693. --- Resolution: Fixed > Remove ambari-infra and ambari-logsearch from ambari repository > --- > > Key: AMBARI-24693 > URL: https://issues.apache.org/jira/browse/AMBARI-24693 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24721) Use maven docker plugin to build infra solr images
Olivér Szabó created AMBARI-24721: - Summary: Use maven docker plugin to build infra solr images Key: AMBARI-24721 URL: https://issues.apache.org/jira/browse/AMBARI-24721 Project: Ambari Issue Type: Task Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24721) Use maven docker plugin to build infra solr images
[ https://issues.apache.org/jira/browse/AMBARI-24721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24721. --- Resolution: Fixed > Use maven docker plugin to build infra solr images > -- > > Key: AMBARI-24721 > URL: https://issues.apache.org/jira/browse/AMBARI-24721 > Project: Ambari > Issue Type: Task > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24739) Add contribution guide to Log Search
Olivér Szabó created AMBARI-24739: - Summary: Add contribution guide to Log Search Key: AMBARI-24739 URL: https://issues.apache.org/jira/browse/AMBARI-24739 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24739) Add support to JDK8 build by makefile and add contribution guide to Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24739: -- Summary: Add support to JDK8 build by makefile and add contribution guide to Log Search (was: Add contribution guide to Log Search) > Add support to JDK8 build by makefile and add contribution guide to Log Search > -- > > Key: AMBARI-24739 > URL: https://issues.apache.org/jira/browse/AMBARI-24739 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24739) Add support to JDK8 build by makefile and add contribution guide to Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24739. --- Resolution: Fixed > Add support to JDK8 build by makefile and add contribution guide to Log Search > -- > > Key: AMBARI-24739 > URL: https://issues.apache.org/jira/browse/AMBARI-24739 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24743) Cleanup logsearch: add/cleanup javadoc
Olivér Szabó created AMBARI-24743: - Summary: Cleanup logsearch: add/cleanup javadoc Key: AMBARI-24743 URL: https://issues.apache.org/jira/browse/AMBARI-24743 Project: Ambari Issue Type: Task Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24743) Cleanup logsearch: add/cleanup javadoc
[ https://issues.apache.org/jira/browse/AMBARI-24743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24743: -- Component/s: ambari-logsearch > Cleanup logsearch: add/cleanup javadoc > -- > > Key: AMBARI-24743 > URL: https://issues.apache.org/jira/browse/AMBARI-24743 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24743) Cleanup logsearch: add/cleanup javadoc
[ https://issues.apache.org/jira/browse/AMBARI-24743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24743. --- Resolution: Fixed > Cleanup logsearch: add/cleanup javadoc > -- > > Key: AMBARI-24743 > URL: https://issues.apache.org/jira/browse/AMBARI-24743 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24746) Infra Solr: upgrade solr version to 7.5.0
Olivér Szabó created AMBARI-24746: - Summary: Infra Solr: upgrade solr version to 7.5.0 Key: AMBARI-24746 URL: https://issues.apache.org/jira/browse/AMBARI-24746 Project: Ambari Issue Type: Task Components: ambari-infra, ambari-logsearch Affects Versions: 2.7.3 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
Péter Gergő Barna created AMBARI-24750:
--
Summary: HTTP 500 internal server error caused by NPE when trying
to set loglevel in logsearch
Key: AMBARI-24750
URL: https://issues.apache.org/jira/browse/AMBARI-24750
Project: Ambari
Issue Type: Bug
Components: logsearch
Affects Versions: 2.7.1
Reporter: Péter Gergő Barna
This request sometimes returns HTTP 500 internal server error:
{noformat}
curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
'{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
a corresponding entry appears in this log
ambari-logsearch-portal/logsearch.json:
{noformat}
{"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
not update log level filters java.lang.NullPointerException at
org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
at
org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
at
org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) at
org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at
org.springframework.boot.web.filter.ApplicationContextHeaderFilter.doFilterInternal(ApplicationContextHeaderFilter.java:55)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.j
[jira] [Commented] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
[
https://issues.apache.org/jira/browse/AMBARI-24750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643162#comment-16643162
]
Péter Gergő Barna commented on AMBARI-24750:
[https://github.com/apache/ambari/pull/2432]
> HTTP 500 internal server error caused by NPE when trying to set loglevel in
> logsearch
> -
>
> Key: AMBARI-24750
> URL: https://issues.apache.org/jira/browse/AMBARI-24750
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Péter Gergő Barna
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This request sometimes returns HTTP 500 internal server error:
>
> {noformat}
> curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
> application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
> '{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
>
> 'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
>
> a corresponding entry appears in this log
> ambari-logsearch-portal/logsearch.json:
>
>
> {noformat}
> {"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
> not update log level filters java.lang.NullPointerException at
> org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
> org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletConta
[jira] [Resolved] (AMBARI-24746) Infra Solr: upgrade solr version to 7.5.0
[ https://issues.apache.org/jira/browse/AMBARI-24746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24746. --- Resolution: Fixed > Infra Solr: upgrade solr version to 7.5.0 > - > > Key: AMBARI-24746 > URL: https://issues.apache.org/jira/browse/AMBARI-24746 > Project: Ambari > Issue Type: Task > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.3 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24763) Infra Solr upgrade (2.7.x): ValueError: invalid literal for float():
Olivér Szabó created AMBARI-24763:
-
Summary: Infra Solr upgrade (2.7.x): ValueError: invalid literal
for float():
Key: AMBARI-24763
URL: https://issues.apache.org/jira/browse/AMBARI-24763
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
Fix For: 2.7.3
exception:
{code:java}
File "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 951, in
parse_size
return int(float(number)*units[unit])
ValueError: invalid literal for float(): 1,013.88
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24765) Fix CVE issues for Log Search (2.7.3)
Olivér Szabó created AMBARI-24765: - Summary: Fix CVE issues for Log Search (2.7.3) Key: AMBARI-24765 URL: https://issues.apache.org/jira/browse/AMBARI-24765 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.1 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24765) Fix CVE issues for Log Search (2.7.3)
[ https://issues.apache.org/jira/browse/AMBARI-24765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24765. --- Resolution: Fixed > Fix CVE issues for Log Search (2.7.3) > - > > Key: AMBARI-24765 > URL: https://issues.apache.org/jira/browse/AMBARI-24765 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24763) Infra Solr upgrade (2.7.x): ValueError: invalid literal for float():
[
https://issues.apache.org/jira/browse/AMBARI-24763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24763.
---
Resolution: Fixed
> Infra Solr upgrade (2.7.x): ValueError: invalid literal for float():
>
>
> Key: AMBARI-24763
> URL: https://issues.apache.org/jira/browse/AMBARI-24763
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> exception:
> {code:java}
> File "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 951, in
> parse_size
> return int(float(number)*units[unit])
> ValueError: invalid literal for float(): 1,013.88
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
Olivér Szabó created AMBARI-24789: - Summary: LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib Key: AMBARI-24789 URL: https://issues.apache.org/jira/browse/AMBARI-24789 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.1 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
