[jira] [Commented] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653074#comment-16653074 ] ASF GitHub Bot commented on AMBARI-24777: - asfgit commented on issue #7: AMBARI-24777 - Infra Manager: Remove dependencies due to security concerns. URL: https://github.com/apache/ambari-infra/pull/7#issuecomment-430510889 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/10/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653073#comment-16653073 ] ASF GitHub Bot commented on AMBARI-24777: - kasakrisz opened a new pull request #7: AMBARI-24777 - Infra Manager: Remove dependencies due to security concerns. URL: https://github.com/apache/ambari-infra/pull/7 ## What changes were proposed in this pull request? Fix CVE issues ## How was this patch tested? UTs and ITs passed Manually: 1. Start Infra Manager in docker environment 2. Check the scheduled jobs are working 3. Query and Launch jobs using the swagger UI 4. Check job results This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24777) Infra Manager: Remove dependencies due to security concerns.
[ https://issues.apache.org/jira/browse/AMBARI-24777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24777: Labels: pull-request-available (was: ) > Infra Manager: Remove dependencies due to security concerns. > > > Key: AMBARI-24777 > URL: https://issues.apache.org/jira/browse/AMBARI-24777 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >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-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653054#comment-16653054 ] Hudson commented on AMBARI-24781: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10221 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10221/]) AMBARI-24781 - Ambari setup-ldap: change group member default for IPA (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2fa4bf30b0324c3ac844f5a6ec54c82413c54422]) * (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py * (edit) ambari-server/src/main/python/ambari-server.py * (edit) ambari-server/src/test/python/TestAmbariServer.py > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24781: Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24781: Status: Patch Available (was: In Progress) > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24791. -- Resolution: Fixed > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652828#comment-16652828 ] Hudson commented on AMBARI-24791: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #367 (See [https://builds.apache.org/job/Ambari-branch-2.7/367/]) [AMBARI-24791] Node Managers fail to start after RM is moved to a (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c69aa741611bfb5bd23bbf4391f6ad75932750a7]) * (edit) ambari-web/app/controllers/main/admin/highAvailability/resourceManager/step3_controller.js * (edit) ambari-web/app/data/configs/wizards/rm_ha_properties.js * (edit) ambari-web/app/utils/configs/rm_ha_config_initializer.js * (edit) ambari-web/app/utils/configs/move_rm_config_initializer.js > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652666#comment-16652666 ] Hudson commented on AMBARI-24791: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10220/]) [AMBARI-24791] Node Managers fail to start after RM is moved to a (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7110d4d965767e1bc98eb79bb12d1d42f65676d4]) * (edit) ambari-web/app/utils/configs/rm_ha_config_initializer.js * (edit) ambari-web/app/data/configs/wizards/rm_ha_properties.js * (edit) ambari-web/app/utils/configs/move_rm_config_initializer.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/resourceManager/step3_controller.js > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24791: Labels: pull-request-available (was: ) > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
Ishan Bhatt created AMBARI-24791: Summary: Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated Key: AMBARI-24791 URL: https://issues.apache.org/jira/browse/AMBARI-24791 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.7.3 # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a new host for the active RM node and let the move operation complete # Observe the state of Node Managers in Ambari UI *Result* All Node Managers show as down. Observed that one of the configs - 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM node[!Screen Shot 2018-10-11 at 6.20.51 PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24790) Restart Masters for Service Restart
[ https://issues.apache.org/jira/browse/AMBARI-24790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652369#comment-16652369 ] Hudson commented on AMBARI-24790: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10219 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10219/]) [AMBARI-24790] Restart Masters for Service Restart. (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b2bbc8536b2fd5f3f8a211c53f42b46467810229]) * (edit) ambari-web/app/utils/batch_scheduled_requests.js * (edit) ambari-web/app/views/common/service_restart_view.js * (edit) ambari-web/app/controllers/main/service/item.js > Restart Masters for Service Restart > --- > > Key: AMBARI-24790 > URL: https://issues.apache.org/jira/browse/AMBARI-24790 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24747) Add Component to host functionality broken
[ https://issues.apache.org/jira/browse/AMBARI-24747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb resolved AMBARI-24747. --- Resolution: Fixed > Add Component to host functionality broken > -- > > Key: AMBARI-24747 > URL: https://issues.apache.org/jira/browse/AMBARI-24747 > 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 > > Time Spent: 0.5h > Remaining Estimate: 0h > > On the Host view, the Add Component functionality (clicking on the Add button > in the Components section) is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24788) Install wizard config page blank on first load due to async bug
[ https://issues.apache.org/jira/browse/AMBARI-24788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Golieb resolved AMBARI-24788. --- Resolution: Fixed > Install wizard config page blank on first load due to async bug > --- > > Key: AMBARI-24788 > URL: https://issues.apache.org/jira/browse/AMBARI-24788 > 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 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Bug in config loading code causes configuration page of install wizard to be > blank initially. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652283#comment-16652283 ] Hudson commented on AMBARI-24781: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #366 (See [https://builds.apache.org/job/Ambari-branch-2.7/366/]) AMBARI-24781 - Ambari setup-ldap: change group member default for IPA (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=455adaacf29b4b48e027b7280c0733df67403470]) * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py * (edit) ambari-server/src/main/python/ambari-server.py > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24785) Eliminating duplicated sudo calls when copying files in Ambari with non-root configuration
[ https://issues.apache.org/jira/browse/AMBARI-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652240#comment-16652240 ] Hudson commented on AMBARI-24785: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10218 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10218/]) AMBARI-24785. Removed double 'sudo' invocation (#2470) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=42c8385734fc943e8db3f19b208b3a08e0c09e94]) * (edit) ambari-common/src/main/python/resource_management/core/sudo.py > Eliminating duplicated sudo calls when copying files in Ambari with non-root > configuration > -- > > Key: AMBARI-24785 > URL: https://issues.apache.org/jira/browse/AMBARI-24785 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > During NiFi start Ambari invokes > ambari-common/src/main/python/resource_management/core/sudo.copy(src, dest) > (line 306) in case of non-root configuration. Here the command we pass to the > command wrapper within shell.py starts with 'sudo'. However the sudo flag is > also set to True. > As a result we have a double 'sudo' invocation which may cause issues in > ambari with non-root configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652165#comment-16652165 ] Hudson commented on AMBARI-24789: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #13 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/13/]) AMBARI-24789. LogFeeder: fix CVE-2018-11771 - upgrade commons-compress (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=efb573ca9d4770eabaab6915ad26727ac16786f5]) * (edit) ambari-logsearch-logfeeder/pom.xml > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652124#comment-16652124 ] ASF GitHub Bot commented on AMBARI-24789: - oleewere closed pull request #9: AMBARI-24789. LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib URL: https://github.com/apache/ambari-logsearch/pull/9 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/ambari-logsearch-logfeeder/pom.xml b/ambari-logsearch-logfeeder/pom.xml index 8b89ff686c..1f8a20c2a5 100644 --- a/ambari-logsearch-logfeeder/pom.xml +++ b/ambari-logsearch-logfeeder/pom.xml @@ -152,7 +152,7 @@ org.apache.commons commons-compress - 1.16.1 + 1.18 com.fasterxml.jackson.dataformat This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652119#comment-16652119 ] Hudson commented on AMBARI-24789: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #365 (See [https://builds.apache.org/job/Ambari-branch-2.7/365/]) AMBARI-24789. LogFeeder: fix CVE-2018-11771 - upgrade commons-compress (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=337f57ac8f1c3e4073e692818cfbfb5596dff74e]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/pom.xml > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24774) Wrong settings in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-24774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24774:
Labels: pull-request-available (was: )
> Wrong settings in exported blueprint
>
>
> Key: AMBARI-24774
> URL: https://issues.apache.org/jira/browse/AMBARI-24774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> Cluster blueprint export is broken wrt. the {{settings}} section.
> # Only one component per service is included.
> # Default setting value assumed to be {{false}}, ignoring component-level
> stack definition
> STR:
> # Disable "Auto Start" for Metrics Collector, for which it is enabled by
> default per stack definition
> # Enable "Auto Start" for both DataNode and NameNode
> # Export blueprint
> Result:
> {noformat:title=http://$AMBARI_SERVER:8080/api/v1/clusters/TEST?format=blueprint}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "HDFS"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "NAMENODE"
> }
> ]
> }
> {noformat}
> Problem: creating a cluster using the exported blueprint results in different
> settings than the original cluster. "Auto Start" would be disabled for
> DataNode and enabled for Metrics Collector per stack defaults.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24780) Add Hotfix to VDF Release Element
[
https://issues.apache.org/jira/browse/AMBARI-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652099#comment-16652099
]
Hudson commented on AMBARI-24780:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10217 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10217/])
[AMBARI-24780] Add Hotfix to VDF Release Element (#2469) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=26bb2ebc342c9f9b56088280e2f852eb1cfa1fa4])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesUpCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit) ambari-server/src/main/resources/version_definition.xsd
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentsInstallationCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/RepositoryVersionHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeContextTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/StackVersionResponse.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/state/repository/DefaultStackVersion.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackVersionResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/RequiredServicesInRepositoryCheck.java
* (add)
ambari-server-spi/src/main/java/org/apache/ambari/spi/stack/StackReleaseInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/RequiredServicesInRepositoryCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/MockCheckHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/AmbariMetricsHadoopSinkVersionCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/StackMetainfoXml.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/repository/Release.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ClusterCheckTest.java
* (add)
ambari-server-spi/src/main/java/org/apache/ambari/spi/stack/StackReleaseVersion.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeContext.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesMaintenanceModeCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java
> Add Hotfix to VDF Release Element
> -
>
> Key: AMBARI-24780
> URL: https://issues.apache.org/jira/browse/AMBARI-24780
> 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: 1h 20m
> Remaining Estimate: 0h
>
> VDF should allow for an optional element: {{hotfix}} that is separate from
> the build number. In addition, the stack should be flexible enough to supply
> how version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24774) Wrong settings in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-24774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652087#comment-16652087
]
Doroszlai, Attila commented on AMBARI-24774:
During cluster creation a service-level {{recovery_enabled: true}} setting in
the blueprint results in _all_ components of that service not explicitly listed
under {{"component_settings"}} to have "Auto Start" enabled. Similarly,
cluster-level {{recovery_enabled: true}} results in all components having "Auto
Start" enabled.
Exported blueprints, however, have service/cluster-level {{recovery_enabled:
true}} if _any_ component has "Auto Start" enabled. This causes further
discrepancy between original cluster and re-created cluster.
STR:
# Create ZooKeeper + Metrics cluster without any explicit recovery settings
result: "Auto Start" is enabled only for Metrics Collector by default
# Export blueprint
# Create cluster using the exported blueprint
result: "Auto Start" is enabled for every component
> Wrong settings in exported blueprint
>
>
> Key: AMBARI-24774
> URL: https://issues.apache.org/jira/browse/AMBARI-24774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Fix For: 2.8.0
>
>
> Cluster blueprint export is broken wrt. the {{settings}} section.
> # Only one component per service is included.
> # Default setting value assumed to be {{false}}, ignoring component-level
> stack definition
> STR:
> # Disable "Auto Start" for Metrics Collector, for which it is enabled by
> default per stack definition
> # Enable "Auto Start" for both DataNode and NameNode
> # Export blueprint
> Result:
> {noformat:title=http://$AMBARI_SERVER:8080/api/v1/clusters/TEST?format=blueprint}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "HDFS"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "NAMENODE"
> }
> ]
> }
> {noformat}
> Problem: creating a cluster using the exported blueprint results in different
> settings than the original cluster. "Auto Start" would be disabled for
> DataNode and enabled for Metrics Collector per stack defaults.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24780) Add Hotfix to VDF Release Element
[
https://issues.apache.org/jira/browse/AMBARI-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-24780.
Resolution: Fixed
> Add Hotfix to VDF Release Element
> -
>
> Key: AMBARI-24780
> URL: https://issues.apache.org/jira/browse/AMBARI-24780
> 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: 1h 10m
> Remaining Estimate: 0h
>
> VDF should allow for an optional element: {{hotfix}} that is separate from
> the build number. In addition, the stack should be flexible enough to supply
> how version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652063#comment-16652063 ] Hudson commented on AMBARI-24782: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #364 (See [https://builds.apache.org/job/Ambari-branch-2.7/364/]) AMBARI-24782. Introduce support for Ubuntu 18 LTS (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=347c61a71bcab605b1c05f7f95e5704ac27527f9]) * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py * (edit) ambari-agent/src/test/python/resource_management/TestRepositoryResource.py * (edit) ambari-common/src/main/python/ambari_commons/resources/os_family.json * (edit) ambari-server/src/main/resources/version_definition.xsd * (edit) ambari-common/src/main/python/resource_management/libraries/providers/repository.py * (edit) ambari-agent/src/main/package/dependencies.properties > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch, AMBARI-24782.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24790) Restart Masters for Service Restart
[ https://issues.apache.org/jira/browse/AMBARI-24790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24790: Labels: pull-request-available (was: ) > Restart Masters for Service Restart > --- > > Key: AMBARI-24790 > URL: https://issues.apache.org/jira/browse/AMBARI-24790 > 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 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24790) Restart Masters for Service Restart
Ishan Bhatt created AMBARI-24790: Summary: Restart Masters for Service Restart Key: AMBARI-24790 URL: https://issues.apache.org/jira/browse/AMBARI-24790 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652013#comment-16652013
]
Hudson commented on AMBARI-24784:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10215 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10215/])
AMBARI-24784. Ambari-agent cannot register sometimes (aonishuk) (aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=345da1abed7c55b6b26c921a0a2ab6b92b37db8d])
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651989#comment-16651989 ] ASF GitHub Bot commented on AMBARI-24789: - asfgit commented on issue #9: AMBARI-24789. LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib URL: https://github.com/apache/ambari-logsearch/pull/9#issuecomment-430294887 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/14/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651973#comment-16651973 ] ASF GitHub Bot commented on AMBARI-24789: - oleewere opened a new pull request #9: AMBARI-24789. LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib URL: https://github.com/apache/ambari-logsearch/pull/9 # What changes were proposed in this pull request? upgrade commons compress libraries ## How was this patch tested? waiting to UT result This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24768) Load Upgrade Checks Dynamically From Stacks
[
https://issues.apache.org/jira/browse/AMBARI-24768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24768.
--
Resolution: Fixed
> Load Upgrade Checks Dynamically From Stacks
> ---
>
> Key: AMBARI-24768
> URL: https://issues.apache.org/jira/browse/AMBARI-24768
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Stack-provided upgrade checks need to be loaded from a provided JAR when
> Ambari Server starts up. Currently, upgrade checks are loaded synchronously,
> scanning the entire classpath for classes matching {{UpgradeCheck}} in the
> package {{org.apache.ambari.server.checks}}. This can be extremely slow and
> cause Ambari Server to fail to start within a reasonable amount of time. The
> proposed changes for this issue are as follows:
> - Move to an asynchronous model for scanning the classpath for instances of
> {{UpgradeCheck}}
> - Allow stacks to provide their own plugin directory & JAR for loading SPI
> implementations of {{UpgradeCheck}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
[ https://issues.apache.org/jira/browse/AMBARI-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24789: Labels: pull-request-available (was: ) > LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib > > > Key: AMBARI-24789 > URL: https://issues.apache.org/jira/browse/AMBARI-24789 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24789) LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib
Olivér Szabó created AMBARI-24789: - Summary: LogFeeder: fix CVE-2018-11771 - upgrade commons-compress lib Key: AMBARI-24789 URL: https://issues.apache.org/jira/browse/AMBARI-24789 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.1 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24768) Load Upgrade Checks Dynamically From Stacks
[
https://issues.apache.org/jira/browse/AMBARI-24768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651910#comment-16651910
]
Hudson commented on AMBARI-24768:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10214 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10214/])
[AMBARI-24768] - Load Upgrade Checks Dynamically From Stacks (#2451) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6f2622c76d63a49f9bf06cb062b939836a8a96b7])
* (edit) ambari-server/docs/configuration/index.md
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistryProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/StackDirectory.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeHelper.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/checks/UpgradeTypeQualificationTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeTypeQualification.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/UpgradeCheckOrderTest.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/annotations/UpgradeCheckInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/cleanup/ClasspathScannerUtils.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/UpgradePack.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java
* (edit)
ambari-server-spi/src/main/java/org/apache/ambari/spi/upgrade/UpgradeCheck.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/UpgradeCheckRegistry.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/AutoStartDisabledCheckTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/checks/ClusterCheckTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java
> Load Upgrade Checks Dynamically From Stacks
> ---
>
> Key: AMBARI-24768
> URL: https://issues.apache.org/jira/browse/AMBARI-24768
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.8.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Stack-provided upgrade checks need to be loaded from a provided JAR when
> Ambari Server starts up. Currently, upgrade checks are loaded synchronously,
> scanning the entire classpath for classes matching {{UpgradeCheck}} in the
> package {{org.apache.ambari.server.checks}}. This can be extremely slow and
> cause Ambari Server to fail to start within a reasonable amount of time. The
> proposed changes for this issue are as follows:
> - Move to an asynchronous model for scanning the classpath for instances of
> {{UpgradeCheck}}
> - Allow stacks to provide their own plugin directory & JAR for loading SPI
> implementations of {{UpgradeCheck}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24788) Install wizard config page blank on first load due to async bug
[ https://issues.apache.org/jira/browse/AMBARI-24788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24788: Labels: pull-request-available (was: ) > Install wizard config page blank on first load due to async bug > --- > > Key: AMBARI-24788 > URL: https://issues.apache.org/jira/browse/AMBARI-24788 > 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 > > > Bug in config loading code causes configuration page of install wizard to be > blank initially. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24788) Install wizard config page blank on first load due to async bug
Jason Golieb created AMBARI-24788: - Summary: Install wizard config page blank on first load due to async bug Key: AMBARI-24788 URL: https://issues.apache.org/jira/browse/AMBARI-24788 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jason Golieb Assignee: Jason Golieb Fix For: 3.0.0 Bug in config loading code causes configuration page of install wizard to be blank initially. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24714) User aborted task reported as FAILED in Bgoperations
[
https://issues.apache.org/jira/browse/AMBARI-24714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-24714.
---
Resolution: Fixed
> User aborted task reported as FAILED in Bgoperations
>
>
> Key: AMBARI-24714
> URL: https://issues.apache.org/jira/browse/AMBARI-24714
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: abort_bg_operations.py
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> User aborted task reported as FAILED in Bgoperations.
> 1. Install cluster with all services ( Including Druid)
> 2. Click on Stop all services
> 3. When BGoperations window is loaded, click on the abort button for the same
> task
> 4. The operation should be aborted and marked as Aborted with "Aborted by
> user" message in the sub tasks logs
> 5. But instead the operation is marked as failure.
> Failed task is Druid Coordinator Stop
> {code:java}
> "href":
> "https://ctr-e138-1518143905142-466827-01-02.hwx.site:8443/api/v1/clusters/cl1/requests/59/stages/0/tasks/756";,
> "Tasks": {
> "attempt_cnt": 1,
> "cluster_name": "cl1",
> "command": "STOP",
> "command_detail": "DRUID_COORDINATOR STOP",
> "end_time": 1536363316602,
> "error_log": "/var/lib/ambari-agent/data/errors-756.txt",
> "exit_code": 0,
> "host_name": "ctr-e138-1518143905142-466827-01-05.hwx.site",
> "id": 756,
> "ops_display_name": null,
> "output_log": "/var/lib/ambari-agent/data/output-756.txt",
> "request_id": 59,
> "role": "DRUID_COORDINATOR",
> "stage_id": 0,
> "start_time": 1536363307548,
> "status": "FAILED",
> "stderr": "\nCommand aborted. Reason: 'Aborted by user'",
> "stdout": "\nCommand aborted. Reason: 'Aborted by user'\n\nCommand failed
> after 1 tries\n",
> "structured_out": {}
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24672) Regenerating keytabs for HDFS only does not re-create headless keytabs on all hosts where needed
[ https://issues.apache.org/jira/browse/AMBARI-24672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas resolved AMBARI-24672. --- Resolution: Fixed > Regenerating keytabs for HDFS only does not re-create headless keytabs on > all hosts where needed > - > > Key: AMBARI-24672 > URL: https://issues.apache.org/jira/browse/AMBARI-24672 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 3h > Remaining Estimate: 0h > > +*STR*+ > # install a cluster with HDFS and Tez (+other dependecies) > # Kerberize the cluster > # remove the HDFS client from the host where Tez client is installed > # regenerate keytabs for HDFS > +*Actual results*+ > the headless keytab for HDFS has not been regenerated > +*Expected results*+ > the headless keytab is regenerated where it's necessary -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24787) Cover with unit tests wizard step7 views
Aleksandr Kovalenko created AMBARI-24787: Summary: Cover with unit tests wizard step7 views Key: AMBARI-24787 URL: https://issues.apache.org/jira/browse/AMBARI-24787 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24786) Cover common configs views
[ https://issues.apache.org/jira/browse/AMBARI-24786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24786: Labels: pull-request-available (was: ) > Cover common configs views > -- > > Key: AMBARI-24786 > URL: https://issues.apache.org/jira/browse/AMBARI-24786 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24786) Cover common configs views
[ https://issues.apache.org/jira/browse/AMBARI-24786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24786: - Status: Patch Available (was: Open) > Cover common configs views > -- > > Key: AMBARI-24786 > URL: https://issues.apache.org/jira/browse/AMBARI-24786 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24786) Cover common configs views
[ https://issues.apache.org/jira/browse/AMBARI-24786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24786: Assignee: Antonenko Alexander > Cover common configs views > -- > > Key: AMBARI-24786 > URL: https://issues.apache.org/jira/browse/AMBARI-24786 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24786) Cover common configs views
Antonenko Alexander created AMBARI-24786: Summary: Cover common configs views Key: AMBARI-24786 URL: https://issues.apache.org/jira/browse/AMBARI-24786 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24785) Eliminating duplicated sudo calls when copying files in Ambari with non-root configuration
[ https://issues.apache.org/jira/browse/AMBARI-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24785: Labels: pull-request-available (was: ) > Eliminating duplicated sudo calls when copying files in Ambari with non-root > configuration > -- > > Key: AMBARI-24785 > URL: https://issues.apache.org/jira/browse/AMBARI-24785 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > > During NiFi start Ambari invokes > ambari-common/src/main/python/resource_management/core/sudo.copy(src, dest) > (line 306) in case of non-root configuration. Here the command we pass to the > command wrapper within shell.py starts with 'sudo'. However the sudo flag is > also set to True. > As a result we have a double 'sudo' invocation which may cause issues in > ambari with non-root configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24785) Eliminating duplicated sudo calls when copying files in Ambari with non-root configuration
Sandor Molnar created AMBARI-24785: -- Summary: Eliminating duplicated sudo calls when copying files in Ambari with non-root configuration Key: AMBARI-24785 URL: https://issues.apache.org/jira/browse/AMBARI-24785 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Sandor Molnar Assignee: Sandor Molnar Fix For: 2.8.0 During NiFi start Ambari invokes ambari-common/src/main/python/resource_management/core/sudo.copy(src, dest) (line 306) in case of non-root configuration. Here the command we pass to the command wrapper within shell.py starts with 'sudo'. However the sudo flag is also set to True. As a result we have a double 'sudo' invocation which may cause issues in ambari with non-root configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24780) Add Hotfix to VDF Release Element
[
https://issues.apache.org/jira/browse/AMBARI-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24780:
Labels: pull-request-available (was: )
> Add Hotfix to VDF Release Element
> -
>
> Key: AMBARI-24780
> URL: https://issues.apache.org/jira/browse/AMBARI-24780
> 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
>
>
> VDF should allow for an optional element: {{hotfix}} that is separate from
> the build number. In addition, the stack should be flexible enough to supply
> how version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651650#comment-16651650 ] Hudson commented on AMBARI-24782: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10213 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10213/]) AMBARI-24782. Introduce support for Ubuntu 18 LTS (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ecaba72046455efae8ac99a8c8eed723b614e3e9]) * (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py * (edit) ambari-common/src/main/python/resource_management/libraries/providers/repository.py * (edit) ambari-common/src/main/python/ambari_commons/resources/os_family.json * (edit) ambari-agent/src/test/python/resource_management/TestRepositoryResource.py * (add) ambari-common/src/main/python/resource_management/libraries/providers/repository.py.rej * (edit) ambari-server/src/main/resources/version_definition.xsd * (edit) ambari-agent/src/main/package/dependencies.properties > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch, AMBARI-24782.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651389#comment-16651389 ] Krisztian Kasa edited comment on AMBARI-24781 at 10/16/18 1:04 PM: --- * The storing settings in database issue was solved in AMBARI-24516 * Change the default value of "Group member attribute" for IPA to "member" * Add --ldap-type option to choose the default values for missing options in cli mode was (Author: kkasa): * The storing settings in database issue was solved in AMBARI-24516 * Change the default value of "Group member attribute" for IPA to "member" * Add --ldap-type option to choose the default values for missing options in cli mode * The newly added option for "--ldap-sync-disable-endpoint-identification" should be defaulted to "true" to avoid issues with newer jdks. > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24778) Fix CVE issues in ambari server
[ https://issues.apache.org/jira/browse/AMBARI-24778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651593#comment-16651593 ] Hudson commented on AMBARI-24778: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #363 (See [https://builds.apache.org/job/Ambari-branch-2.7/363/]) AMBARI-24778. Removed CVE issues from ambari-server (#2462) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d7f13babdd0893d91d82a691a027d6fbda226ebe]) * (delete) ambari-web/api-docs/lib/jquery-1.8.3.min.js * (edit) ambari-project/pom.xml * (edit) ambari-web/api-docs/index.html * (add) ambari-web/api-docs/lib/jquery-1.9.0.min.js > Fix CVE issues in ambari server > --- > > Key: AMBARI-24778 > URL: https://issues.apache.org/jira/browse/AMBARI-24778 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > The following 3rd party dependencies have to be eliminated/upgraded to a > secure version based on the latest BlackDuck scan: > ||Current version||Upgrade to||CVE issue(s)|| > |org.springframework:spring-web:jar:4.3.17.RELEASE|org.springframework:spring-web:jar:4.3.18.RELEASE > or the latest|CVE-2018-11039, CVE-2018-11040| > |jquery-1.8.3.min.js|1.9.0rc1 or the latest|CVE-2011-4969, CVE-2015-9251, > CVE-2012-6708| > |org.eclipse.jetty:jetty-server:jar:9.4.11.v20180605|9.4.12.v20180830 or the > latest|CVE-2017-9735, CVE-2018-12536| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24784:
Labels: pull-request-available (was: )
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch
>
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24784) Ambari-agent cannot register sometimes
Andrew Onischuk created AMBARI-24784:
Summary: Ambari-agent cannot register sometimes
Key: AMBARI-24784
URL: https://issues.apache.org/jira/browse/AMBARI-24784
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.8.0
Attachments: AMBARI-24784.patch
ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
HeartbeatThread. Re-running the registration
Traceback (most recent call last):
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
95, in run
self.register()
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
163, in register
self.force_component_status_update()
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
173, in force_component_status_update
self.component_status_executor.force_send_component_statuses()
File "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py",
line 206, in force_send_component_statuses
service_name, component_name = service_and_component_name.split("/")
ValueError: need more than 1 value to unpack
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24784:
-
Attachment: AMBARI-24784.patch
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch
>
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24784:
-
Status: Patch Available (was: Open)
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: AMBARI-24784.patch
>
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24677) Directory resource cannot work with symlinks if link target is a relative path
[ https://issues.apache.org/jira/browse/AMBARI-24677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651562#comment-16651562 ] Hudson commented on AMBARI-24677: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10212 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10212/]) AMBARI-24677. Directory resource cannot work with symlinks if link (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=3adfe2e72e5dda0bbfd7e27e6aadd537f3efff3d]) * (edit) ambari-common/src/main/python/resource_management/core/providers/system.py > Directory resource cannot work with symlinks if link target is a relative path > -- > > Key: AMBARI-24677 > URL: https://issues.apache.org/jira/browse/AMBARI-24677 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24677.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Description: remove any dependencies with probable bugs in it. > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 20m > Remaining Estimate: 0h > > remove any dependencies with probable bugs in it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24658) Cluster creation fails with KeyError in get_cluster_host_info method of ClusterTopologyCache.py
[
https://issues.apache.org/jira/browse/AMBARI-24658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-24658.
--
Resolution: Duplicate
> Cluster creation fails with KeyError in get_cluster_host_info method of
> ClusterTopologyCache.py
> ---
>
> Key: AMBARI-24658
> URL: https://issues.apache.org/jira/browse/AMBARI-24658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Siddharth Wagle
>Assignee: Andrew Onischuk
>Priority: Blocker
> Fix For: 2.7.2
>
>
> Cluster creation fails with KeyError in get_cluster_host_info method of
> ClusterTopologyCache.py'
> Here is the stacktrace:
> {code}
> ambari_agent - CustomServiceOrchestrator.py - [4840] - root - ERROR - Caught
> an exception while executing custom service command: 'exceptions.KeyError'>: 7; 7#012Traceback (most recent call last):#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 324, in runCommand#012 command = self.generate_command(command_header)#012
> File "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py",
> line 504, in generate_command#012 command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp)#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in
> get_configuration#012 'clusterHostInfo':
> self.topology_cache.get_cluster_host_info(cluster_id),#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ClusterTopologyCache.py", line 108,
> in get_cluster_host_info#012 hostnames =
> [self.hosts_to_id[cluster_id][host_id].hostName for host_id in
> component_dict.hostIds]#012KeyError: 7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23585) Register VDF failing for AmazonLinux2
[
https://issues.apache.org/jira/browse/AMBARI-23585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-23585:
-
Fix Version/s: 3.0.0
> Register VDF failing for AmazonLinux2
> --
>
> Key: AMBARI-23585
> URL: https://issues.apache.org/jira/browse/AMBARI-23585
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-23585.patch, AMBARI-23585.patch,
> AMBARI-23585.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
>
> -bash-4.2# curl -v -k -u admin:admin -H "X-Requested-By:ambari" -X POST
> http://ctr-e138-1518143905142-226218-01-02.hwx.site:8080/api/v1/version_definitions
> -d '{ "VersionDefinition": { "version_url":
> "http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml";
> } }'
> Note: Unnecessary use of -X or --request, POST is already inferred.
> * Trying 172.27.80.4...
> * TCP_NODELAY set
> * Connected to ctr-e138-1518143905142-226218-01-02.hwx.site
> (172.27.80.4) port 8080 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/v1/version_definitions HTTP/1.1
> > Host: ctr-e138-1518143905142-226218-01-02.hwx.site:8080
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.55.1
> > Accept: */*
> > X-Requested-By:ambari
> > Content-Length: 151
> > Content-Type: application/x-www-form-urlencoded
> >
> * upload completely sent off: 151 out of 151 bytes
> < HTTP/1.1 500 Internal Server Error
> < Date: Fri, 13 Apr 2018 10:09:15 GMT
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < X-Content-Type-Options: nosniff
> < Cache-Control: no-store
> < Pragma: no-cache
> < X-Content-Type-Options: nosniff
> < X-Frame-Options: DENY
> < Set-Cookie:
> AMBARISESSIONID=node018hn2df5vsjqjuo7g1yr9mvno8.node0;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < User: admin
> < Content-Type: text/plain;charset=utf-8
> < Transfer-Encoding: chunked
> <
> {
> "status" : 500,
> "message" : "An internal system exception occurred: Could not load url
> from
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml.
> null"
> * Connection #0 to host ctr-e138-1518143905142-226218-01-02.hwx.site
> left intact
> }-bash-4.2#
> -bash-4.2#
>
> Build Used:
>
>
>
> -bash-4.2# cat /etc/yum.repos.d/ambari.repo
> #VERSION_NUMBER=2.7.0.0-309
> [ambari-2.7.0.0-309]
> name=ambari Version - ambari-2.7.0.0-309
>
> baseurl=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309
> gpgcheck=1
>
> gpgkey=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
> enabled=1
> priority=1
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23585) Register VDF failing for AmazonLinux2
[
https://issues.apache.org/jira/browse/AMBARI-23585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-23585:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Register VDF failing for AmazonLinux2
> --
>
> Key: AMBARI-23585
> URL: https://issues.apache.org/jira/browse/AMBARI-23585
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-23585.patch, AMBARI-23585.patch,
> AMBARI-23585.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
>
> -bash-4.2# curl -v -k -u admin:admin -H "X-Requested-By:ambari" -X POST
> http://ctr-e138-1518143905142-226218-01-02.hwx.site:8080/api/v1/version_definitions
> -d '{ "VersionDefinition": { "version_url":
> "http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml";
> } }'
> Note: Unnecessary use of -X or --request, POST is already inferred.
> * Trying 172.27.80.4...
> * TCP_NODELAY set
> * Connected to ctr-e138-1518143905142-226218-01-02.hwx.site
> (172.27.80.4) port 8080 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/v1/version_definitions HTTP/1.1
> > Host: ctr-e138-1518143905142-226218-01-02.hwx.site:8080
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.55.1
> > Accept: */*
> > X-Requested-By:ambari
> > Content-Length: 151
> > Content-Type: application/x-www-form-urlencoded
> >
> * upload completely sent off: 151 out of 151 bytes
> < HTTP/1.1 500 Internal Server Error
> < Date: Fri, 13 Apr 2018 10:09:15 GMT
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < X-Content-Type-Options: nosniff
> < Cache-Control: no-store
> < Pragma: no-cache
> < X-Content-Type-Options: nosniff
> < X-Frame-Options: DENY
> < Set-Cookie:
> AMBARISESSIONID=node018hn2df5vsjqjuo7g1yr9mvno8.node0;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < User: admin
> < Content-Type: text/plain;charset=utf-8
> < Transfer-Encoding: chunked
> <
> {
> "status" : 500,
> "message" : "An internal system exception occurred: Could not load url
> from
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/amazonlinux2/3.x/BUILDS/3.0.0.0-1189/HDP-3.0.0.0-1189.xml.
> null"
> * Connection #0 to host ctr-e138-1518143905142-226218-01-02.hwx.site
> left intact
> }-bash-4.2#
> -bash-4.2#
>
> Build Used:
>
>
>
> -bash-4.2# cat /etc/yum.repos.d/ambari.repo
> #VERSION_NUMBER=2.7.0.0-309
> [ambari-2.7.0.0-309]
> name=ambari Version - ambari-2.7.0.0-309
>
> baseurl=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309
> gpgcheck=1
>
> gpgkey=http://s3.amazonaws.com/dev.hortonworks.com/ambari/amazonlinux2/2.x/BUILDS/2.7.0.0-309/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
> enabled=1
> priority=1
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24677) Directory resource cannot work with symlinks if link target is a relative path
[ https://issues.apache.org/jira/browse/AMBARI-24677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24677: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Directory resource cannot work with symlinks if link target is a relative path > -- > > Key: AMBARI-24677 > URL: https://issues.apache.org/jira/browse/AMBARI-24677 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24677.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24623) hdfsResource fails to using nameservices for filesystems which does not support that
[ https://issues.apache.org/jira/browse/AMBARI-24623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24623: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > hdfsResource fails to using nameservices for filesystems which does not > support that > > > Key: AMBARI-24623 > URL: https://issues.apache.org/jira/browse/AMBARI-24623 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24623.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Some filesystems does not support nameservices: > > > resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop > --config /usr/hdp/3.0.1.0-179/hadoop/conf jar > /var/lib/ambari-agent/lib/fast-hdfs-resource.jar > /var/lib/ambari-agent/tmp/hdfs_resources_1536226305.38.json' returned 1. > Exception occurred, Reason: abfs://mycluster has invalid authority. > abfs://mycluster has invalid authority. > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.initializeClient(AzureBlobFileSystemStore.java:732) > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.(AzureBlobFileSystemStore.java:129) > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.initialize(AzureBlobFileSystem.java:97) > at > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3354) > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124) > at > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403) > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477) > at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.apache.hadoop.util.RunJar.run(RunJar.java:318) > at org.apache.hadoop.util.RunJar.main(RunJar.java:232) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24758) Ambari-agent takes up too many cpu on perf
[
https://issues.apache.org/jira/browse/AMBARI-24758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24758:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> Ambari-agent takes up too many cpu on perf
> --
>
> Key: AMBARI-24758
> URL: https://issues.apache.org/jira/browse/AMBARI-24758
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: AMBARI-24758.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
>ncalls tottime percall cumtime percall filename:lineno(function)
> 14129 1426.1220.101 1426.1220.101 {time.sleep}
> 10.3370.337 1426.769 1426.769 main.py:358(run_threads)
> 3310.2190.0010.2190.001 {method 'acquire' of
> 'thread.lock' objects}
>110.1810.0160.1810.016 {built-in method poll}
> 10.1080.1080.1080.108 {method 'do_handshake' of
> '_ssl._SSLSocket' objects}
> 141510.0420.0000.0420.000 threading.py:571(isSet)
> 1250.0280.0000.0280.000 {method 'flush' of 'file'
> objects}
> 50780.0270.0000.0520.000 decoder.py:65(py_scanstring)
>150.0200.0010.0200.001 {posix.read}
> 50930.0200.0000.0240.000 {method 'sub' of
> '_sre.SRE_Pattern' objects}
> 10.0190.0190.0190.019 {method 'connect' of
> '_socket.socket' objects}
> 153650.0180.0000.0180.000 {method 'match' of
> '_sre.SRE_Pattern' objects}
> 55424/131310.0160.0000.0570.000
> encoder.py:332(_iterencode_dict)
> 382410.0140.0000.0140.000 {isinstance}
>210.0130.0010.0220.001 collections.py:282(namedtuple)
> 473/50.0120.0000.0730.015 decoder.py:148(JSONObject)
> 50780.0090.0000.0340.000
> encoder.py:43(py_encode_basestring_ascii)
> 50.0060.0010.0700.014 __init__.py:122(dump)
> 132510.0050.0000.0050.000 {method 'write' of 'file'
> objects}
> 70.0040.0010.0040.001
> {ambari_commons.libs.x86_64._posixsubprocess.fork_exec}
> 56380.0040.0000.0040.000 encoder.py:49(replace)
>3167/50.0030.0000.0730.015 scanner.py:27(_scan_once)
> 13353/99090.0030.0000.0300.000
> encoder.py:279(_iterencode_list)
>750.0030.0000.0030.000 {method 'read' of
> '_ssl._SSLSocket' objects}
>3177/80.0030.0000.0080.001 Utils.py:124(make_immutable)
> 131310.0030.0000.0600.000 encoder.py:409(_iterencode)
> 111280.0030.0000.0030.000 {method 'groups' of
> '_sre.SRE_Match' objects}
> 2202/450.0030.0000.0040.000 Utils.py:135(get_mutable_copy)
>474/100.0020.0000.0080.001 Utils.py:170(__init__)
> 2380.0020.0000.0020.000 {time.localtime}
> 1190.0020.0000.0040.000 __init__.py:242(__init__)
> 37590.0020.0000.0020.000 {method 'isalnum' of 'str'
> objects}
> 147520.0020.0000.0020.000 {method 'end' of
> '_sre.SRE_Match' objects}
> 168540.0020.0000.0020.000 {method 'append' of 'list'
> objects}
> 50980.0020.0000.0020.000 {method 'join' of 'unicode'
> objects}
> 2380.0020.0000.0070.000 __init__.py:451(format)
>130.0020.0000.0040.000 metric_alert.py:286(__init__)
> 70.0010.0000.0260.004
> subprocess32.py:1153(_execute_child)
>410.0010.0000.0010.000 {open}
> 6160.0010.0000.0010.000 {method 'format' of 'str'
> objects}
> 2380.0010.0000.0040.000 __init__.py:404(formatTime)
>180.0010.0000.0010.000 {posix.listdir}
> 50.0010.0000.0720.014
> ClusterCache.py:131(persist_cache)
> 40320.0010.0000.0030.000 collections.py:323()
>180.0010.0000.0010.000 {method 'sort' of 'list'
> objects}
>900.0010.0000.0010.000 {built-in method now}
> 2380.0010.0000.0010.000 {time.strftime}
> 1190.0010.0000.0010.000 __init__.py:1215(findCaller)
> 57060.0010.0000.0010.000 {method 'group' of
> '_sre.SRE_Match' objects}
> 2810.0010.0000.0010.000 threading.py:146(acquire)
> 2810.0010.0000.0010.000 threading.py:186(releas
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24614: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24654) Tasks fail on ambari-agent intermittently under cpu load due to race condition in ambari-agent
[
https://issues.apache.org/jira/browse/AMBARI-24654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24654:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.7
> Tasks fail on ambari-agent intermittently under cpu load due to race
> condition in ambari-agent
> --
>
> Key: AMBARI-24654
> URL: https://issues.apache.org/jira/browse/AMBARI-24654
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Attachments: AMBARI-24654.patch, AMBARI-24654.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> INFO 2018-09-13 18:30:15,817 ClusterCache.py:125 - Rewriting cache
> ClusterTopologyCache for cluster 2
> ERROR 2018-09-13 18:30:16,386 CustomServiceOrchestrator.py:456 - Caught
> an exception while executing custom service command: 'exceptions.TypeError'>: 'NoneType' object has no attribute '__getitem__';
> 'NoneType' object has no attribute '__getitem__'
> Traceback (most recent call last):
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 324, in runCommand
> command = self.generate_command(command_header)
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 504, in generate_command
> command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp)
> File "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py",
> line 46, in get_configuration
> 'agentLevelParams': {'hostname':
> self.topology_cache.get_current_host_info(cluster_id)['hostName']},
> TypeError: 'NoneType' object has no attribute '__getitem__'
>
> This was found while perf testing.
> However can occur under any circumstances if ambari-agent node if slow enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24647: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24638) Ambari-agent process memory leak
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > Ambari-agent process memory leak > > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > There was one process which started using memory rapidly at certain point and > grew up to ~27GB of RSS used until eventually we restarted it. Which happened > after a month of running of 10 ambari-agent nodes. > [root@andrew2-1n01 ~]# ps aux | grep ambari_agent > root 39955 0.0 0.0 47580 6024 ?SAug17 0:00 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/AmbariAgent.py start > root 39959 20.4 10.2 31623096 27154348 ? Sl Aug17 7645:55 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/main.py start > Just before the growth in memory usage is seen. This exception pops out: > ERROR 2018-09-11 10:56:59,716 websocket.py:552 - Websocket connection was > closed with an exception > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 549, in run > if not self.once(): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 428, in > once > if not self.process(self.buf[:requested]): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 483, in > process > self.reading_buffer_size = s.parser.send(bytes) or DEFAULT_READING_SIZE > ValueError: generator already executing > This exception is not seen on all other nodes or on this one at any other > period (during 1 month). So I suggest it can be the root cause. > Basically this error means that generator is being used by multiple threads. > So I will upload the fix to thread-lock this place. > This is just a guess solution which might work and might not. No way to test > really. But definitely we should try this. > > This is noticed in ambari-2.7.1.0-73 version as well. -- 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:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
> 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] [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: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > 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] [Updated] (AMBARI-24717) Ambari-agent does for save data hashes correctly
[ https://issues.apache.org/jira/browse/AMBARI-24717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24717: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Ambari-agent does for save data hashes correctly > > > Key: AMBARI-24717 > URL: https://issues.apache.org/jira/browse/AMBARI-24717 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24717.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This causes all the data to be re-send during registration. Which can be very > dramatic for perf clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24757) Grafana start failing on U14 fails with error "AttributeError: 'module' object has no attribute 'PROTOCOL_TLSv1_2'"
[ https://issues.apache.org/jira/browse/AMBARI-24757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24757: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > Grafana start failing on U14 fails with error "AttributeError: 'module' > object has no attribute 'PROTOCOL_TLSv1_2'" > --- > > Key: AMBARI-24757 > URL: https://issues.apache.org/jira/browse/AMBARI-24757 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24757.patch, AMBARI-24757.patch, > AMBARI-24757.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24715) Clean up ambari-agent.log
[ https://issues.apache.org/jira/browse/AMBARI-24715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24715: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Clean up ambari-agent.log > - > > Key: AMBARI-24715 > URL: https://issues.apache.org/jira/browse/AMBARI-24715 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24715.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24661) While registering agent can miss updates from server
[ https://issues.apache.org/jira/browse/AMBARI-24661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24661: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > While registering agent can miss updates from server > > > Key: AMBARI-24661 > URL: https://issues.apache.org/jira/browse/AMBARI-24661 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24661.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24587) HDI Livy2 fails to restart
[
https://issues.apache.org/jira/browse/AMBARI-24587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-24587:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.7
> HDI Livy2 fails to restart
> --
>
> Key: AMBARI-24587
> URL: https://issues.apache.org/jira/browse/AMBARI-24587
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Attachments: AMBARI-24587.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Livy2 restart fails from Ambari due to Ambari could not fetch some Hadoop
> configs?
> StdErr:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 148, in
> LivyServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 62, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 52, in configure
> setup_livy(env, 'server', upgrade_type=upgrade_type, action =
> 'config')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
> line 53, in setup_livy
> params.HdfsResource(None, action="execute")
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 681, in action_execute
> self.get_hdfs_resource_executor().action_execute(self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 164, in action_execute
> logoutput=logoutput,
> 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 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
> --config /usr/hdp/3.0.1.0-175/hadoop/conf jar
> /var/lib/ambari-agent/lib/fast-hdfs-resource.jar
> /var/lib/ambari-agent/tmp/hdfs_resources_1535895647.58.json' returned 1.
> Initializing filesystem uri: hdfs://mycluster
> Creating: Resource [source=null,
> target=wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> type=directory, action=create, owner=livy, group=null, mode=700,
> recursiveChown=false, recursiveChmod=false, changePermissionforParents=false,
> manageIfExists=true] in hdfs://mycluster
> Exception occurred, Reason: Wrong FS:
> wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> expected: hdfs://mycluster
> java.lang.IllegalArgumentException: Wrong FS:
> wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> expected: hdfs://mycluster
> at org.apache.hadoop.fs.FileSy
[jira] [Updated] (AMBARI-24560) Better debugging for agent start failure due to stuck fuser call
[ https://issues.apache.org/jira/browse/AMBARI-24560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24560: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Better debugging for agent start failure due to stuck fuser call > > > Key: AMBARI-24560 > URL: https://issues.apache.org/jira/browse/AMBARI-24560 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-24560.patch > > Time Spent: 20m > Remaining Estimate: 0h > > While debugging with we encountered an issue where call to `fuser 8670/tcp` > it got blocked for minutes > - in fact we did not ever see the agent start and had to comment the call. Two > improvements: > * Need timeout for such calls (lets also research and see why the call may > get stuck). We checked that the port was free. > * Need more debug logging in the initial start up path to help debug what > command is getting stuck - in main.py, and PingPortListener.py lets see if > more debug logging can be added -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24583) Ambari agent status could be reported stale just after execution command thread has finished execution
[ https://issues.apache.org/jira/browse/AMBARI-24583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24583: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.7 > Ambari agent status could be reported stale just after execution command > thread has finished execution > -- > > Key: AMBARI-24583 > URL: https://issues.apache.org/jira/browse/AMBARI-24583 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24583.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24527: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24783: Labels: pull-request-available (was: ) > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24783) Cleanup dependencies in Capacity Scheduler
[ https://issues.apache.org/jira/browse/AMBARI-24783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-24783: --- Summary: Cleanup dependencies in Capacity Scheduler (was: Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler) > Cleanup dependencies in Capacity Scheduler > -- > > Key: AMBARI-24783 > URL: https://issues.apache.org/jira/browse/AMBARI-24783 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Fix For: 2.7.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24783) Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler
Nitiraj Singh Rathore created AMBARI-24783: -- Summary: Remove dependency on org.eclipse.jetty:jetty-http:jar:9.3.19.v20170502 in Capacity Scheduler Key: AMBARI-24783 URL: https://issues.apache.org/jira/browse/AMBARI-24783 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.7.0 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24778) Fix CVE issues in ambari server
[ https://issues.apache.org/jira/browse/AMBARI-24778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Molnar resolved AMBARI-24778. Resolution: Fixed > Fix CVE issues in ambari server > --- > > Key: AMBARI-24778 > URL: https://issues.apache.org/jira/browse/AMBARI-24778 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > The following 3rd party dependencies have to be eliminated/upgraded to a > secure version based on the latest BlackDuck scan: > ||Current version||Upgrade to||CVE issue(s)|| > |org.springframework:spring-web:jar:4.3.17.RELEASE|org.springframework:spring-web:jar:4.3.18.RELEASE > or the latest|CVE-2018-11039, CVE-2018-11040| > |jquery-1.8.3.min.js|1.9.0rc1 or the latest|CVE-2011-4969, CVE-2015-9251, > CVE-2012-6708| > |org.eclipse.jetty:jetty-server:jar:9.4.11.v20180605|9.4.12.v20180830 or the > latest|CVE-2017-9735, CVE-2018-12536| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Attachment: AMBARI-24782.patch > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch, AMBARI-24782.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24782: Labels: pull-request-available (was: ) > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Attachment: AMBARI-24782.patch > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Attachment: AMBARI-24782.patch > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Attachment: AMBARI-24782.patch > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch, AMBARI-24782.patch, > AMBARI-24782.patch, AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Attachment: AMBARI-24782.patch > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
[ https://issues.apache.org/jira/browse/AMBARI-24782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24782: - Status: Patch Available (was: Open) > Introduce support for Ubuntu 18 LTS > --- > > Key: AMBARI-24782 > URL: https://issues.apache.org/jira/browse/AMBARI-24782 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24782.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24782) Introduce support for Ubuntu 18 LTS
Andrew Onischuk created AMBARI-24782: Summary: Introduce support for Ubuntu 18 LTS Key: AMBARI-24782 URL: https://issues.apache.org/jira/browse/AMBARI-24782 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24781: Labels: pull-request-available (was: ) > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651389#comment-16651389 ] Krisztian Kasa commented on AMBARI-24781: - * The storing settings in database issue was solved in AMBARI-24516 * Change the default value of "Group member attribute" for IPA to "member" * Add --ldap-type option to choose the default values for missing options in cli mode * The newly added option for "--ldap-sync-disable-endpoint-identification" should be defaulted to "true" to avoid issues with newer jdks. > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.3 > > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24781) Ambari setup-ldap: change group member default for IPA
[ https://issues.apache.org/jira/browse/AMBARI-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24781: Summary: Ambari setup-ldap: change group member default for IPA (was: Ambari setup-ldap doesn't persist settings) > Ambari setup-ldap: change group member default for IPA > -- > > Key: AMBARI-24781 > URL: https://issues.apache.org/jira/browse/AMBARI-24781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Kat Petre >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.3 > > > The new cli options we introduced in Ambari 2.7.1 seem to be causing some > problems. Here's a few observations from the past couple of days putting > together the Ambari 2.7.1 - IPA security labs. > - Even after encrypting passwords and persisting thekey, the ambari-server > setup-ldap cli doesn't seem to store the previous settings in the database. > - The ldap-type option seemed to cause a lot of grief and confusion for the > cli users. Could we please document its behavior in the cli help menu (and > let's add it to the docs, after we get clarity)? > - The default options for IPA integration aren't quite working. Please see > the IPA lab for the values we have to override to get a working group > resolution (*User object class* and *Group member attribute*) > [https://github.com/HortonworksUniversity/Security_Labs/blob/master/HDP-3.0-IPA.md#4-enable-ldap-for-ambari] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24778) Fix CVE issues in ambari server
[ https://issues.apache.org/jira/browse/AMBARI-24778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651274#comment-16651274 ] Hudson commented on AMBARI-24778: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10211 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10211/]) AMBARI-24778. Removed CVE issues from ambari-server (#2459) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=3b50cb6a1a2cfb2bfc45869d4c9609b3ef87932b]) * (edit) ambari-web/api-docs/index.html * (delete) ambari-web/api-docs/lib/jquery-1.8.3.min.js * (add) ambari-web/api-docs/lib/jquery-1.9.0.min.js * (edit) ambari-project/pom.xml > Fix CVE issues in ambari server > --- > > Key: AMBARI-24778 > URL: https://issues.apache.org/jira/browse/AMBARI-24778 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The following 3rd party dependencies have to be eliminated/upgraded to a > secure version based on the latest BlackDuck scan: > ||Current version||Upgrade to||CVE issue(s)|| > |org.springframework:spring-web:jar:4.3.17.RELEASE|org.springframework:spring-web:jar:4.3.18.RELEASE > or the latest|CVE-2018-11039, CVE-2018-11040| > |jquery-1.8.3.min.js|1.9.0rc1 or the latest|CVE-2011-4969, CVE-2015-9251, > CVE-2012-6708| > |org.eclipse.jetty:jetty-server:jar:9.4.11.v20180605|9.4.12.v20180830 or the > latest|CVE-2017-9735, CVE-2018-12536| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
