[jira] [Updated] (AMBARI-24670) Directory creation should be atomic
[ https://issues.apache.org/jira/browse/AMBARI-24670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24670: - Status: Patch Available (was: Open) > Directory creation should be atomic > --- > > Key: AMBARI-24670 > URL: https://issues.apache.org/jira/browse/AMBARI-24670 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Doroszlai, Attila >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24670.patch > > > If parallel execution is enabled on Ambari Agent, concurrent directory > creation may fail with: > {noformat:title=errors-62.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 191, in action_create > sudo.makedir(path, self.resource.mode or 0755) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 121, in makedir > os.mkdir(path) > OSError: [Errno 17] File exists: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > or > {noformat:title=errors-63.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 179, in action_create > path = sudo.readlink(path) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 161, in readlink > return os.readlink(path) > OSError: [Errno 22] Invalid argument: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > The failed tasks need to be retried to succeed, causing delays. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24670) Directory creation should be atomic
[ https://issues.apache.org/jira/browse/AMBARI-24670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24670: - Attachment: AMBARI-24670.patch > Directory creation should be atomic > --- > > Key: AMBARI-24670 > URL: https://issues.apache.org/jira/browse/AMBARI-24670 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Doroszlai, Attila >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24670.patch > > > If parallel execution is enabled on Ambari Agent, concurrent directory > creation may fail with: > {noformat:title=errors-62.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 191, in action_create > sudo.makedir(path, self.resource.mode or 0755) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 121, in makedir > os.mkdir(path) > OSError: [Errno 17] File exists: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > or > {noformat:title=errors-63.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 179, in action_create > path = sudo.readlink(path) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 161, in readlink > return os.readlink(path) > OSError: [Errno 22] Invalid argument: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > The failed tasks need to be retried to succeed, causing delays. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24670) Directory creation should be atomic
[ https://issues.apache.org/jira/browse/AMBARI-24670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24670: Labels: pull-request-available (was: ) > Directory creation should be atomic > --- > > Key: AMBARI-24670 > URL: https://issues.apache.org/jira/browse/AMBARI-24670 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Doroszlai, Attila >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24670.patch > > > If parallel execution is enabled on Ambari Agent, concurrent directory > creation may fail with: > {noformat:title=errors-62.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 191, in action_create > sudo.makedir(path, self.resource.mode or 0755) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 121, in makedir > os.mkdir(path) > OSError: [Errno 17] File exists: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > or > {noformat:title=errors-63.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 179, in action_create > path = sudo.readlink(path) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 161, in readlink > return os.readlink(path) > OSError: [Errno 22] Invalid argument: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > The failed tasks need to be retried to succeed, causing delays. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24689) All component statuses should be re-send on registration
[ https://issues.apache.org/jira/browse/AMBARI-24689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24689: - Status: Patch Available (was: Open) > All component statuses should be re-send on registration > > > Key: AMBARI-24689 > URL: https://issues.apache.org/jira/browse/AMBARI-24689 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24689.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24689) All component statuses should be re-send on registration
Andrew Onischuk created AMBARI-24689: Summary: All component statuses should be re-send on registration Key: AMBARI-24689 URL: https://issues.apache.org/jira/browse/AMBARI-24689 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.8.0 Attachments: AMBARI-24689.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24689) All component statuses should be re-send on registration
[ https://issues.apache.org/jira/browse/AMBARI-24689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24689: - Attachment: AMBARI-24689.patch > All component statuses should be re-send on registration > > > Key: AMBARI-24689 > URL: https://issues.apache.org/jira/browse/AMBARI-24689 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24689.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24689) All component statuses should be re-send on registration
[ https://issues.apache.org/jira/browse/AMBARI-24689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24689: Labels: pull-request-available (was: ) > All component statuses should be re-send on registration > > > Key: AMBARI-24689 > URL: https://issues.apache.org/jira/browse/AMBARI-24689 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24689.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20390: - Affects Version/s: (was: 2.4.0) 2.7.2 2.7.1 2.7.0 > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 50m > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24690) Ambari-server setup-ldap throws an error when the OU has spaces
Attila Magyar created AMBARI-24690: -- Summary: Ambari-server setup-ldap throws an error when the OU has spaces Key: AMBARI-24690 URL: https://issues.apache.org/jira/browse/AMBARI-24690 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.7.0 Reporter: Attila Magyar Assignee: Attila Magyar Ambari-server setup-ldap throws an error when the OU has spaces {code} ambari-server setup-ldap \ --ldap-url=ldap.example.com:636 \ --ldap-secondary-url=ldap.example.com:636 \ --ldap-ssl=true \ --ldap-user-class=person \ --ldap-user-attr=sAMAccountName \ --ldap-group-class=group \ --ldap-group-attr=cn \ --ldap-member-attr=member \ --ldap-dn=distinguishName \ --ldap-base-dn="OU=Group Users,DC=example,DC=com" \ --ldap-referral=follow \ --ldap-bind-anonym=false \ --ldap-manager-dn=b...@example.com \ --ldap-manager-password= \ --ldap-sync-username-collisions-behavior=convert \ --ldap-save-settings {code} error message: {code} Using python /usr/bin/python Usage: ambari-server.py action [options] Options: -h, --helpshow this help message and exit ... --truststore-reconfigure Force to reconfigure TrustStore if exits None Usage: ambari-server.py action [options] ambari-server.py: error: Invalid number of arguments. Entered: 2, required: 1 {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24690) Ambari-server setup-ldap throws an error when the OU has spaces
[ https://issues.apache.org/jira/browse/AMBARI-24690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24690: Labels: pull-request-available (was: ) > Ambari-server setup-ldap throws an error when the OU has spaces > --- > > Key: AMBARI-24690 > URL: https://issues.apache.org/jira/browse/AMBARI-24690 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > > Ambari-server setup-ldap throws an error when the OU has spaces > {code} > ambari-server setup-ldap \ > --ldap-url=ldap.example.com:636 \ > --ldap-secondary-url=ldap.example.com:636 \ > --ldap-ssl=true \ > --ldap-user-class=person \ > --ldap-user-attr=sAMAccountName \ > --ldap-group-class=group \ > --ldap-group-attr=cn \ > --ldap-member-attr=member \ > --ldap-dn=distinguishName \ > --ldap-base-dn="OU=Group Users,DC=example,DC=com" \ > --ldap-referral=follow \ > --ldap-bind-anonym=false \ > --ldap-manager-dn=b...@example.com \ > --ldap-manager-password= \ > --ldap-sync-username-collisions-behavior=convert \ > --ldap-save-settings > {code} > error message: > {code} > Using python /usr/bin/python > Usage: ambari-server.py action [options] > Options: > -h, --helpshow this help message and exit > ... > --truststore-reconfigure > Force to reconfigure TrustStore if exits > None > Usage: ambari-server.py action [options] > ambari-server.py: error: Invalid number of arguments. Entered: 2, required: 1 > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24689) All component statuses should be re-send on registration
[ https://issues.apache.org/jira/browse/AMBARI-24689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628563#comment-16628563 ] Hudson commented on AMBARI-24689: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10136 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10136/]) AMBARI-24689. All component statuses should be re-send on registration (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1aae0de04bb29b9e14603722be18fe8393c4fbd8]) * (edit) ambari-agent/src/test/python/resource_management/TestLinkResource.py * (edit) ambari-agent/src/main/python/ambari_agent/HeartbeatThread.py * (edit) ambari-agent/src/main/python/ambari_agent/ComponentStatusExecutor.py AMBARI-24689. All component statuses should be re-send on registration (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=204e7770ace9b017fb3d6be127d5e3f3938ea01b]) * (edit) ambari-agent/src/test/python/resource_management/TestLinkResource.py > All component statuses should be re-send on registration > > > Key: AMBARI-24689 > URL: https://issues.apache.org/jira/browse/AMBARI-24689 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24689.patch > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24670) Directory creation should be atomic
[ https://issues.apache.org/jira/browse/AMBARI-24670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628564#comment-16628564 ] Hudson commented on AMBARI-24670: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10136 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10136/]) AMBARI-24670. Directory creation sometimes fails with (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=50d955084256a79c2b03599cfc0e3658779057d5]) * (edit) ambari-common/src/main/python/resource_management/core/source.py * (edit) ambari-common/src/main/python/resource_management/core/providers/system.py * (edit) ambari-common/src/main/python/resource_management/core/sudo.py AMBARI-24670. Directory creation sometimes fails with (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e64f3dfb2365cfdfa14db553b0d9b55a3e80f6e2]) * (edit) ambari-agent/src/test/python/resource_management/TestLinkResource.py > Directory creation should be atomic > --- > > Key: AMBARI-24670 > URL: https://issues.apache.org/jira/browse/AMBARI-24670 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Doroszlai, Attila >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24670.patch > > Time Spent: 40m > Remaining Estimate: 0h > > If parallel execution is enabled on Ambari Agent, concurrent directory > creation may fail with: > {noformat:title=errors-62.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 191, in action_create > sudo.makedir(path, self.resource.mode or 0755) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 121, in makedir > os.mkdir(path) > OSError: [Errno 17] File exists: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > or > {noformat:title=errors-63.txt} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 35, in > BeforeAnyHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/hook.py", > line 31, in hook > setup_hadoop_env() > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py", > line 203, in setup_hadoop_env > mode=01777 > File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line > 166, in __init__ > self.env.run() > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", > line 179, in action_create > path = sudo.readlink(path) > File "/usr/lib/ambari-agent/lib/resource_management/core/sudo.py", line > 161, in readlink > return os.readlink(path) > OSError: [Errno 22] Invalid argument: > '/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir' > {noformat} > The failed tasks need to be retried to succeed, causing delays. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24682) Rolling Restarts: Option to specify number of failures per batch
[ https://issues.apache.org/jira/browse/AMBARI-24682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628667#comment-16628667 ] Hudson commented on AMBARI-24682: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10137 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10137/]) [AMBARI-24682] Rolling Restarts: Option to specify number of failures (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=46711f8259e388868ce2a58845e7edc92c199b1a]) * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (add) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog280Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/scheduler/RequestExecutionImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RequestScheduleEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/scheduler/BatchRequestJobTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog280.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/scheduler/BatchSettings.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/scheduler/ExecutionScheduleManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/scheduler/BatchRequestJob.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/RequestExecutionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/scheduler/ExecutionScheduleManagerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestScheduleResourceProvider.java > Rolling Restarts: Option to specify number of failures per batch > > > Key: AMBARI-24682 > URL: https://issues.apache.org/jira/browse/AMBARI-24682 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > User may choose maximum number of failures or specify the number of failures > per batch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24685) Create a Maven Consumable Ambari SPI Client Library
[ https://issues.apache.org/jira/browse/AMBARI-24685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-24685. -- Resolution: Fixed > Create a Maven Consumable Ambari SPI Client Library > --- > > Key: AMBARI-24685 > URL: https://issues.apache.org/jira/browse/AMBARI-24685 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > With management packs and stacks being moved out of Ambari's source control, > framework components such as upgrade checks and upgrade configuration actions > will be to be delivered as part of the 3rd party stack and no long checked > into Apache. > However, Ambari does not expose any kind of API/SPI/library for consumers to > use when creating their own custom classes. A new maven-compatible project > should be created as a home for classes which we expect our 3rd party > consumers to use when creating custom plugins to be delivered in their > stacks. > They can then compile their code against this API/SPI and deliver a JAR which > can be discovered and loaded by Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24651) Add cluster and stack settings properties to agent STOMP updates
[ https://issues.apache.org/jira/browse/AMBARI-24651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24651: Labels: pull-request-available (was: ) > Add cluster and stack settings properties to agent STOMP updates > > > Key: AMBARI-24651 > URL: https://issues.apache.org/jira/browse/AMBARI-24651 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Server should post cluster settings and stack settings to agent with STOMP > updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24687) Upgrade Pack Should Allow Source Information
[ https://issues.apache.org/jira/browse/AMBARI-24687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24687. Resolution: Fixed > Upgrade Pack Should Allow Source Information > > > Key: AMBARI-24687 > URL: https://issues.apache.org/jira/browse/AMBARI-24687 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Allow Upgrade Packs to specify {{source}} information in addition to > {{target}} (for backward compatibility) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24669) Component status can stuck in starting/stopping status on heartbeat lost
[ https://issues.apache.org/jira/browse/AMBARI-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24669: Labels: pull-request-available (was: ) > Component status can stuck in starting/stopping status on heartbeat lost > > > Key: AMBARI-24669 > URL: https://issues.apache.org/jira/browse/AMBARI-24669 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > > Now server sets components statuses to UNKNOWN and saves last actual state on > heartbeat lost. After agent re-registering server restores saved state, but > in case "in progress" state request is already aborted and agent status > updates can not be applied. Agent should always send component statuses after > registering, not only on status changes. Also last actual state logic should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
Nate Cole created AMBARI-24691: -- Summary: Refactor Upgrade Classes to Proper Packages Key: AMBARI-24691 URL: https://issues.apache.org/jira/browse/AMBARI-24691 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole With SPI changes, key upgrade classes should move to the correct package to separate definition from orchestration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
[ https://issues.apache.org/jira/browse/AMBARI-24691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24691: Labels: pull-request-available (was: ) > Refactor Upgrade Classes to Proper Packages > --- > > Key: AMBARI-24691 > URL: https://issues.apache.org/jira/browse/AMBARI-24691 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > > With SPI changes, key upgrade classes should move to the correct package to > separate definition from orchestration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24687) Upgrade Pack Should Allow Source Information
[ https://issues.apache.org/jira/browse/AMBARI-24687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628915#comment-16628915 ] Hudson commented on AMBARI-24687: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10146 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10146/]) [AMBARI-24687] Upgrade Pack Should Allow Source Information (#2375) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=3a5177f1c11e980f752ec7444eb98d24d178e1f6]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/UpgradePack.java * (add) ambari-server/src/test/resources/stacks/HDP/2.2.0/upgrades/upgrade_with_source.xml * (edit) ambari-server/src/main/resources/upgrade-pack.xsd > Upgrade Pack Should Allow Source Information > > > Key: AMBARI-24687 > URL: https://issues.apache.org/jira/browse/AMBARI-24687 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Allow Upgrade Packs to specify {{source}} information in addition to > {{target}} (for backward compatibility) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24685) Create a Maven Consumable Ambari SPI Client Library
[ https://issues.apache.org/jira/browse/AMBARI-24685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628916#comment-16628916 ] Hudson commented on AMBARI-24685: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10146 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10146/]) [AMBARI-24685] - Create a Maven Consumable Ambari SPI Client Library (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ec097f6563b85b49e06c4d41053e101d2c6c8656]) * (add) ambari-server-spi/pom.xml * (add) ambari-server-spi/src/main/java/org/apache/ambari/annotations/UpgradeCheck.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckResult.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/AmbariException.java * (edit) ambari-server/pom.xml * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckGroup.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckStatus.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/server/AmbariException.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckType.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/RepositoryType.java * (add) ambari-server-spi/src/test/java/org/apache/ambari/spi/upgrade/RepositoryTypeTest.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/CheckQualification.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheckRequest.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/CheckDescription.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/package-info.java * (edit) pom.xml * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheck.java * (add) ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeType.java > Create a Maven Consumable Ambari SPI Client Library > --- > > Key: AMBARI-24685 > URL: https://issues.apache.org/jira/browse/AMBARI-24685 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > With management packs and stacks being moved out of Ambari's source control, > framework components such as upgrade checks and upgrade configuration actions > will be to be delivered as part of the 3rd party stack and no long checked > into Apache. > However, Ambari does not expose any kind of API/SPI/library for consumers to > use when creating their own custom classes. A new maven-compatible project > should be created as a home for classes which we expect our 3rd party > consumers to use when creating custom plugins to be delivered in their > stacks. > They can then compile their code against this API/SPI and deliver a JAR which > can be discovered and loaded by Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24690) Ambari-server setup-ldap throws an error when the OU has spaces
[ https://issues.apache.org/jira/browse/AMBARI-24690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628917#comment-16628917 ] Hudson commented on AMBARI-24690: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10146 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10146/]) AMBARI-24690. Ambari-server setup-ldap throws an error when the OU has (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1bc2c69747b9c8be6cfb22d4325d4014a1452970]) * (edit) ambari-server/sbin/ambari-server > Ambari-server setup-ldap throws an error when the OU has spaces > --- > > Key: AMBARI-24690 > URL: https://issues.apache.org/jira/browse/AMBARI-24690 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Ambari-server setup-ldap throws an error when the OU has spaces > {code} > ambari-server setup-ldap \ > --ldap-url=ldap.example.com:636 \ > --ldap-secondary-url=ldap.example.com:636 \ > --ldap-ssl=true \ > --ldap-user-class=person \ > --ldap-user-attr=sAMAccountName \ > --ldap-group-class=group \ > --ldap-group-attr=cn \ > --ldap-member-attr=member \ > --ldap-dn=distinguishName \ > --ldap-base-dn="OU=Group Users,DC=example,DC=com" \ > --ldap-referral=follow \ > --ldap-bind-anonym=false \ > --ldap-manager-dn=b...@example.com \ > --ldap-manager-password= \ > --ldap-sync-username-collisions-behavior=convert \ > --ldap-save-settings > {code} > error message: > {code} > Using python /usr/bin/python > Usage: ambari-server.py action [options] > Options: > -h, --helpshow this help message and exit > ... > --truststore-reconfigure > Force to reconfigure TrustStore if exits > None > Usage: ambari-server.py action [options] > ambari-server.py: error: Invalid number of arguments. Entered: 2, required: 1 > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24684) Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition
[ https://issues.apache.org/jira/browse/AMBARI-24684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24684. -- Resolution: Fixed Committed to branch 2.7 > Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition > > > Key: AMBARI-24684 > URL: https://issues.apache.org/jira/browse/AMBARI-24684 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition > Found this issue with public bits for Ambari-2.7.1 > On ui install -> select version page, select HDP-3.0.1.0 (Default Version > Definition) from the drop down > All the repository urls are still pointing to HDP-3.0.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24692) JDK 11 support for Log Search
Olivér Szabó created AMBARI-24692: - Summary: JDK 11 support for Log Search Key: AMBARI-24692 URL: https://issues.apache.org/jira/browse/AMBARI-24692 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
[ https://issues.apache.org/jira/browse/AMBARI-24691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24691. Resolution: Fixed > Refactor Upgrade Classes to Proper Packages > --- > > Key: AMBARI-24691 > URL: https://issues.apache.org/jira/browse/AMBARI-24691 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > With SPI changes, key upgrade classes should move to the correct package to > separate definition from orchestration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
[ https://issues.apache.org/jira/browse/AMBARI-24691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629175#comment-16629175 ] Hudson commented on AMBARI-24691: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10147 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10147/]) [AMBARI-24691] Refactor Upgrade Classes to Proper Packages (#2386) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b145740dced09143d6cbeae5c52a8ec99a30f234]) * (add) ambari-server/src/test/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeHelperTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureFunction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveDynamicServiceDiscoveryCheck.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveNotRollingWarning.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/ExecuteStage.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/HostMaintenanceModeCheck.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TransferCoercionType.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/ColocatedGrouping.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/StageWrapperBuilder.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ServicePresenceCheck.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeServiceSummary.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeContextTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServerSideActionTask.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/ParallelScheduler.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/PreviousUpgradeCompletedTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/Direction.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServerActionTask.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentExistsInRepoCheckTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/VersionMismatchCheck.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/RestartGrouping.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesMapReduceDistributedCacheCheckTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/AmbariMetricsHadoopSinkVersionCheckTest.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/UpgradeType.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesTezDistributedCacheCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/OozieConfigCalculation.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/AmbariMetricsHadoopSinkVersionCompatibilityCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeSummaryResourceProviderTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/RestartTask.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesUpCheck.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/UpgradeFunction.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/CreateAndConfigureTask.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ExecuteTask.java * (add) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeSummary.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StartGrouping.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ExecuteHostType.java
[jira] [Commented] (AMBARI-24684) Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition
[ https://issues.apache.org/jira/browse/AMBARI-24684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629188#comment-16629188 ] Hudson commented on AMBARI-24684: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #335 (See [https://builds.apache.org/job/Ambari-branch-2.7/335/]) AMBARI-24684. Wrong repo urls on UI for HDP-3.0.1.0 Default Version (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=90947893a7c686c5a1feb6feb3e23c4406603355]) * (edit) ambari-web/app/controllers/installer.js > Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition > > > Key: AMBARI-24684 > URL: https://issues.apache.org/jira/browse/AMBARI-24684 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Wrong repo urls on UI for HDP-3.0.1.0 Default Version Definition > Found this issue with public bits for Ambari-2.7.1 > On ui install -> select version page, select HDP-3.0.1.0 (Default Version > Definition) from the drop down > All the repository urls are still pointing to HDP-3.0.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24693) Remove ambari-infra and ambari-logsearch from ambari repository
Olivér Szabó created AMBARI-24693: - Summary: Remove ambari-infra and ambari-logsearch from ambari repository Key: AMBARI-24693 URL: https://issues.apache.org/jira/browse/AMBARI-24693 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-logsearch Affects Versions: 2.7.2 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24678) Config group mapping should allow multiple service instances
[ https://issues.apache.org/jira/browse/AMBARI-24678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári resolved AMBARI-24678. Resolution: Fixed Fix Version/s: 3.0.0 > Config group mapping should allow multiple service instances > > > Key: AMBARI-24678 > URL: https://issues.apache.org/jira/browse/AMBARI-24678 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Fix For: 3.0.0 > > > Unique constraints in {{clusterconfig}} do not allow multiple service > instances: > {noformat:title=clusterconfig} > CONSTRAINT UQ_config_type_tag UNIQUE (cluster_id, type_name, version_tag), > CONSTRAINT UQ_config_type_version UNIQUE (cluster_id, type_name, version)); > {noformat} > Adding {{service_id}} would be trivial, but {{confgroupclusterconfigmapping}} > references the first one in a foreign key: > {noformat:title=confgroupclusterconfigmapping} > CONSTRAINT FK_confg FOREIGN KEY (version_tag, config_type, cluster_id) > REFERENCES clusterconfig (version_tag, type_name, cluster_id)) > {noformat} > I think it should reference {{clusterconfig}} by its surrogate key > ({{config_id}}). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24693) Remove ambari-infra and ambari-logsearch from ambari repository
[ https://issues.apache.org/jira/browse/AMBARI-24693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24693: Labels: pull-request-available (was: ) > Remove ambari-infra and ambari-logsearch from ambari repository > --- > > Key: AMBARI-24693 > URL: https://issues.apache.org/jira/browse/AMBARI-24693 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24694) Redo Add Host wizard
Jason Golieb created AMBARI-24694: - Summary: Redo Add Host wizard Key: AMBARI-24694 URL: https://issues.apache.org/jira/browse/AMBARI-24694 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Add Service wizard needs major revamp to work with v3.0 mpack model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24694) Redo Add Host wizard
[ https://issues.apache.org/jira/browse/AMBARI-24694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb updated AMBARI-24694: -- Description: Add Host wizard needs major revamp to work in v3.0. (was: Add Service wizard needs major revamp to work with v3.0 mpack model.) > Redo Add Host wizard > > > Key: AMBARI-24694 > URL: https://issues.apache.org/jira/browse/AMBARI-24694 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Add Host wizard needs major revamp to work in v3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24695) Remove ambari-metrics from ambari repository.
Aravindan Vijayan created AMBARI-24695: -- Summary: Remove ambari-metrics from ambari repository. Key: AMBARI-24695 URL: https://issues.apache.org/jira/browse/AMBARI-24695 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24692) JDK 11 support for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629259#comment-16629259 ] Olivér Szabó commented on AMBARI-24692: --- see: https://github.com/apache/ambari-logsearch/commit/01162a04d70d9173ede408372bbb14eeddbc3229 > JDK 11 support for Log Search > - > > Key: AMBARI-24692 > URL: https://issues.apache.org/jira/browse/AMBARI-24692 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24622) Allow skipping package operations for LZO on sysprepped hosts
[ https://issues.apache.org/jira/browse/AMBARI-24622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629302#comment-16629302 ] Hudson commented on AMBARI-24622: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #336 (See [https://builds.apache.org/job/Ambari-branch-2.7/336/]) AMBARI-24622. Allow skipping package operations for LZO on sysprepped (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ebc084e74cf10ba14ab7cae86864b988f87b50b5]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/configuration/cluster-env.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/lzo_utils.py > Allow skipping package operations for LZO on sysprepped hosts > - > > Key: AMBARI-24622 > URL: https://issues.apache.org/jira/browse/AMBARI-24622 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > LZO packages may be pre-installed in sysprepped environments, but Ambari > still manages the repo and checks for existence of the packages, which takes > time. The goal of this change is to allow users who pre-install packages to > skip package manager operations for LZO packages, too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24692) JDK 11 support for Log Search
[ https://issues.apache.org/jira/browse/AMBARI-24692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629259#comment-16629259 ] Olivér Szabó edited comment on AMBARI-24692 at 9/26/18 8:29 PM: see: https://github.com/apache/ambari-logsearch/commit/f6468c8fad122d6fe29652ad484d2db4383151dc was (Author: oleewere): see: https://github.com/apache/ambari-logsearch/commit/01162a04d70d9173ede408372bbb14eeddbc3229 > JDK 11 support for Log Search > - > > Key: AMBARI-24692 > URL: https://issues.apache.org/jira/browse/AMBARI-24692 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24695) Remove ambari-metrics from ambari repository.
[ https://issues.apache.org/jira/browse/AMBARI-24695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24695: Labels: pull-request-available (was: ) > Remove ambari-metrics from ambari repository. > - > > Key: AMBARI-24695 > URL: https://issues.apache.org/jira/browse/AMBARI-24695 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24693) Remove ambari-infra and ambari-logsearch from ambari repository
[ https://issues.apache.org/jira/browse/AMBARI-24693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629381#comment-16629381 ] Hudson commented on AMBARI-24693: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10148 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10148/]) AMBARI-24693. Remove ambari-infra and ambari-logsearch from ambari (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1ff788b72617b46757923e059f8809d18c90063c]) * (delete) ambari-logsearch/ambari-logsearch-server/src/main/configsets/history/conf/managed-schema * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/response/NameValueDataListResponse.java * (delete) ambari-infra/.gitignore * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/conf/security/SecurityEnvironment.java * (delete) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/commands/AbstractSolrRetryCommand.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputSocketMarker.java * (delete) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/commands/UnsecureZNodeZkCommand.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/impl/query/ServiceLogLevelCountQueryRequest.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerMapFieldCopy.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/impl/AuditLogRequest.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputLineFilterTest.java * (delete) ambari-logsearch/ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputFileBaseDescriptorImpl.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/ServiceLogsResource.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LogSearchConstants.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/global/SolrServiceLogsState.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/handler/UploadConfigurationHandler.java * (delete) ambari-infra/ambari-infra-solr-client/src/main/java/org/apache/ambari/infra/solr/commands/AbstractRetryCommand.java * (delete) ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/preinst * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/DateRangeParamDefinition.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputHDFSFile.java * (delete) ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/converter/HostLogFilesRequestQueryConverterTest.java * (delete) ambari-logsearch/ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/MapFieldDescriptorImpl.java * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/deleting/DocumentWiperTasklet.java * (delete) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentExporterTest.java * (delete) ambari-logsearch/ambari-logsearch-appender/src/main/java/org/apache/ambari/logsearch/appender/LogsearchRollingFileAppender.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrKerberosConfig.java * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentDestination.java * (delete) ambari-logsearch/ambari-logsearch-it/src/test/java/org/apache/ambari/logsearch/story/LogSearchStoryLocator.java * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/impl/query/HostLogFilesQueryRequest.java * (delete) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/file/checkpoint/util/ResumeLineNumberHelper.java * (delete) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigServerClass1.java * (delete) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigServerClass2.java * (delete) ambari-logsearch/ambari-logsearch-config-solr/pom.xml * (delete) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/request/ClustersParamDefinition.java * (delete) ambari-logsearch/ambari-logsearch-appender/src/test/java/org/a
[jira] [Commented] (AMBARI-24690) Ambari-server setup-ldap throws an error when the OU has spaces
[ https://issues.apache.org/jira/browse/AMBARI-24690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629448#comment-16629448 ] Hudson commented on AMBARI-24690: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #339 (See [https://builds.apache.org/job/Ambari-branch-2.7/339/]) AMBARI-24690. Ambari-server setup-ldap throws an error when the OU has (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=cc7248448f1a27036fc55fb6af35e0a0c5575d86]) * (edit) ambari-server/sbin/ambari-server > Ambari-server setup-ldap throws an error when the OU has spaces > --- > > Key: AMBARI-24690 > URL: https://issues.apache.org/jira/browse/AMBARI-24690 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Ambari-server setup-ldap throws an error when the OU has spaces > {code} > ambari-server setup-ldap \ > --ldap-url=ldap.example.com:636 \ > --ldap-secondary-url=ldap.example.com:636 \ > --ldap-ssl=true \ > --ldap-user-class=person \ > --ldap-user-attr=sAMAccountName \ > --ldap-group-class=group \ > --ldap-group-attr=cn \ > --ldap-member-attr=member \ > --ldap-dn=distinguishName \ > --ldap-base-dn="OU=Group Users,DC=example,DC=com" \ > --ldap-referral=follow \ > --ldap-bind-anonym=false \ > --ldap-manager-dn=b...@example.com \ > --ldap-manager-password= \ > --ldap-sync-username-collisions-behavior=convert \ > --ldap-save-settings > {code} > error message: > {code} > Using python /usr/bin/python > Usage: ambari-server.py action [options] > Options: > -h, --helpshow this help message and exit > ... > --truststore-reconfigure > Force to reconfigure TrustStore if exits > None > Usage: ambari-server.py action [options] > ambari-server.py: error: Invalid number of arguments. Entered: 2, required: 1 > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
Ishan Bhatt created AMBARI-24696: Summary: UI: Options Page to choose Rolling or Express Restart Key: AMBARI-24696 URL: https://issues.apache.org/jira/browse/AMBARI-24696 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Attachments: Screen Shot 2018-09-26 at 3.03.48 PM.png !Screen Shot 2018-09-26 at 3.03.48 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24696: Labels: pull-request-available (was: ) > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.03.48 PM.png > > > !Screen Shot 2018-09-26 at 3.03.48 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Description: (was: !Screen Shot 2018-09-26 at 3.03.48 PM.png!) > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Attachment: (was: Screen Shot 2018-09-26 at 3.03.48 PM.png) > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Attachment: Screen Shot 2018-09-26 at 3.21.27 PM.png > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.21.27 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Description: !Screen Shot 2018-09-26 at 3.21.27 PM.png! > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.21.27 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > !Screen Shot 2018-09-26 at 3.21.27 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24697) [Intermittent] Client installation failures when parallel_execution enabled
Srikanth Janardhan created AMBARI-24697: --- Summary: [Intermittent] Client installation failures when parallel_execution enabled Key: AMBARI-24697 URL: https://issues.apache.org/jira/browse/AMBARI-24697 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.2 Reporter: Srikanth Janardhan Fix For: 2.7.2 Several client installation failing in a baked image setup due to timeout with Ambari-2.7.3.0-6 {code:title=Infra Solr Client Install failed} stderr: Python script has been killed due to timeout after waiting 2400 secs stdout: 2018-09-26 04:30:05,749 - Stack Feature Version Info: Cluster Stack=3.0, Command Stack=None, Command Version=None -> 3.0 2018-09-26 04:30:05,769 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf 2018-09-26 04:30:05,773 - Group['cstm-users'] {} 2018-09-26 04:30:05,776 - Group['cstm-kms'] {} 2018-09-26 04:30:05,777 - Group['cstm-ranger'] {} 2018-09-26 04:30:05,777 - Group['cstm-zeppelin'] {} 2018-09-26 04:30:05,778 - Group['hdfs'] {} 2018-09-26 04:30:05,778 - Group['cstm-livy'] {} 2018-09-26 04:30:05,779 - Group['hadoop'] {} 2018-09-26 04:30:05,779 - Group['cstm-knox'] {} 2018-09-26 04:30:05,779 - Group['cstm-spark'] {} 2018-09-26 04:30:05,782 - User['yarn-ats'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,786 - User['superset'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,790 - User['cstm-hive'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,794 - User['cstm-sqoop'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,797 - User['cstm-yarn'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,801 - User['cstm-tez'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:30:05,805 - User['cstm-storm'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,809 - User['cstm-kafka'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,840 - Adding user User['cstm-kafka'] 2018-09-26 04:30:05,945 - User['cstm-logsearch'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,946 - Adding user User['cstm-logsearch'] 2018-09-26 04:30:06,283 - User['cstm-infra-solr'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:06,284 - Adding user User['cstm-infra-solr'] 2018-09-26 04:30:06,491 - User['cstm-mr'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:06,492 - Adding user User['cstm-mr'] 2018-09-26 04:30:06,732 - User['cstm-zeppelin'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-zeppelin', 'hadoop'], 'uid': None} 2018-09-26 04:30:06,733 - Adding user User['cstm-zeppelin'] 2018-09-26 04:30:07,044 - User['cstm-oozie'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,045 - Adding user User['cstm-oozie'] 2018-09-26 04:30:07,404 - User['cstm-kms'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-kms', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,405 - Adding user User['cstm-kms'] 2018-09-26 04:30:07,660 - User['cstm-ranger'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-ranger', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,665 - User['cstm-ams'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:07,666 - Adding user User['cstm-ams'] 2018-09-26 04:30:07,920 - User['cstm-atlas'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:07,920 - Adding user User['cstm-atlas'] 2018-09-26 04:30:08,060 - User['cstm-knox'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'cstm-knox'], 'uid': None} 2018-09-26 04:30:08,062 - Modifying user cstm-knox 2018-09-26 04:30:08,263 - User['cstm-hbase'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:08,273 - User['cstm-hdfs'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None} 2018-09-26 04:30:08,274 - Adding user User['cstm-hdfs'] 2018-09-26 04:30:08,435 - User['druid'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:08,437 - Modifying user druid 2018-09-26 04:30:08,610 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:3
[jira] [Updated] (AMBARI-24697) [Intermittent] Client installation failures when parallel_execution enabled
[ https://issues.apache.org/jira/browse/AMBARI-24697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24697: Description: Several client installation failing in a baked image setup due to timeout with Ambari-2.7.3.0-6 {code:title=Infra Solr Client Install failed} stderr: Python script has been killed due to timeout after waiting 2400 secs stdout: 2018-09-26 04:30:05,749 - Stack Feature Version Info: Cluster Stack=3.0, Command Stack=None, Command Version=None -> 3.0 2018-09-26 04:30:05,769 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf 2018-09-26 04:30:05,773 - Group['cstm-users'] {} 2018-09-26 04:30:05,776 - Group['cstm-kms'] {} 2018-09-26 04:30:05,777 - Group['cstm-ranger'] {} 2018-09-26 04:30:05,777 - Group['cstm-zeppelin'] {} 2018-09-26 04:30:05,778 - Group['hdfs'] {} 2018-09-26 04:30:05,778 - Group['cstm-livy'] {} 2018-09-26 04:30:05,779 - Group['hadoop'] {} 2018-09-26 04:30:05,779 - Group['cstm-knox'] {} 2018-09-26 04:30:05,779 - Group['cstm-spark'] {} 2018-09-26 04:30:05,782 - User['yarn-ats'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,786 - User['superset'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,790 - User['cstm-hive'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,794 - User['cstm-sqoop'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,797 - User['cstm-yarn'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,801 - User['cstm-tez'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:30:05,805 - User['cstm-storm'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,809 - User['cstm-kafka'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,840 - Adding user User['cstm-kafka'] 2018-09-26 04:30:05,945 - User['cstm-logsearch'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:05,946 - Adding user User['cstm-logsearch'] 2018-09-26 04:30:06,283 - User['cstm-infra-solr'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:06,284 - Adding user User['cstm-infra-solr'] 2018-09-26 04:30:06,491 - User['cstm-mr'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:06,492 - Adding user User['cstm-mr'] 2018-09-26 04:30:06,732 - User['cstm-zeppelin'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-zeppelin', 'hadoop'], 'uid': None} 2018-09-26 04:30:06,733 - Adding user User['cstm-zeppelin'] 2018-09-26 04:30:07,044 - User['cstm-oozie'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,045 - Adding user User['cstm-oozie'] 2018-09-26 04:30:07,404 - User['cstm-kms'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-kms', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,405 - Adding user User['cstm-kms'] 2018-09-26 04:30:07,660 - User['cstm-ranger'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-ranger', 'hadoop'], 'uid': None} 2018-09-26 04:30:07,665 - User['cstm-ams'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:07,666 - Adding user User['cstm-ams'] 2018-09-26 04:30:07,920 - User['cstm-atlas'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:07,920 - Adding user User['cstm-atlas'] 2018-09-26 04:30:08,060 - User['cstm-knox'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'cstm-knox'], 'uid': None} 2018-09-26 04:30:08,062 - Modifying user cstm-knox 2018-09-26 04:30:08,263 - User['cstm-hbase'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:08,273 - User['cstm-hdfs'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None} 2018-09-26 04:30:08,274 - Adding user User['cstm-hdfs'] 2018-09-26 04:30:08,435 - User['druid'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:08,437 - Modifying user druid 2018-09-26 04:30:08,610 - User['ambari-qa'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None} 2018-09-26 04:30:08,619 - User['cstm-zookeeper'] {'gid': 'hadoop', 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None} 2018-09-26 04:30:08,620 - Adding user User['cstm-zookeeper'] 2018-09-26 04:30:08,842 - User['cstm-livy'] {'gid': 'hadoop', 'fetch_no