[jira] [Commented] (AMBARI-24849) Add Information to the SPI to Support Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-24849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669465#comment-16669465
]
Hudson commented on AMBARI-24849:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10257 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10257/])
[AMBARI-24849] Add Information to the SPI to Support Upgrade Checks (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d7ce1ef3668d551061fa0539fda7befdb6cb1b43])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HealthCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ConfigurationMergeCheckTest.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheck.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ClusterCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/VersionMismatchCheckTest.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/RepositoryVersion.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BootStrapImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/MissingOsInRepoVersionCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicePresenceCheckTest.java
* (delete)
ambari-server/src/main/java/org/apache/ambari/server/utils/VersionUtils.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckDescription.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/utils/TestVersionUtils.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostMaintenanceModeCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesUpCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/ClusterCheck.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/RequiredServicesInRepositoryCheckTest.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/ClusterInformation.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentExistsInRepoCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentsInstallationCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/KerberosAdminPersistedCredentialCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/LZOCheckTest.java
* (edit) ambari-server-spi/pom.xml
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckResult.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/AmbariMetricsHadoopSinkVersionCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsHeartbeatCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/InstallPackagesCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/PreviousUpgradeCompletedTest.java
* (add)
ambari-server-spi/src/main/java/org/apache/ambari/server/utils/VersionUtils.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/UpgradeTypeQualificationTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesMaintenanceModeCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServiceCheckValidityCheckTest.java
> Add Information to the SPI to Support Upgrade Checks
>
>
> Key: AMBARI-24849
> URL: https://issues.apache.org/jira/browse/AMBARI-24849
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While implementing some of the upgrade checks which were removed as part of
> AMBARI-24737, the SPI needed some extra information added.
> - Some checks used {{VersionUtils}}, so this needed to be relocated to the
> SPI.
>
[jira] [Commented] (AMBARI-24834) UI: Configure Rolling Restart Batch Options for service rolling restart
[ https://issues.apache.org/jira/browse/AMBARI-24834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669464#comment-16669464 ] Hudson commented on AMBARI-24834: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10257 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10257/]) [AMBARI-24834] UI: Configure Rolling Restart Batch Options for service (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=99e14e98ec5d3744f6ea8dba6a4ba2a9f7d26d63]) * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/app/views/common/service_restart_view.js * (edit) ambari-web/app/utils/batch_scheduled_requests.js > UI: Configure Rolling Restart Batch Options for service rolling restart > --- > > Key: AMBARI-24834 > URL: https://issues.apache.org/jira/browse/AMBARI-24834 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >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] [Updated] (AMBARI-24850) Use the proper stack root for Hive pre upgrade
[ https://issues.apache.org/jira/browse/AMBARI-24850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24850: Labels: pull-request-available (was: ) > Use the proper stack root for Hive pre upgrade > -- > > Key: AMBARI-24850 > URL: https://issues.apache.org/jira/browse/AMBARI-24850 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > /usr/hdp was hard coded, need to use Script.get_stack_root() instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24850) Use the proper stack root for Hive pre upgrade
Miklos Gergely created AMBARI-24850: --- Summary: Use the proper stack root for Hive pre upgrade Key: AMBARI-24850 URL: https://issues.apache.org/jira/browse/AMBARI-24850 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.7.0 /usr/hdp was hard coded, need to use Script.get_stack_root() instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24849) Add Information to the SPI to Support Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-24849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24849.
--
Resolution: Fixed
> Add Information to the SPI to Support Upgrade Checks
>
>
> Key: AMBARI-24849
> URL: https://issues.apache.org/jira/browse/AMBARI-24849
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While implementing some of the upgrade checks which were removed as part of
> AMBARI-24737, the SPI needed some extra information added.
> - Some checks used {{VersionUtils}}, so this needed to be relocated to the
> SPI.
> - Added service-level repository version information to {{ClusterInformation}}
> - Simplified the {{UpgradeCheckDescription}} when there is only 1 failure
> message.
> - Prevent NPE when {{CheckQualifications}} is {{null}} (even though Javadoc
> says it must return an empty iist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24849) Add Information to the SPI to Support Upgrade Checks
[
https://issues.apache.org/jira/browse/AMBARI-24849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24849:
Labels: pull-request-available (was: )
> Add Information to the SPI to Support Upgrade Checks
>
>
> Key: AMBARI-24849
> URL: https://issues.apache.org/jira/browse/AMBARI-24849
> Project: Ambari
> Issue Type: Task
> Components: ambari-server-spi
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> While implementing some of the upgrade checks which were removed as part of
> AMBARI-24737, the SPI needed some extra information added.
> - Some checks used {{VersionUtils}}, so this needed to be relocated to the
> SPI.
> - Added service-level repository version information to {{ClusterInformation}}
> - Simplified the {{UpgradeCheckDescription}} when there is only 1 failure
> message.
> - Prevent NPE when {{CheckQualifications}} is {{null}} (even though Javadoc
> says it must return an empty iist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24849) Add Information to the SPI to Support Upgrade Checks
Jonathan Hurley created AMBARI-24849:
Summary: Add Information to the SPI to Support Upgrade Checks
Key: AMBARI-24849
URL: https://issues.apache.org/jira/browse/AMBARI-24849
Project: Ambari
Issue Type: Task
Components: ambari-server-spi
Affects Versions: 2.8.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.8.0
While implementing some of the upgrade checks which were removed as part of
AMBARI-24737, the SPI needed some extra information added.
- Some checks used {{VersionUtils}}, so this needed to be relocated to the SPI.
- Added service-level repository version information to {{ClusterInformation}}
- Simplified the {{UpgradeCheckDescription}} when there is only 1 failure
message.
- Prevent NPE when {{CheckQualifications}} is {{null}} (even though Javadoc
says it must return an empty iist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24848) Satellite repo cluster installation Issues
[
https://issues.apache.org/jira/browse/AMBARI-24848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-24848:
--
Description:
Steps to reproduce:
---
1. Install Ambari 2.7.1
2. To install the cluster , select Satelite repo and updated tag name.
3. Enter new hosts - and click next.
4. You end of seeing WARNINGS - click on WARNING and you would see below
message.
{noformat}
The following registered hosts have different Operating System types from the
available Repositories chosen in "Select Stack" step. You can go back to
"Select Stack" step to select another OS repository or remove the host.
Same workflow with public/private repos it works fine - problem is only with
satelite repos
{noformat}
and eventually cluster installation fails with below error
{noformat}
Error 500 Server Error
HTTP ERROR 500 Problem accessing
/api/v1/clusters/test/hosts. Reason: Server ErrorCaused
by:java.lang.RuntimeException:
org.apache.ambari.server.controller.spi.SystemException: Operating System
matching redhat7 could not be found at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.retrieveHostRepositories(AmbariManagementControllerImpl.java:5891)
at
org.apache.ambari.server.agent.stomp.HostLevelParamsHolder.getCurrentDataExcludeCluster(HostLevelParamsHolder.java:78)
at
org.apache.ambari.server.agent.stomp.HostLevelParamsHolder.getCurrentData(HostLevelParamsHolder.java:67)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.getAddedComponentsTopologyEvent(AmbariManagementControllerImpl.java:807)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createHostComponents(AmbariManagementControllerImpl.java:705)
at
org.apache.ambari.server.controller.internal.HostComponentResourceProvider$1.invoke(HostComponentResourceProvider.java:213)
at
org.apache.ambari.server.controller.internal.HostComponentResourceProvider$1.invoke(HostComponentResourceProvider.java:210)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
at
org.apache.ambari.server.controller.internal.HostComponentResourceProvider.createResourcesAuthorized(HostComponentResourceProvider.java:210)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.QueryCreateHandler.persist(QueryCreateHandler.java:186)
at
org.apache.ambari.server.api.handlers.QueryCreateHandler.handleRequest(QueryCreateHandler.java:91)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.HostService.createHosts(HostService.java:170)
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
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
[jira] [Created] (AMBARI-24848) Satellite repo cluster installation Issues
amarnath reddy pappu created AMBARI-24848:
-
Summary: Satellite repo cluster installation Issues
Key: AMBARI-24848
URL: https://issues.apache.org/jira/browse/AMBARI-24848
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: amarnath reddy pappu
Attachments: Screen Shot 2018-10-30 at 11.08.12 AM.png
Steps to reproduce:
---
1. Install Ambari 2.7.1
2. To install the cluster , select Satelite repo and updated tag name.
3. Enter new hosts - and click next.
4. You end of seeing WARNINGS - click on WARNING and you would see below
message.
{noformat}
The following registered hosts have different Operating System types from the
available Repositories chosen in "Select Stack" step. You can go back to
"Select Stack" step to select another OS repository or remove the host.
Same workflow with public/private repos it works fine - problem is only with
satelite repos
{noformat}
Root cause:
In checkHostOSType function call - selectedStack.get('operatingSystems') does
not have any "isSelected" entries - hence above error message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24848) Satellite repo cluster installation Issues
[
https://issues.apache.org/jira/browse/AMBARI-24848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-24848:
--
Attachment: Screen Shot 2018-10-30 at 11.08.12 AM.png
> Satellite repo cluster installation Issues
> --
>
> Key: AMBARI-24848
> URL: https://issues.apache.org/jira/browse/AMBARI-24848
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: amarnath reddy pappu
>Priority: Major
> Attachments: Screen Shot 2018-10-30 at 11.08.12 AM.png
>
>
> Steps to reproduce:
> ---
> 1. Install Ambari 2.7.1
> 2. To install the cluster , select Satelite repo and updated tag name.
> 3. Enter new hosts - and click next.
> 4. You end of seeing WARNINGS - click on WARNING and you would see below
> message.
> {noformat}
> The following registered hosts have different Operating System types from the
> available Repositories chosen in "Select Stack" step. You can go back to
> "Select Stack" step to select another OS repository or remove the host.
> Same workflow with public/private repos it works fine - problem is only with
> satelite repos
> {noformat}
> Root cause:
> In checkHostOSType function call - selectedStack.get('operatingSystems') does
> not have any "isSelected" entries - hence above error message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23476) Install wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669077#comment-16669077 ] Naresh Bhat commented on AMBARI-23476: -- I have compiled and set-up Ambari release v2.7.1 on ARM64 machine (CentOS7.4/Debian-9). But when I click on "LAUNCH INSTALL WIZARD" I am not able to see any components. It is just showing up the blank page. > Install wizard issues > - > > Key: AMBARI-23476 > URL: https://issues.apache.org/jira/browse/AMBARI-23476 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-04-05 at 5.35.06 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > In the above cluster, when install wizard is running , reloading Ambari fails > to load the page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669043#comment-16669043 ] ASF GitHub Bot commented on AMBARI-24551: - asfgit commented on issue #5: [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps URL: https://github.com/apache/ambari-logsearch/pull/5#issuecomment-434385923 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/21/ Test FAILed. Test FAILured. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.8.0 > > Original Estimate: 4h > Time Spent: 3.5h > Remaining Estimate: 0.5h > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24784:
---
Fix Version/s: (was: 2.8.0)
2.7.3
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch,
> AMBARI-24784.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24840) Change Hostname does not honor uppercase hosts
[ https://issues.apache.org/jira/browse/AMBARI-24840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669023#comment-16669023 ] Hudson commented on AMBARI-24840: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10256 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10256/]) AMBARI-24840. Change Hostname does not honor uppercase hosts (dlisnic… (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=89de44acf2106c4c70631db4dc253b940539f6dc]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/update/HostUpdateHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java > Change Hostname does not honor uppercase hosts > -- > > Key: AMBARI-24840 > URL: https://issues.apache.org/jira/browse/AMBARI-24840 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > > During the [Ambari change hostname > procedure|https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-administration/content/ch_changing_host_names.html], > hostnames in configs when they were all uppercase are not being replaced. I > think the code is converting hosts to all lowercase to do replacements. See: > https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java#L383-L393 > Appears to affect up from 2.6.1 and 2.6.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24829) Allow blueprint install for YARN without RESOURCEMANAGER and HDFS_CLIENT without HDFS server components
[ https://issues.apache.org/jira/browse/AMBARI-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári resolved AMBARI-24829. Resolution: Fixed > Allow blueprint install for YARN without RESOURCEMANAGER and HDFS_CLIENT > without HDFS server components > --- > > Key: AMBARI-24829 > URL: https://issues.apache.org/jira/browse/AMBARI-24829 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.2 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Make the BlueprintConfigurationProcessor process HDFS_CLIENT without HDFS > server components and YARN timeline service components without the rest of > YARN server components without throwing Exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24845) Sometimes host status still in heartbeat lost after agent become heartbeating
[ https://issues.apache.org/jira/browse/AMBARI-24845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668943#comment-16668943 ] Hudson commented on AMBARI-24845: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #395 (See [https://builds.apache.org/job/Ambari-branch-2.7/395/]) AMBARI-24845. Sometimes host status still in heartbeat lost after agent (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7d19eb2e37067137d6e06a8d1a86c759db5b90fc]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java > Sometimes host status still in heartbeat lost after agent become heartbeating > - > > Key: AMBARI-24845 > URL: https://issues.apache.org/jira/browse/AMBARI-24845 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 50m > Remaining Estimate: 0h > > Sometimes initial component states update does not fire host status recheck > and host still in heartbeat lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668791#comment-16668791
]
Hudson commented on AMBARI-24784:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #394 (See
[https://builds.apache.org/job/Ambari-branch-2.7/394/])
AMBARI-24784. Ambari-agent cannot register sometimes (aonishuk) (aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3c2bc7abd66cf7c5930a52b192196d8cc2ffdbbf])
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch,
> AMBARI-24784.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24847) Logsearch: Cannot search for a term that includes spaces or dashes
Krisztian Kasa created AMBARI-24847: --- Summary: Logsearch: Cannot search for a term that includes spaces or dashes Key: AMBARI-24847 URL: https://issues.apache.org/jira/browse/AMBARI-24847 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.8.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.8.0 If I type the following "Some terrible error has happened" I got a huge amount irrelevant results from Logsearch, this is mainly because the search term is tokenized and finds every line that contains any of the words even if I am using ". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24846) Ambari-agent stop hangs if ambari-server is stopped.
[ https://issues.apache.org/jira/browse/AMBARI-24846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24846: - Attachment: AMBARI-24846.patch > Ambari-agent stop hangs if ambari-server is stopped. > > > Key: AMBARI-24846 > URL: https://issues.apache.org/jira/browse/AMBARI-24846 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24846.patch > > > [root@gc7001 ~]# ambari-agent stop > Verifying Python version compatibility... > Using python /usr/bin/python > Found ambari-agent PID: 7391 > Stopping ambari-agent > ^C^C^X^Z > [2]+ Stopped ambari-agent stop > [root@gc7001 ~]# ^C > [root@gc7001 ~]# kill -9 7391 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24846) Ambari-agent stop hangs if ambari-server is stopped.
[ https://issues.apache.org/jira/browse/AMBARI-24846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24846: - Status: Patch Available (was: Open) > Ambari-agent stop hangs if ambari-server is stopped. > > > Key: AMBARI-24846 > URL: https://issues.apache.org/jira/browse/AMBARI-24846 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24846.patch > > > [root@gc7001 ~]# ambari-agent stop > Verifying Python version compatibility... > Using python /usr/bin/python > Found ambari-agent PID: 7391 > Stopping ambari-agent > ^C^C^X^Z > [2]+ Stopped ambari-agent stop > [root@gc7001 ~]# ^C > [root@gc7001 ~]# kill -9 7391 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24846) Ambari-agent stop hangs if ambari-server is stopped.
[ https://issues.apache.org/jira/browse/AMBARI-24846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24846: Labels: pull-request-available (was: ) > Ambari-agent stop hangs if ambari-server is stopped. > > > Key: AMBARI-24846 > URL: https://issues.apache.org/jira/browse/AMBARI-24846 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24846.patch > > > [root@gc7001 ~]# ambari-agent stop > Verifying Python version compatibility... > Using python /usr/bin/python > Found ambari-agent PID: 7391 > Stopping ambari-agent > ^C^C^X^Z > [2]+ Stopped ambari-agent stop > [root@gc7001 ~]# ^C > [root@gc7001 ~]# kill -9 7391 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24846) Ambari-agent stop hangs if ambari-server is stopped.
Andrew Onischuk created AMBARI-24846: Summary: Ambari-agent stop hangs if ambari-server is stopped. Key: AMBARI-24846 URL: https://issues.apache.org/jira/browse/AMBARI-24846 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.8.0 Attachments: AMBARI-24846.patch [root@gc7001 ~]# ambari-agent stop Verifying Python version compatibility... Using python /usr/bin/python Found ambari-agent PID: 7391 Stopping ambari-agent ^C^C^X^Z [2]+ Stopped ambari-agent stop [root@gc7001 ~]# ^C [root@gc7001 ~]# kill -9 7391 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24845) Sometimes host status still in heartbeat lost after agent become heartbeating
[ https://issues.apache.org/jira/browse/AMBARI-24845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24845: Labels: pull-request-available (was: ) > Sometimes host status still in heartbeat lost after agent become heartbeating > - > > Key: AMBARI-24845 > URL: https://issues.apache.org/jira/browse/AMBARI-24845 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > > Sometimes initial component states update does not fire host status recheck > and host still in heartbeat lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24845) Sometimes host status still in heartbeat lost after agent become heartbeating
Myroslav Papirkovskyi created AMBARI-24845: -- Summary: Sometimes host status still in heartbeat lost after agent become heartbeating Key: AMBARI-24845 URL: https://issues.apache.org/jira/browse/AMBARI-24845 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.3 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.3 Sometimes initial component states update does not fire host status recheck and host still in heartbeat lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24784:
-
Attachment: AMBARI-24784.patch
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch,
> AMBARI-24784.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24784:
-
Attachment: AMBARI-24784.patch
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
