[jira] [Commented] (AMBARI-25061) Refactor AddServiceInfo to use a builder
[
https://issues.apache.org/jira/browse/AMBARI-25061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736312#comment-16736312
]
Hudson commented on AMBARI-25061:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10414 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10414/])
AMBARI-25061. Refactor AddServiceInfo to use a builder (#2756) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=883d95f7a93ed53e637b617acd86cd2bf9b5c3fd])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/RequestValidator.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/addservice/ProvisionActionPredicateBuilderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/addservice/StackAdvisorAdapterTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/AddServiceInfo.java
> Refactor AddServiceInfo to use a builder
>
>
> Key: AMBARI-25061
> URL: https://issues.apache.org/jira/browse/AMBARI-25061
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{AddServiceInfo}} constructor could be improved by the Builder pattern.
> https://github.com/apache/ambari/blob/1431ab44887c2ff7f9e94f8fcb42e24e3ce33800/ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/AddServiceInfo.java#L45-L83
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-25061) Refactor AddServiceInfo to use a builder
[
https://issues.apache.org/jira/browse/AMBARI-25061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-25061.
Resolution: Implemented
> Refactor AddServiceInfo to use a builder
>
>
> Key: AMBARI-25061
> URL: https://issues.apache.org/jira/browse/AMBARI-25061
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{AddServiceInfo}} constructor could be improved by the Builder pattern.
> https://github.com/apache/ambari/blob/1431ab44887c2ff7f9e94f8fcb42e24e3ce33800/ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/AddServiceInfo.java#L45-L83
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25090) Logsearch should index keywords without the ending periods(.)
[ https://issues.apache.org/jira/browse/AMBARI-25090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-25090: - Reporter: Kishor Ramakrishnan (was: Krisztian Kasa) > Logsearch should index keywords without the ending periods(.) > - > > Key: AMBARI-25090 > URL: https://issues.apache.org/jira/browse/AMBARI-25090 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Kishor Ramakrishnan >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.8.0 > > > Logsearch should index keywords without the ending periods(.). > E.g : Log message : "Caught exception checkIn.". Message filters were not > able to filter the logs with partial text "checkIn" but only with "checkIn." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25090) Logsearch should index keywords without the ending periods(.)
Krisztian Kasa created AMBARI-25090: --- Summary: Logsearch should index keywords without the ending periods(.) Key: AMBARI-25090 URL: https://issues.apache.org/jira/browse/AMBARI-25090 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.8.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.8.0 Logsearch should index keywords without the ending periods(.). E.g : Log message : "Caught exception checkIn.". Message filters were not able to filter the logs with partial text "checkIn" but only with "checkIn." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25069) Ambari writes Empty baseurl values written to Repo Files when using a local repository causing stack installation failure
[
https://issues.apache.org/jira/browse/AMBARI-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-25069:
---
Fix Version/s: 2.8.0
> Ambari writes Empty baseurl values written to Repo Files when using a local
> repository causing stack installation failure
> -
>
> Key: AMBARI-25069
> URL: https://issues.apache.org/jira/browse/AMBARI-25069
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: Screen Shot 2018-12-26 at 10.12.29 AM.png, Screen Shot
> 2018-12-26 at 10.13.14 AM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> when using a local repository, installation fails due to empty baseurls being
> written to the Ambari repository (even though local repository baseurl values
> were provided). The installation fails with below error :
> {code:java}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 352, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_packages()
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/shared_initialization.py",
> line 37, in install_packages
> retry_count=params.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 753, in
> repository_manager_executor
> raise RuntimeError(message)
> RuntimeError: Failed to execute command '/usr/bin/yum -y install hdp-select',
> exited with code '1', message: 'Repository InstallMedia is listed more than
> once in the configuration
>
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this:
>
> 1. Contact the upstream for the repository and get them to fix the
> problem.
>
> 2. Reconfigure the baseurl/etc. for the repository, to point to a working
>
>upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work).
>
> 3. Run the command with the repository temporarily disabled
>
> yum --disablerepo= ...
>
> 4. Disable the repository permanently, so yum won't use it by default.
> Yum will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
> yum-config-manager --disable
> or
> subscription-manager repos --disable=
> 5. Configure the failing repository to be skipped, if it is unavailable.
> Note that yum will try to contact the repo. when it runs most
> commands,so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a nice
> compromise:
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true
>
> Cannot find a valid baseurl for repo: HDP-3.1-repo-1
> '
> Command aborted. Reason: 'Server considered task failed and automatically
> aborted it'
> stdout:
> {code}
> We can See that Ambari UI shows the empty baseURL in review step
> !Screen Shot 2018-12-26 at 10.12.29 AM.png|height=350,width=850!
> It also sends the empty Repo version while deploy stage
> !Screen Shot 2018-12-26 at 10.13.14 AM.png|height=350,width=850!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25061) Refactor AddServiceInfo to use a builder
[
https://issues.apache.org/jira/browse/AMBARI-25061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25061:
Labels: pull-request-available (was: )
> Refactor AddServiceInfo to use a builder
>
>
> Key: AMBARI-25061
> URL: https://issues.apache.org/jira/browse/AMBARI-25061
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> {{AddServiceInfo}} constructor could be improved by the Builder pattern.
> https://github.com/apache/ambari/blob/1431ab44887c2ff7f9e94f8fcb42e24e3ce33800/ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/AddServiceInfo.java#L45-L83
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735934#comment-16735934 ] Hudson commented on AMBARI-23456: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #92 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/92/]) AMBARI-23456. Update development docs (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=0ace4f5d15ce6f8eb3d3ef2e0ab6ba722319d435]) * (edit) docs/development.md > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735892#comment-16735892 ] Hudson commented on AMBARI-23456: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #91 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/91/]) AMBARI-23456. Update development docs (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=423635b74231f3bb2766e26c8dc294b6837199ca]) * (edit) docs/development.md > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23456) Log Search: generate mardown docs for properties and logfeeder configs based on annotations
[ https://issues.apache.org/jira/browse/AMBARI-23456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735830#comment-16735830 ] Hudson commented on AMBARI-23456: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #90 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/90/]) AMBARI-23456. Make rest api doc generation configureable & doc fixes (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=eeb9da1d5ae1df5cb17bb3294d4c698dd3d86d17]) * (edit) ambari-logsearch-docs/src/main/java/org/apache/ambari/logsearch/doc/LogSearchDocumentationGenerator.java * (edit) ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/ServiceLogsResource.java * (edit) Makefile * (edit) ambari-logsearch-docs/pom.xml * (edit) docs/api-docs/logsearch-swagger.yaml > Log Search: generate mardown docs for properties and logfeeder configs based > on annotations > --- > > Key: AMBARI-23456 > URL: https://issues.apache.org/jira/browse/AMBARI-23456 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.8.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
