[jira] [Updated] (AMBARI-21685) Component fails to install with error, "The stack packages are not defined on the command. Unable to load packages for the stack-select tool"
[
https://issues.apache.org/jira/browse/AMBARI-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21685:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit ea2c432fcff5807b3cffc5cb94e0764cb8f94aa7
> Component fails to install with error, "The stack packages are not defined on
> the command. Unable to load packages for the stack-select tool"
> -
>
> Key: AMBARI-21685
> URL: https://issues.apache.org/jira/browse/AMBARI-21685
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Kishor Ramakrishnan
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-21685.patch
>
>
> STR:
> * Install Ambari 3.0 build 1020
> * Install HDP 3.0
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21685) Component fails to install with error, "The stack packages are not defined on the command. Unable to load packages for the stack-select tool"
[
https://issues.apache.org/jira/browse/AMBARI-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21685:
-
Status: Patch Available (was: Open)
> Component fails to install with error, "The stack packages are not defined on
> the command. Unable to load packages for the stack-select tool"
> -
>
> Key: AMBARI-21685
> URL: https://issues.apache.org/jira/browse/AMBARI-21685
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Kishor Ramakrishnan
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-21685.patch
>
>
> STR:
> * Install Ambari 3.0 build 1020
> * Install HDP 3.0
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21685) Component fails to install with error, "The stack packages are not defined on the command. Unable to load packages for the stack-select tool"
[
https://issues.apache.org/jira/browse/AMBARI-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21685:
-
Attachment: AMBARI-21685.patch
> Component fails to install with error, "The stack packages are not defined on
> the command. Unable to load packages for the stack-select tool"
> -
>
> Key: AMBARI-21685
> URL: https://issues.apache.org/jira/browse/AMBARI-21685
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Kishor Ramakrishnan
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-21685.patch
>
>
> STR:
> * Install Ambari 3.0 build 1020
> * Install HDP 3.0
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21685) Component fails to install with error, "The stack packages are not defined on the command. Unable to load packages for the stack-select tool"
[
https://issues.apache.org/jira/browse/AMBARI-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21685:
-
Reporter: Kishor Ramakrishnan (was: Alejandro Fernandez)
> Component fails to install with error, "The stack packages are not defined on
> the command. Unable to load packages for the stack-select tool"
> -
>
> Key: AMBARI-21685
> URL: https://issues.apache.org/jira/browse/AMBARI-21685
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Kishor Ramakrishnan
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
>
> STR:
> * Install Ambari 3.0 build 1020
> * Install HDP 3.0
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 336, in execute
> self.save_component_version_to_structured_out()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 218, in save_component_version_to_structured_out
> stack_select_package_name = stack_select.get_package_name()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 98, in get_package_name
> package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
> component_name)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
> line 143, in get_packages
> raise Fail("The stack packages are not defined on the command. Unable to
> load packages for the stack-select tool")
> resource_management.core.exceptions.Fail: The stack packages are not defined
> on the command. Unable to load packages for the stack-select tool
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21685) Component fails to install with error, "The stack packages are not defined on the command. Unable to load packages for the stack-select tool"
Alejandro Fernandez created AMBARI-21685:
Summary: Component fails to install with error, "The stack
packages are not defined on the command. Unable to load packages for the
stack-select tool"
Key: AMBARI-21685
URL: https://issues.apache.org/jira/browse/AMBARI-21685
Project: Ambari
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 3.0.0
STR:
* Install Ambari 3.0 build 1020
* Install HDP 3.0
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
line 37, in
BeforeInstallHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 336, in execute
self.save_component_version_to_structured_out()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 218, in save_component_version_to_structured_out
stack_select_package_name = stack_select.get_package_name()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 98, in get_package_name
package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
component_name)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 143, in get_packages
raise Fail("The stack packages are not defined on the command. Unable to
load packages for the stack-select tool")
resource_management.core.exceptions.Fail: The stack packages are not defined on
the command. Unable to load packages for the stack-select tool
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/hooks/before-INSTALL/scripts/hook.py",
line 37, in
BeforeInstallHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 336, in execute
self.save_component_version_to_structured_out()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 218, in save_component_version_to_structured_out
stack_select_package_name = stack_select.get_package_name()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 98, in get_package_name
package = get_packages(PACKAGE_SCOPE_STACK_SELECT, service_name,
component_name)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_select.py",
line 143, in get_packages
raise Fail("The stack packages are not defined on the command. Unable to
load packages for the stack-select tool")
resource_management.core.exceptions.Fail: The stack packages are not defined on
the command. Unable to load packages for the stack-select tool
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21673) Deploy fails with alert_state constraint violation
[
https://issues.apache.org/jira/browse/AMBARI-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21673:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit e88b61e6c7831a569876dcbac524fbe2b465c967
> Deploy fails with alert_state constraint violation
> --
>
> Key: AMBARI-21673
> URL: https://issues.apache.org/jira/browse/AMBARI-21673
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-21673.patch
>
>
> From Ambari server logs:
> {code:java}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label,
> alert_state, alert_text, alert_timestamp, cluster_id, component_name,
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?)
> bind => [11 parameters bound]
> Query: UpdateObjectQuery(AlertCurrentEntity{alertId=9,
> name=namenode_last_checkpoint, state=UNKNOWN, latestTimestamp=1501086624471})
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:797)
> at
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:435)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1078)
> at
> org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839)
> at
>
[jira] [Commented] (AMBARI-21673) Deploy fails with alert_state constraint violation
[
https://issues.apache.org/jira/browse/AMBARI-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117593#comment-16117593
]
Alejandro Fernandez commented on AMBARI-21673:
--
+1 LGTM
> Deploy fails with alert_state constraint violation
> --
>
> Key: AMBARI-21673
> URL: https://issues.apache.org/jira/browse/AMBARI-21673
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-21673.patch
>
>
> From Ambari server logs:
> {code:java}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label,
> alert_state, alert_text, alert_timestamp, cluster_id, component_name,
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?)
> bind => [11 parameters bound]
> Query: UpdateObjectQuery(AlertCurrentEntity{alertId=9,
> name=namenode_last_checkpoint, state=UNKNOWN, latestTimestamp=1501086624471})
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:797)
> at
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:435)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1078)
> at
> org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790)
> at
>
[jira] [Updated] (AMBARI-21673) Deploy fails with alert_state constraint violation
[
https://issues.apache.org/jira/browse/AMBARI-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21673:
-
Attachment: AMBARI-21673.patch
> Deploy fails with alert_state constraint violation
> --
>
> Key: AMBARI-21673
> URL: https://issues.apache.org/jira/browse/AMBARI-21673
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-21673.patch
>
>
> From Ambari server logs:
> {code:java}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label,
> alert_state, alert_text, alert_timestamp, cluster_id, component_name,
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?)
> bind => [11 parameters bound]
> Query: UpdateObjectQuery(AlertCurrentEntity{alertId=9,
> name=namenode_last_checkpoint, state=UNKNOWN, latestTimestamp=1501086624471})
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:797)
> at
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:435)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1078)
> at
> org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790)
> at
>
[jira] [Updated] (AMBARI-21673) Deploy fails with alert_state constraint violation
[
https://issues.apache.org/jira/browse/AMBARI-21673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21673:
-
Status: Patch Available (was: Open)
> Deploy fails with alert_state constraint violation
> --
>
> Key: AMBARI-21673
> URL: https://issues.apache.org/jira/browse/AMBARI-21673
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-21673.patch
>
>
> From Ambari server logs:
> {code:java}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Column 'alert_state' cannot be null
> Error Code: 1048
> Call: INSERT INTO alert_history (alert_id, alert_instance, alert_label,
> alert_state, alert_text, alert_timestamp, cluster_id, component_name,
> host_name, service_name, alert_definition_id) VALUES (?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?)
> bind => [11 parameters bound]
> Query: UpdateObjectQuery(AlertCurrentEntity{alertId=9,
> name=namenode_last_checkpoint, state=UNKNOWN, latestTimestamp=1501086624471})
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:902)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.appendCall(ParameterizedSQLBatchWritingMechanism.java:82)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:605)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:560)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:2055)
> at
> org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:306)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
> at
> org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:797)
> at
> org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:435)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1078)
> at
> org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
> at
> org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
> at
> org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
> at
> org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:904)
> at
> org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:803)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
> at
> org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1857)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1839)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1790)
> at
>
[jira] [Commented] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117366#comment-16117366
]
Alejandro Fernandez commented on AMBARI-21627:
--
Pushed addendum patch to branch-2.5,
commit 2533644003a58fa3a6909d10ed184eb9d126fe1c
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.addendum.patch, AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21627:
-
Attachment: AMBARI-21627.addendum.patch
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.addendum.patch, AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21627:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5, commit 266deaf1dc0129ee447e9255ed253a16535e6bf5
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21627:
-
Status: Patch Available (was: Open)
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
[
https://issues.apache.org/jira/browse/AMBARI-21627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21627:
-
Attachment: AMBARI-21627.patch
> Cross-stack upgrade from IOP to HDP, ranger audit properties need to be
> deleted
> ---
>
> Key: AMBARI-21627
> URL: https://issues.apache.org/jira/browse/AMBARI-21627
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21627.patch
>
>
> STR:
> * Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
> * Upgrade Ambari to 2.5.2
> * Install HDP 2.6
> * Perform EU to HDP 2.6
> All of the config types like ranger-*-audit.xml have configs that need to be
> deleted that begin with xasecure.audit.destination.db.*
> E.g.,
> {noformat}
> xasecure.audit.destination.db: "true",
> xasecure.audit.destination.db.batch.filespool.dir:
> "/var/log/hbase/audit/db/spool",
> xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
> xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
> xasecure.audit.destination.db.password:
> "SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
> xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21627) Cross-stack upgrade from IOP to HDP, ranger audit properties need to be deleted
Alejandro Fernandez created AMBARI-21627:
Summary: Cross-stack upgrade from IOP to HDP, ranger audit
properties need to be deleted
Key: AMBARI-21627
URL: https://issues.apache.org/jira/browse/AMBARI-21627
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.5.2
STR:
* Install BigInsights 4.2.0 with Ranger, Knox, Kafka, Hive, HBase, YARN, HDFS
* Upgrade Ambari to 2.5.2
* Install HDP 2.6
* Perform EU to HDP 2.6
All of the config types like ranger-*-audit.xml have configs that need to be
deleted that begin with xasecure.audit.destination.db.*
E.g.,
{noformat}
xasecure.audit.destination.db: "true",
xasecure.audit.destination.db.batch.filespool.dir:
"/var/log/hbase/audit/db/spool",
xasecure.audit.destination.db.jdbc.driver: "{{jdbc_driver}}",
xasecure.audit.destination.db.jdbc.url: "{{audit_jdbc_url}}",
xasecure.audit.destination.db.password:
"SECRET:ranger-hbase-audit:3:xasecure.audit.destination.db.password",
xasecure.audit.destination.db.user: "{{xa_audit_db_user}}",
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104006#comment-16104006
]
Alejandro Fernandez commented on AMBARI-21463:
--
Looks like there was an error merging this to trunk, so committed commit
8d3570f8aba559741d4e45da425eda3613c8d405
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch, AMBARI-21463.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21326) Implement CodeCache related configuration change for HBase daemons
[ https://issues.apache.org/jira/browse/AMBARI-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-21326. -- Resolution: Fixed Pushed to branch-2.5, commit 0fa6e2091cbe7e1f2741568fdfb2f244398ba59c trunk, commit ae1369742081df3b99cf3ef678b24afc20b062fb > Implement CodeCache related configuration change for HBase daemons > -- > > Key: AMBARI-21326 > URL: https://issues.apache.org/jira/browse/AMBARI-21326 > Project: Ambari > Issue Type: Task >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Critical > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21326.v1.patch > > > Add -XX:ReservedCodeCacheSize=256m to the regionserver's JVM options in > hbase-env.sh > The details are here > https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21326) Implement CodeCache related configuration change for HBase daemons
[ https://issues.apache.org/jira/browse/AMBARI-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez reassigned AMBARI-21326: Assignee: Ted Yu > Implement CodeCache related configuration change for HBase daemons > -- > > Key: AMBARI-21326 > URL: https://issues.apache.org/jira/browse/AMBARI-21326 > Project: Ambari > Issue Type: Task >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Critical > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21326.v1.patch > > > Add -XX:ReservedCodeCacheSize=256m to the regionserver's JVM options in > hbase-env.sh > The details are here > https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21326) Implement CodeCache related configuration change for HBase daemons
[ https://issues.apache.org/jira/browse/AMBARI-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103985#comment-16103985 ] Alejandro Fernandez commented on AMBARI-21326: -- +1 > Implement CodeCache related configuration change for HBase daemons > -- > > Key: AMBARI-21326 > URL: https://issues.apache.org/jira/browse/AMBARI-21326 > Project: Ambari > Issue Type: Task >Reporter: Ted Yu >Priority: Critical > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21326.v1.patch > > > Add -XX:ReservedCodeCacheSize=256m to the regionserver's JVM options in > hbase-env.sh > The details are here > https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21326) Implement CodeCache related configuration change for HBase daemons
[ https://issues.apache.org/jira/browse/AMBARI-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21326: - Fix Version/s: 2.5.2 trunk > Implement CodeCache related configuration change for HBase daemons > -- > > Key: AMBARI-21326 > URL: https://issues.apache.org/jira/browse/AMBARI-21326 > Project: Ambari > Issue Type: Task >Reporter: Ted Yu >Priority: Critical > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21326.v1.patch > > > Add -XX:ReservedCodeCacheSize=256m to the regionserver's JVM options in > hbase-env.sh > The details are here > https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21326) Implement CodeCache related configuration change for HBase daemons
[
https://issues.apache.org/jira/browse/AMBARI-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103980#comment-16103980
]
Alejandro Fernandez commented on AMBARI-21326:
--
Reviewing the batch, what should happen to existing clusters that are missing
{noformat} -XX:ReservedCodeCacheSize=256m{noformat} in hbase-env content?
The current patch will only affect new clusters.
> Implement CodeCache related configuration change for HBase daemons
> --
>
> Key: AMBARI-21326
> URL: https://issues.apache.org/jira/browse/AMBARI-21326
> Project: Ambari
> Issue Type: Task
>Reporter: Ted Yu
>Priority: Critical
> Attachments: AMBARI-21326.v1.patch
>
>
> Add -XX:ReservedCodeCacheSize=256m to the regionserver's JVM options in
> hbase-env.sh
> The details are here
> https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21554) Cross-stack upgrade, regenerating keytabs after upgrading Ambari fails in Stack Advisor
[
https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21554:
-
Summary: Cross-stack upgrade, regenerating keytabs after upgrading Ambari
fails in Stack Advisor (was: Attempting to make a configuration change to a
IOP-4.2.x cluster will result in a service advisor error)
> Cross-stack upgrade, regenerating keytabs after upgrading Ambari fails in
> Stack Advisor
> ---
>
> Key: AMBARI-21554
> URL: https://issues.apache.org/jira/browse/AMBARI-21554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
> Fix For: 2.5.3
>
>
> STR:
> * Install BigInsights
> * Kerberize the cluster
> * Upgrade Ambari to 2.5.2
> * Regenerate keytabs
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 98,
> in main
> stackAdvisor = instantiateStackAdvisor(stackName, stackVersion,
> parentVersions)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 147,
> in instantiateStackAdvisor
> stack_advisor = imp.load_module('stack_advisor_impl', fp, path, ('.py',
> 'rb', imp.PY_SOURCE))
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/BigInsights/4.0/services/stack_advisor.py",
> line 20, in
> from stack_advisor_25 import *
> ImportError: No module named stack_advisor_25
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21554) Attempting to make a configuration change to a IOP-4.2.x cluster will result in a service advisor error
[
https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21554:
-
Fix Version/s: 2.5.3
> Attempting to make a configuration change to a IOP-4.2.x cluster will result
> in a service advisor error
> ---
>
> Key: AMBARI-21554
> URL: https://issues.apache.org/jira/browse/AMBARI-21554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
> Fix For: 2.5.3
>
>
> STR:
> * Install BigInsights
> * Kerberize the cluster
> * Upgrade Ambari to 2.5.2
> * Regenerate keytabs
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 98,
> in main
> stackAdvisor = instantiateStackAdvisor(stackName, stackVersion,
> parentVersions)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 147,
> in instantiateStackAdvisor
> stack_advisor = imp.load_module('stack_advisor_impl', fp, path, ('.py',
> 'rb', imp.PY_SOURCE))
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/BigInsights/4.0/services/stack_advisor.py",
> line 20, in
> from stack_advisor_25 import *
> ImportError: No module named stack_advisor_25
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21554) Attempting to make a configuration change to a IOP-4.2.x cluster will result in a service advisor error
[
https://issues.apache.org/jira/browse/AMBARI-21554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21554:
-
Description:
STR:
* Install BigInsights
* Kerberize the cluster
* Upgrade Ambari to 2.5.2
* Regenerate keytabs
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 98, in
main
stackAdvisor = instantiateStackAdvisor(stackName, stackVersion,
parentVersions)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 147,
in instantiateStackAdvisor
stack_advisor = imp.load_module('stack_advisor_impl', fp, path, ('.py',
'rb', imp.PY_SOURCE))
File
"/var/lib/ambari-server/resources/scripts/./../stacks/BigInsights/4.0/services/stack_advisor.py",
line 20, in
from stack_advisor_25 import *
ImportError: No module named stack_advisor_25
{code}
was:
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 98, in
main
stackAdvisor = instantiateStackAdvisor(stackName, stackVersion,
parentVersions)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 147,
in instantiateStackAdvisor
stack_advisor = imp.load_module('stack_advisor_impl', fp, path, ('.py',
'rb', imp.PY_SOURCE))
File
"/var/lib/ambari-server/resources/scripts/./../stacks/BigInsights/4.0/services/stack_advisor.py",
line 20, in
from stack_advisor_25 import *
ImportError: No module named stack_advisor_25
> Attempting to make a configuration change to a IOP-4.2.x cluster will result
> in a service advisor error
> ---
>
> Key: AMBARI-21554
> URL: https://issues.apache.org/jira/browse/AMBARI-21554
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Tim Thorpe
>
> STR:
> * Install BigInsights
> * Kerberize the cluster
> * Upgrade Ambari to 2.5.2
> * Regenerate keytabs
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 98,
> in main
> stackAdvisor = instantiateStackAdvisor(stackName, stackVersion,
> parentVersions)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 147,
> in instantiateStackAdvisor
> stack_advisor = imp.load_module('stack_advisor_impl', fp, path, ('.py',
> 'rb', imp.PY_SOURCE))
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/BigInsights/4.0/services/stack_advisor.py",
> line 20, in
> from stack_advisor_25 import *
> ImportError: No module named stack_advisor_25
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5, commit ab05c5fec861bce64234400ea6bb665dc42b7c87
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21573.patch
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Attachment: (was: AMBARI-21573.patch)
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21573.patch
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Attachment: AMBARI-21573.patch
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21573.patch
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Attachment: AMBARI-21573.patch
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21573.patch
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Status: Patch Available (was: Open)
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21573.patch
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21573:
-
Labels: AMBARI-21348 (was: )
> Kafka service failed to start during regenerate keytab after upgrade from
> Biginsights 4.2.5,4.2.0 to HDP 2.6.2
> --
>
> Key: AMBARI-21573
> URL: https://issues.apache.org/jira/browse/AMBARI-21573
> Project: Ambari
> Issue Type: Bug
> Components: express-upgrade
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> *Steps to Reproduce*
> # Install IOP 4.2.5 with Kafka
> # Kerberize the cluster
> # Upgrade Ambari to 2.5.2
> # Register HDP 2.6
> # Remove iop-select
> # Install HDP 2.6.
> # Express Upgrade from BigInsights to HDP
> # Regenerate Keytab
> After regenerate keytab, Kafka will go down.
> The problem is that kafka-broker config type has
> {noformat}
> listeners: "SASL_PLAINTEXT://localhost:6667"
> security.inter.broker.protocol: "SASL_PLAINTEXT"
> {noformat}
> and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21573) Kafka service failed to start during regenerate keytab after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
Alejandro Fernandez created AMBARI-21573:
Summary: Kafka service failed to start during regenerate keytab
after upgrade from Biginsights 4.2.5,4.2.0 to HDP 2.6.2
Key: AMBARI-21573
URL: https://issues.apache.org/jira/browse/AMBARI-21573
Project: Ambari
Issue Type: Bug
Components: express-upgrade
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Blocker
Fix For: 2.5.2
*Steps to Reproduce*
# Install IOP 4.2.5 with Kafka
# Kerberize the cluster
# Upgrade Ambari to 2.5.2
# Register HDP 2.6
# Remove iop-select
# Install HDP 2.6.
# Express Upgrade from BigInsights to HDP
# Regenerate Keytab
After regenerate keytab, Kafka will go down.
The problem is that kafka-broker config type has
{noformat}
listeners: "SASL_PLAINTEXT://localhost:6667"
security.inter.broker.protocol: "SASL_PLAINTEXT"
{noformat}
and it needs to replace "SASL_PLAINTEXT" with "PLAINTEXTSASL"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Addendum pushed,
trunk, eca55998d38f6a8edbb156d84c6cc963c68e85a9
branch-2.5, 0ad9d587d0d7cf88c53ae08c8ce9d7351be4a505
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch, AMBARI-21463.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez reopened AMBARI-21463:
--
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch, AMBARI-21463.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Attachment: AMBARI-21463.patch
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch, AMBARI-21463.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Status: Patch Available (was: Reopened)
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch, AMBARI-21463.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Attachment: AMBARI-21463.addendum.patch
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21463.addendum.patch
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value
[
https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21528:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5, commit d4244f5206feca1bb6001eea6d550494f69e8762
trunk, commit 2a298a3f707c4a3702d0f70e927946540661c916
> Zookeeper server has incorrect memory setting, missing m in Xmx value
> -
>
> Key: AMBARI-21528
> URL: https://issues.apache.org/jira/browse/AMBARI-21528
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21528.patch
>
>
> Repro Steps:
> * Installed BI 4.2.0 cluster on IBM Ambari 2.2.2 with Zookeeper
> * Upgraded Ambari to 2.5.2.0-146
> * Registered HDP 2.6.2.0 repo, installed packages
> * Ran service checks
> * Started Express Upgrade
> Result: _Service Check ZooKeeper_ step failed with {{KeeperErrorCode =
> ConnectionLoss for /zk_smoketest}}
> This was caused by Zookeeper dying immediately during restart:
> {noformat}
> Error occurred during initialization of VM
> Too small initial heap
> {noformat}
> {noformat:title=zookeeper-env.sh before upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/iop/current/zookeeper-server
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024m
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> {noformat:title=zookeeper-env.sh after upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/hdp/current/zookeeper-client
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> Note missing "m" in memory setting.
> zookeeper-env template contains,
> {noformat}
> export SERVER_JVMFLAGS={{zk_server_heapsize}}
> {noformat}
> In this cluster, zookeeper-env contains,
> zk_server_heapsize: "1024"
> While the params_linux.py file has some inconsistencies with appending the
> letter "m".
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024m"))
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
> Instead, it should be,
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024"))
> zk_server_heapsize_value = zk_server_heapsize_value.strip()
> if len(zk_server_heapsize_value) > 0 and not
> zk_server_heapsize_value[-1].isdigit():
> zk_server_heapsize_value = zk_server_heapsize_value + "m"
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value
[
https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21528:
-
Attachment: (was: AMBARI-21528.patch)
> Zookeeper server has incorrect memory setting, missing m in Xmx value
> -
>
> Key: AMBARI-21528
> URL: https://issues.apache.org/jira/browse/AMBARI-21528
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21528.patch
>
>
> Repro Steps:
> * Installed BI 4.2.0 cluster on IBM Ambari 2.2.2 with Zookeeper
> * Upgraded Ambari to 2.5.2.0-146
> * Registered HDP 2.6.2.0 repo, installed packages
> * Ran service checks
> * Started Express Upgrade
> Result: _Service Check ZooKeeper_ step failed with {{KeeperErrorCode =
> ConnectionLoss for /zk_smoketest}}
> This was caused by Zookeeper dying immediately during restart:
> {noformat}
> Error occurred during initialization of VM
> Too small initial heap
> {noformat}
> {noformat:title=zookeeper-env.sh before upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/iop/current/zookeeper-server
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024m
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> {noformat:title=zookeeper-env.sh after upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/hdp/current/zookeeper-client
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> Note missing "m" in memory setting.
> zookeeper-env template contains,
> {noformat}
> export SERVER_JVMFLAGS={{zk_server_heapsize}}
> {noformat}
> In this cluster, zookeeper-env contains,
> zk_server_heapsize: "1024"
> While the params_linux.py file has some inconsistencies with appending the
> letter "m".
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024m"))
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
> Instead, it should be,
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024"))
> zk_server_heapsize_value = zk_server_heapsize_value.strip()
> if len(zk_server_heapsize_value) > 0 and not
> zk_server_heapsize_value[-1].isdigit():
> zk_server_heapsize_value = zk_server_heapsize_value + "m"
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value
[
https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21528:
-
Status: Patch Available (was: Open)
> Zookeeper server has incorrect memory setting, missing m in Xmx value
> -
>
> Key: AMBARI-21528
> URL: https://issues.apache.org/jira/browse/AMBARI-21528
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21528.patch
>
>
> Repro Steps:
> * Installed BI 4.2.0 cluster on IBM Ambari 2.2.2 with Zookeeper
> * Upgraded Ambari to 2.5.2.0-146
> * Registered HDP 2.6.2.0 repo, installed packages
> * Ran service checks
> * Started Express Upgrade
> Result: _Service Check ZooKeeper_ step failed with {{KeeperErrorCode =
> ConnectionLoss for /zk_smoketest}}
> This was caused by Zookeeper dying immediately during restart:
> {noformat}
> Error occurred during initialization of VM
> Too small initial heap
> {noformat}
> {noformat:title=zookeeper-env.sh before upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/iop/current/zookeeper-server
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024m
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> {noformat:title=zookeeper-env.sh after upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/hdp/current/zookeeper-client
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> Note missing "m" in memory setting.
> zookeeper-env template contains,
> {noformat}
> export SERVER_JVMFLAGS={{zk_server_heapsize}}
> {noformat}
> In this cluster, zookeeper-env contains,
> zk_server_heapsize: "1024"
> While the params_linux.py file has some inconsistencies with appending the
> letter "m".
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024m"))
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
> Instead, it should be,
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024"))
> zk_server_heapsize_value = zk_server_heapsize_value.strip()
> if len(zk_server_heapsize_value) > 0 and not
> zk_server_heapsize_value[-1].isdigit():
> zk_server_heapsize_value = zk_server_heapsize_value + "m"
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value
[
https://issues.apache.org/jira/browse/AMBARI-21528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21528:
-
Attachment: AMBARI-21528.patch
> Zookeeper server has incorrect memory setting, missing m in Xmx value
> -
>
> Key: AMBARI-21528
> URL: https://issues.apache.org/jira/browse/AMBARI-21528
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21528.patch
>
>
> Repro Steps:
> * Installed BI 4.2.0 cluster on IBM Ambari 2.2.2 with Zookeeper
> * Upgraded Ambari to 2.5.2.0-146
> * Registered HDP 2.6.2.0 repo, installed packages
> * Ran service checks
> * Started Express Upgrade
> Result: _Service Check ZooKeeper_ step failed with {{KeeperErrorCode =
> ConnectionLoss for /zk_smoketest}}
> This was caused by Zookeeper dying immediately during restart:
> {noformat}
> Error occurred during initialization of VM
> Too small initial heap
> {noformat}
> {noformat:title=zookeeper-env.sh before upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/iop/current/zookeeper-server
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024m
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> {noformat:title=zookeeper-env.sh after upgrade}
> export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
> export ZOOKEEPER_HOME=/usr/hdp/current/zookeeper-client
> export ZOO_LOG_DIR=/var/log/zookeeper
> export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
> export SERVER_JVMFLAGS=-Xmx1024
> export JAVA=$JAVA_HOME/bin/java
> export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
> {noformat}
> Note missing "m" in memory setting.
> zookeeper-env template contains,
> {noformat}
> export SERVER_JVMFLAGS={{zk_server_heapsize}}
> {noformat}
> In this cluster, zookeeper-env contains,
> zk_server_heapsize: "1024"
> While the params_linux.py file has some inconsistencies with appending the
> letter "m".
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024m"))
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
> Instead, it should be,
> {noformat}
> zk_server_heapsize_value =
> str(default('configurations/zookeeper-env/zk_server_heapsize', "1024"))
> zk_server_heapsize_value = zk_server_heapsize_value.strip()
> if len(zk_server_heapsize_value) > 0 and not
> zk_server_heapsize_value[-1].isdigit():
> zk_server_heapsize_value = zk_server_heapsize_value + "m"
> zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21528) Zookeeper server has incorrect memory setting, missing m in Xmx value
Alejandro Fernandez created AMBARI-21528:
Summary: Zookeeper server has incorrect memory setting, missing m
in Xmx value
Key: AMBARI-21528
URL: https://issues.apache.org/jira/browse/AMBARI-21528
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Blocker
Fix For: 2.5.2
Repro Steps:
* Installed BI 4.2.0 cluster on IBM Ambari 2.2.2 with Zookeeper
* Upgraded Ambari to 2.5.2.0-146
* Registered HDP 2.6.2.0 repo, installed packages
* Ran service checks
* Started Express Upgrade
Result: _Service Check ZooKeeper_ step failed with {{KeeperErrorCode =
ConnectionLoss for /zk_smoketest}}
This was caused by Zookeeper dying immediately during restart:
{noformat}
Error occurred during initialization of VM
Too small initial heap
{noformat}
{noformat:title=zookeeper-env.sh before upgrade}
export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
export ZOOKEEPER_HOME=/usr/iop/current/zookeeper-server
export ZOO_LOG_DIR=/var/log/zookeeper
export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
export SERVER_JVMFLAGS=-Xmx1024m
export JAVA=$JAVA_HOME/bin/java
export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
{noformat}
{noformat:title=zookeeper-env.sh after upgrade}
export JAVA_HOME=/usr/jdk64/java-1.8.0-openjdk-1.8.0.77-0.b03.el7_2.x86_64
export ZOOKEEPER_HOME=/usr/hdp/current/zookeeper-client
export ZOO_LOG_DIR=/var/log/zookeeper
export ZOOPIDFILE=/var/run/zookeeper/zookeeper_server.pid
export SERVER_JVMFLAGS=-Xmx1024
export JAVA=$JAVA_HOME/bin/java
export CLASSPATH=$CLASSPATH:/usr/share/zookeeper/*
{noformat}
Note missing "m" in memory setting.
zookeeper-env template contains,
{noformat}
export SERVER_JVMFLAGS={{zk_server_heapsize}}
{noformat}
In this cluster, zookeeper-env contains,
zk_server_heapsize: "1024"
While the params_linux.py file has some inconsistencies with appending the
letter "m".
{noformat}
zk_server_heapsize_value =
str(default('configurations/zookeeper-env/zk_server_heapsize', "1024m"))
zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
{noformat}
Instead, it should be,
{noformat}
zk_server_heapsize_value =
str(default('configurations/zookeeper-env/zk_server_heapsize', "1024"))
zk_server_heapsize_value = zk_server_heapsize_value.strip()
if len(zk_server_heapsize_value) > 0 and not
zk_server_heapsize_value[-1].isdigit():
zk_server_heapsize_value = zk_server_heapsize_value + "m"
zk_server_heapsize = format("-Xmx{zk_server_heapsize_value}")
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21510) Convert calculated value for 'hive.server2.tez.sessions.per.default.queue' to long before setting it.
[ https://issues.apache.org/jira/browse/AMBARI-21510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092276#comment-16092276 ] Alejandro Fernandez commented on AMBARI-21510: -- +1 > Convert calculated value for 'hive.server2.tez.sessions.per.default.queue' to > long before setting it. > - > > Key: AMBARI-21510 > URL: https://issues.apache.org/jira/browse/AMBARI-21510 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21510.patch, Screen Shot 2017-07-18 at 1.38.47 > PM.png > > > In one code flow, calculated value for > *'hive.server2.tez.sessions.per.default.queue*' is not converted it to *long* > and it ends up getting set as *float*. This effects HSI's Hive2/HiveServer2 > alerts. > Fixed the issue by converting calculated value to *long* before setting it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5, commit d8a5bad1b4b67367818646e7b65a2419021bb420 > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: AMBARI-21502.patch > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: (was: AMBARI-21502.patch) > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5, commit 0ed09cd5342cfc4cac0d6061a7b7b9a3cef127c1
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: AMBARI-21502.patch > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Status: Patch Available (was: Open) > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
Alejandro Fernandez created AMBARI-21502: Summary: Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770 Key: AMBARI-21502 URL: https://issues.apache.org/jira/browse/AMBARI-21502 Project: Ambari Issue Type: Bug Components: express-upgrade, stacks Affects Versions: 2.5.2 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Priority: Blocker Fix For: 2.5.2 During cross stack upgrade from BigInsights, if user has not set custom.hive.warehouse.mode in hive-site, as the default value is changed in HDFS from BigInsights default (0770) to HDP default (0777). EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Status: Open (was: Patch Available)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Status: Patch Available (was: Open)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Status: Patch Available (was: Open)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez reassigned AMBARI-21481:
Assignee: Alejandro Fernandez
Affects Version/s: 2.5.2
Fix Version/s: 2.5.2
Component/s: stacks
ambari-server
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
Alejandro Fernandez created AMBARI-21481:
Summary: Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails
on start because config mapping spark2-javaopts-properties is never selected
Key: AMBARI-21481
URL: https://issues.apache.org/jira/browse/AMBARI-21481
Project: Ambari
Issue Type: Bug
Reporter: Alejandro Fernandez
Priority: Blocker
STR:
* Install BigInsights 4.2.5 with Spark2
* Upgrade to Ambari 2.5.2
* Start Ambari, which will fail in the DB consistency check
{code}
2017-07-07 01:07:01,881 ERROR - You have non selected configs:
spark2-javaopts-properties for service SPARK2 from cluster c1!
{code}
Looks like this config is never selected,
{noformat}
ambari=> SELECT sc.service_name, sc.version, sc.user_name,
TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
ccm.selected, ccm.user_name
FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
m.service_config_id
JOIN clusterconfig c ON m.config_id = c.config_id
JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND c.version_tag
= ccm.version_tag
WHERE sc.service_name = 'SPARK2' and c.type_name = 'spark2-javaopts-properties'
ORDER BY sc.version, c.type_name;
service_name | version | user_name| to_timestamp | stack_id |
note| type_version | version_tag |
type_name | stack_id | clusterconfig_created |
clusterconfigmapping_created | selected | user_name
--+-+++--+---+--+-++--++--+--+---
SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3 |
Initial configurations for Spark2 |1 | version1|
spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
20:17:01+00 |0 | admin
SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3 |
|1 | version1|
spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
20:17:01+00 |0 | admin
(2 rows)
{noformat}
This is because the config type has a single config with an empty value, so
perhaps UI never selects it.
{code}
content
Spark2-javaopts-properties
{code}
Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
config type if none are selected.
The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-21463.
--
Resolution: Fixed
Pushed to branch-2.5,
commit d2c6d53f70bcaa6aee789e6d026cc06990acd16c
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Description:
Oozie Server restart failed due to this: Unable to copy
/usr/share/HDP-oozie/ext-2.2.zip because it does not exist
Doesn't look like HDP rpms created this path:
{code}
[root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
-rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
[root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
-rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
/usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
{code}
The ext2js rpm seems to come from IOPUtils:
{code}
[root@sid-test-2 oozie]# yum list | grep extjs
extjs.noarch 2.2_IBM_2-1
@IOP-UTILS-1.3
[root@sid-test-2 oozie]# rpm -qa | grep extjs
extjs-2.2_IBM_2-1.noarch
{code}
We should swap the source from
{noformat}
/usr/share/HDP-oozie/ext-2.2.zip
{noformat}
to
{noformat}
/usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
{noformat}
since the latter does exist.
Also, restarting Oozie Clients during EU is failing because stack_tools.py is
missing the "get_stack_name" function in the __all__ variable.
Lastly, disable showing the BigInsights stack by default in the UI.
was:
Oozie Server restart failed due to this: Unable to copy
/usr/share/HDP-oozie/ext-2.2.zip because it does not exist
Doesn't look like HDP rpms created this path:
{code}
[root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
-rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
[root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
-rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
/usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
{code}
The ext2js rpm seems to come from IOPUtils:
{code}
[root@sid-test-2 oozie]# yum list | grep extjs
extjs.noarch 2.2_IBM_2-1
@IOP-UTILS-1.3
[root@sid-test-2 oozie]# rpm -qa | grep extjs
extjs-2.2_IBM_2-1.noarch
{code}
We should swap the source from
{noformat}
/usr/share/HDP-oozie/ext-2.2.zip
{noformat}
to
{noformat}
/usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
{noformat}
since the latter does exist.
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Summary: Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing
error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights
in UI (was: Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing
error)
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Attachment: AMBARI-21462.patch > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error
Alejandro Fernandez created AMBARI-21463:
Summary: Cross-stack upgrade, Oozie restart fails with ext-2.2.zip
missing error
Key: AMBARI-21463
URL: https://issues.apache.org/jira/browse/AMBARI-21463
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Blocker
Fix For: 2.5.2
Oozie Server restart failed due to this: Unable to copy
/usr/share/HDP-oozie/ext-2.2.zip because it does not exist
Doesn't look like HDP rpms created this path:
{code}
[root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
-rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
[root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
-rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
/usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
{code}
The ext2js rpm seems to come from IOPUtils:
{code}
[root@sid-test-2 oozie]# yum list | grep extjs
extjs.noarch 2.2_IBM_2-1
@IOP-UTILS-1.3
[root@sid-test-2 oozie]# rpm -qa | grep extjs
extjs-2.2_IBM_2-1.noarch
{code}
We should swap the source from
{noformat}
/usr/share/HDP-oozie/ext-2.2.zip
{noformat}
to
{noformat}
/usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
{noformat}
since the latter does exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-21462. -- Resolution: Fixed Pushed to branch-2.5, commit 69e492f288340e797cce62bfd42e677bec958158 > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Attachment: (was: AMBARI-21462.patch) > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Attachment: AMBARI-21462.patch > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Attachment: (was: AMBARI-21462.patch) > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Attachment: AMBARI-21462.patch > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Description: Services to be deleted (in-order of delete after Ambari upgrade) TITAN R4ML SYSTEMML JNBG Fix imports in HBase and the "take_snapshot" function called during EU. was: Services to be deleted (in-order of delete) TITAN R4ML SYSTEMML JNBG Fix imports in HBase and the "take_snapshot" function called during EU. > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21462: - Summary: Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports (was: Remove unnecessary services from BigInsights stack) > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > > Services to be deleted (in-order of delete) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21462) Remove unnecessary services from BigInsights stack
Alejandro Fernandez created AMBARI-21462: Summary: Remove unnecessary services from BigInsights stack Key: AMBARI-21462 URL: https://issues.apache.org/jira/browse/AMBARI-21462 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.2 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Priority: Blocker Fix For: 2.5.2 Services to be deleted (in-order of delete) TITAN R4ML SYSTEMML JNBG Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21455) Remove unnecessary services from BigInsights stack
[
https://issues.apache.org/jira/browse/AMBARI-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21455:
-
Description: Remove services that are not needed in BigInsights stack such
as Titan and SYSTEMML, and all references to JNBG, R4ML. (was: Remove services
that are not needed in BigInsights stack such as Titan and SYSTEMML, and all
references to JNBG, R4ML.
Also, fix a bug when calling force_remove_packages.py in the "Remove IOP
Select" action because the path to "rpm" should not be fully qualified.
{noformat}
ExecutionFailed: Execution of '/usr/bin/rpm -e --nodeps iop-select' returned
127. /var/lib/ambari-agent/ambari-sudo.sh: line 50: /usr/bin/rpm: No such file
or directory
{noformat})
> Remove unnecessary services from BigInsights stack
> --
>
> Key: AMBARI-21455
> URL: https://issues.apache.org/jira/browse/AMBARI-21455
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21455.patch
>
>
> Remove services that are not needed in BigInsights stack such as Titan and
> SYSTEMML, and all references to JNBG, R4ML.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21455) Remove unnecessary services from BigInsights stack
[ https://issues.apache.org/jira/browse/AMBARI-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21455: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5, commit 08f48c1eb85a3763891584b835977809936f3a19 > Remove unnecessary services from BigInsights stack > -- > > Key: AMBARI-21455 > URL: https://issues.apache.org/jira/browse/AMBARI-21455 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Critical > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21455.patch > > > Remove services that are not needed in BigInsights stack such as Titan and > SYSTEMML, and all references to JNBG, R4ML. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21455) Remove unnecessary services from BigInsights stack
[
https://issues.apache.org/jira/browse/AMBARI-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21455:
-
Summary: Remove unnecessary services from BigInsights stack (was: Remove
unnecessary services from BigInsights stack, fix rpm command in Remove IOP
Select action)
> Remove unnecessary services from BigInsights stack
> --
>
> Key: AMBARI-21455
> URL: https://issues.apache.org/jira/browse/AMBARI-21455
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21455.patch
>
>
> Remove services that are not needed in BigInsights stack such as Titan and
> SYSTEMML, and all references to JNBG, R4ML.
> Also, fix a bug when calling force_remove_packages.py in the "Remove IOP
> Select" action because the path to "rpm" should not be fully qualified.
> {noformat}
> ExecutionFailed: Execution of '/usr/bin/rpm -e --nodeps iop-select' returned
> 127. /var/lib/ambari-agent/ambari-sudo.sh: line 50: /usr/bin/rpm: No such
> file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21455) Remove unnecessary services from BigInsights stack, fix rpm command in Remove IOP Select action
[
https://issues.apache.org/jira/browse/AMBARI-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21455:
-
Status: Patch Available (was: Open)
> Remove unnecessary services from BigInsights stack, fix rpm command in Remove
> IOP Select action
> ---
>
> Key: AMBARI-21455
> URL: https://issues.apache.org/jira/browse/AMBARI-21455
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21455.patch
>
>
> Remove services that are not needed in BigInsights stack such as Titan and
> SYSTEMML, and all references to JNBG, R4ML.
> Also, fix a bug when calling force_remove_packages.py in the "Remove IOP
> Select" action because the path to "rpm" should not be fully qualified.
> {noformat}
> ExecutionFailed: Execution of '/usr/bin/rpm -e --nodeps iop-select' returned
> 127. /var/lib/ambari-agent/ambari-sudo.sh: line 50: /usr/bin/rpm: No such
> file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21455) Remove unnecessary services from BigInsights stack, fix rpm command in Remove IOP Select action
[
https://issues.apache.org/jira/browse/AMBARI-21455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21455:
-
Attachment: AMBARI-21455.patch
> Remove unnecessary services from BigInsights stack, fix rpm command in Remove
> IOP Select action
> ---
>
> Key: AMBARI-21455
> URL: https://issues.apache.org/jira/browse/AMBARI-21455
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21455.patch
>
>
> Remove services that are not needed in BigInsights stack such as Titan and
> SYSTEMML, and all references to JNBG, R4ML.
> Also, fix a bug when calling force_remove_packages.py in the "Remove IOP
> Select" action because the path to "rpm" should not be fully qualified.
> {noformat}
> ExecutionFailed: Execution of '/usr/bin/rpm -e --nodeps iop-select' returned
> 127. /var/lib/ambari-agent/ambari-sudo.sh: line 50: /usr/bin/rpm: No such
> file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21455) Remove unnecessary services from BigInsights stack, fix rpm command in Remove IOP Select action
Alejandro Fernandez created AMBARI-21455:
Summary: Remove unnecessary services from BigInsights stack, fix
rpm command in Remove IOP Select action
Key: AMBARI-21455
URL: https://issues.apache.org/jira/browse/AMBARI-21455
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Priority: Critical
Fix For: 2.5.2
Remove services that are not needed in BigInsights stack such as Titan and
SYSTEMML, and all references to JNBG, R4ML.
Also, fix a bug when calling force_remove_packages.py in the "Remove IOP
Select" action because the path to "rpm" should not be fully qualified.
{noformat}
ExecutionFailed: Execution of '/usr/bin/rpm -e --nodeps iop-select' returned
127. /var/lib/ambari-agent/ambari-sudo.sh: line 50: /usr/bin/rpm: No such file
or directory
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
[
https://issues.apache.org/jira/browse/AMBARI-21440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21440:
-
Labels: AMBARI-21348 (was: )
> Cross-stack migration, package supplemental stack in RPM
>
>
> Key: AMBARI-21440
> URL: https://issues.apache.org/jira/browse/AMBARI-21440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Labels: AMBARI-21348
> Fix For: 2.5.2, branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21440.patch
>
>
> When trying to upgrade ambari-server, it fails with error:
> {noformat}
> Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
> data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
> {noformat}
> For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
> For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
[
https://issues.apache.org/jira/browse/AMBARI-21440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-21440.
--
Resolution: Fixed
Pushed to branch-feature-AMBARI-21348
commit 40cd87d82bd2d7a2e282614443bef2186dd48bbd
> Cross-stack migration, package supplemental stack in RPM
>
>
> Key: AMBARI-21440
> URL: https://issues.apache.org/jira/browse/AMBARI-21440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2, branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21440.patch
>
>
> When trying to upgrade ambari-server, it fails with error:
> {noformat}
> Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
> data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
> {noformat}
> For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
> For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
[
https://issues.apache.org/jira/browse/AMBARI-21440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21440:
-
Fix Version/s: branch-feature-AMBARI-21348
> Cross-stack migration, package supplemental stack in RPM
>
>
> Key: AMBARI-21440
> URL: https://issues.apache.org/jira/browse/AMBARI-21440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2, branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21440.patch
>
>
> When trying to upgrade ambari-server, it fails with error:
> {noformat}
> Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
> data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
> {noformat}
> For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
> For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
[
https://issues.apache.org/jira/browse/AMBARI-21440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081360#comment-16081360
]
Alejandro Fernandez commented on AMBARI-21440:
--
Verified the new RPMs,
{noformat}
# Generate the RPM
mvn -B install package rpm:rpm -pl
utility,ambari-views,ambari-metrics/ambari-metrics-common,ambari-server,ambari-agent
-Dmaven.clover.skip=true -Dfindbugs.skip=true -DskipTests=true
-Dstack.distribution=HDP -Dsupplemental.distribution=BigInsights
-Dpython.ver="python >= 2.6" -Drat.ignoreErrors=true
# Verify the contents
rpm -qlp rpm -qlp ambari-server-2.5.1.0-0.x86_64.rpm | grep
"var/lib/ambari-server/resources/stacks/BigInsights"
rpm -qlp rpm -qlp ambari-agent-2.5.1.0-0.x86_64.rpm | grep
"/var/lib/ambari-agent/cache/stacks/BigInsights"
{noformat}
> Cross-stack migration, package supplemental stack in RPM
>
>
> Key: AMBARI-21440
> URL: https://issues.apache.org/jira/browse/AMBARI-21440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21440.patch
>
>
> When trying to upgrade ambari-server, it fails with error:
> {noformat}
> Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
> data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
> {noformat}
> For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
> For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
[
https://issues.apache.org/jira/browse/AMBARI-21440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21440:
-
Attachment: AMBARI-21440.patch
> Cross-stack migration, package supplemental stack in RPM
>
>
> Key: AMBARI-21440
> URL: https://issues.apache.org/jira/browse/AMBARI-21440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21440.patch
>
>
> When trying to upgrade ambari-server, it fails with error:
> {noformat}
> Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
> data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
> {noformat}
> For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
> For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21440) Cross-stack migration, package supplemental stack in RPM
Alejandro Fernandez created AMBARI-21440:
Summary: Cross-stack migration, package supplemental stack in RPM
Key: AMBARI-21440
URL: https://issues.apache.org/jira/browse/AMBARI-21440
Project: Ambari
Issue Type: Bug
Components: ambari-agent, ambari-server
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.5.2
When trying to upgrade ambari-server, it fails with error:
{noformat}
Exception in thread "main" org.apache.ambari.server.AmbariException: Stack
data, Stack BigInsights 4.2.5 is not found in Ambari metainfo
{noformat}
For the server, package /var/lib/ambari-server/resources/stacks/BigInsights
For the agent, package /var/lib/ambari-agent/cache/stacks/BigInsights
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21411) Backend - Run EU/RU PreChecks during a cross-stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21411:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-feature-AMBARI-21348
commit 4e668ca683e4aacd35aed9274662a749b930fa06
> Backend - Run EU/RU PreChecks during a cross-stack upgrade
> --
>
> Key: AMBARI-21411
> URL: https://issues.apache.org/jira/browse/AMBARI-21411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2, branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21411.patch
>
>
> During a cross-stack upgrade, the PreChecks need to be able to run.
> STR:
> * Install BigInsights 4.2.5
> * Upgrade Ambari to 2.5
> * Register bits for HDP 2.6
> * Install bits for HDP 2.6
> * Attempt to run PreChecks
> {noformat}
> curl -u admin:admin -H "X-Requested-By: ambari" -i -X GET
> http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*/repository_version=2.6.1.0-129/upgrade_type=NON_ROLLING/upgrade_pack=nonrolling-upgrade-to-hdp-2.6
> {noformat}
> This returns,
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException:
> Repository version null was not found"
> }
> {noformat}
> because in UpgradeHelper.java it cannot find the upgrade pack.
> The new API will requiring passing in a new argument, e.g.,
> UpgradeChecks/target_stack=HDP-2.6
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21411) Backend - Run EU/RU PreChecks during a cross-stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21411:
-
Fix Version/s: branch-feature-AMBARI-21348
> Backend - Run EU/RU PreChecks during a cross-stack upgrade
> --
>
> Key: AMBARI-21411
> URL: https://issues.apache.org/jira/browse/AMBARI-21411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2, branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21411.patch
>
>
> During a cross-stack upgrade, the PreChecks need to be able to run.
> STR:
> * Install BigInsights 4.2.5
> * Upgrade Ambari to 2.5
> * Register bits for HDP 2.6
> * Install bits for HDP 2.6
> * Attempt to run PreChecks
> {noformat}
> curl -u admin:admin -H "X-Requested-By: ambari" -i -X GET
> http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*/repository_version=2.6.1.0-129/upgrade_type=NON_ROLLING/upgrade_pack=nonrolling-upgrade-to-hdp-2.6
> {noformat}
> This returns,
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException:
> Repository version null was not found"
> }
> {noformat}
> because in UpgradeHelper.java it cannot find the upgrade pack.
> The new API will requiring passing in a new argument, e.g.,
> UpgradeChecks/target_stack=HDP-2.6
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21411) Backend - Run EU/RU PreChecks during a cross-stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21411:
-
Attachment: AMBARI-21411.patch
> Backend - Run EU/RU PreChecks during a cross-stack upgrade
> --
>
> Key: AMBARI-21411
> URL: https://issues.apache.org/jira/browse/AMBARI-21411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21411.patch
>
>
> During a cross-stack upgrade, the PreChecks need to be able to run.
> STR:
> * Install BigInsights 4.2.5
> * Upgrade Ambari to 2.5
> * Register bits for HDP 2.6
> * Install bits for HDP 2.6
> * Attempt to run PreChecks
> {noformat}
> curl -u admin:admin -H "X-Requested-By: ambari" -i -X GET
> http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*/repository_version=2.6.1.0-129/upgrade_type=NON_ROLLING/upgrade_pack=nonrolling-upgrade-to-hdp-2.6
> {noformat}
> This returns,
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException:
> Repository version null was not found"
> }
> {noformat}
> because in UpgradeHelper.java it cannot find the upgrade pack.
> The new API will requiring passing in a new argument, e.g.,
> UpgradeChecks/target_stack=HDP-2.6
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21411) Backend - Run EU/RU PreChecks during a cross-stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21411:
-
Status: Patch Available (was: Open)
> Backend - Run EU/RU PreChecks during a cross-stack upgrade
> --
>
> Key: AMBARI-21411
> URL: https://issues.apache.org/jira/browse/AMBARI-21411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21411.patch
>
>
> During a cross-stack upgrade, the PreChecks need to be able to run.
> STR:
> * Install BigInsights 4.2.5
> * Upgrade Ambari to 2.5
> * Register bits for HDP 2.6
> * Install bits for HDP 2.6
> * Attempt to run PreChecks
> {noformat}
> curl -u admin:admin -H "X-Requested-By: ambari" -i -X GET
> http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*/repository_version=2.6.1.0-129/upgrade_type=NON_ROLLING/upgrade_pack=nonrolling-upgrade-to-hdp-2.6
> {noformat}
> This returns,
> {noformat}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException:
> Repository version null was not found"
> }
> {noformat}
> because in UpgradeHelper.java it cannot find the upgrade pack.
> The new API will requiring passing in a new argument, e.g.,
> UpgradeChecks/target_stack=HDP-2.6
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21411) Backend - Run EU/RU PreChecks during a cross-stack upgrade
Alejandro Fernandez created AMBARI-21411:
Summary: Backend - Run EU/RU PreChecks during a cross-stack upgrade
Key: AMBARI-21411
URL: https://issues.apache.org/jira/browse/AMBARI-21411
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.5.2
During a cross-stack upgrade, the PreChecks need to be able to run.
STR:
* Install BigInsights 4.2.5
* Upgrade Ambari to 2.5
* Register bits for HDP 2.6
* Install bits for HDP 2.6
* Attempt to run PreChecks
{noformat}
curl -u admin:admin -H "X-Requested-By: ambari" -i -X GET
http://localhost:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*/repository_version=2.6.1.0-129/upgrade_type=NON_ROLLING/upgrade_pack=nonrolling-upgrade-to-hdp-2.6
{noformat}
This returns,
{noformat}
{
"status" : 500,
"message" : "org.apache.ambari.server.controller.spi.SystemException:
Repository version null was not found"
}
{noformat}
because in UpgradeHelper.java it cannot find the upgrade pack.
The new API will requiring passing in a new argument, e.g.,
UpgradeChecks/target_stack=HDP-2.6
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21408) Update Custom Action during EU to replace all occurrences of iop with hdp
Alejandro Fernandez created AMBARI-21408: Summary: Update Custom Action during EU to replace all occurrences of iop with hdp Key: AMBARI-21408 URL: https://issues.apache.org/jira/browse/AMBARI-21408 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.2 Reporter: Alejandro Fernandez Fix For: 2.5.2 ChangeStackRootDirectoryAction.java also needs to account for the following changes in any config, "iop/apps" => "hdp/apps" "iop-select" => "hdp-select" "iop.version" => "hdp.version" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21390) Change stack root references in config during cross-stack upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075100#comment-16075100 ] Alejandro Fernandez commented on AMBARI-21390: -- This also needs to account for the following changes in any config, "iop/apps" => "hdp/apps" "iop-select" => "hdp-select" "iop.version" => "hdp.version" > Change stack root references in config during cross-stack upgrade > - > > Key: AMBARI-21390 > URL: https://issues.apache.org/jira/browse/AMBARI-21390 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21390.patch > > > Create a custom upgrade action to change all references to the stack root > directory. It should be executed after the stack has been moved during the > express upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21378) BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie
[ https://issues.apache.org/jira/browse/AMBARI-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21378: - Resolution: Invalid Status: Resolved (was: Patch Available) Already committed in another patch > BigInsights stack changes needed to make Ambari upgrade functional by > repointing Flume and Oozie > > > Key: AMBARI-21378 > URL: https://issues.apache.org/jira/browse/AMBARI-21378 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.2, branch-feature-AMBARI-21348 > > Attachments: AMBARI-21378.patch > > > Ambari Upgrade from BigInsights stack 4.2.5 to Ambari 2.5.next fails if Flume > and Oozie are present since the version it is pointing does not exist in > common-services. > FLUME: Re-point to 1.4.2.0 definition > OOZIE: Re-point to 4.2.0.2.5 definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21378) BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie
[ https://issues.apache.org/jira/browse/AMBARI-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21378: - Fix Version/s: branch-feature-AMBARI-21348 > BigInsights stack changes needed to make Ambari upgrade functional by > repointing Flume and Oozie > > > Key: AMBARI-21378 > URL: https://issues.apache.org/jira/browse/AMBARI-21378 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.2, branch-feature-AMBARI-21348 > > Attachments: AMBARI-21378.patch > > > Ambari Upgrade from BigInsights stack 4.2.5 to Ambari 2.5.next fails if Flume > and Oozie are present since the version it is pointing does not exist in > common-services. > FLUME: Re-point to 1.4.2.0 definition > OOZIE: Re-point to 4.2.0.2.5 definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21378) BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie
[ https://issues.apache.org/jira/browse/AMBARI-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21378: - Attachment: AMBARI-21378.patch > BigInsights stack changes needed to make Ambari upgrade functional by > repointing Flume and Oozie > > > Key: AMBARI-21378 > URL: https://issues.apache.org/jira/browse/AMBARI-21378 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.2 > > Attachments: AMBARI-21378.patch > > > Ambari Upgrade from BigInsights stack 4.2.5 to Ambari 2.5.next fails if Flume > and Oozie are present since the version it is pointing does not exist in > common-services. > FLUME: Re-point to 1.4.2.0 definition > OOZIE: Re-point to 4.2.0.2.5 definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21378) BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie
[ https://issues.apache.org/jira/browse/AMBARI-21378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21378: - Status: Patch Available (was: Open) > BigInsights stack changes needed to make Ambari upgrade functional by > repointing Flume and Oozie > > > Key: AMBARI-21378 > URL: https://issues.apache.org/jira/browse/AMBARI-21378 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.2 > > Attachments: AMBARI-21378.patch > > > Ambari Upgrade from BigInsights stack 4.2.5 to Ambari 2.5.next fails if Flume > and Oozie are present since the version it is pointing does not exist in > common-services. > FLUME: Re-point to 1.4.2.0 definition > OOZIE: Re-point to 4.2.0.2.5 definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21378) BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie
Alejandro Fernandez created AMBARI-21378: Summary: BigInsights stack changes needed to make Ambari upgrade functional by repointing Flume and Oozie Key: AMBARI-21378 URL: https://issues.apache.org/jira/browse/AMBARI-21378 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.2 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Fix For: 2.5.2 Ambari Upgrade from BigInsights stack 4.2.5 to Ambari 2.5.next fails if Flume and Oozie are present since the version it is pointing does not exist in common-services. FLUME: Re-point to 1.4.2.0 definition OOZIE: Re-point to 4.2.0.2.5 definition -- This message was sent by Atlassian JIRA (v6.4.14#64029)
