[jira] [Commented] (AMBARI-24181) Build failure due to bower version deprecation
[
https://issues.apache.org/jira/browse/AMBARI-24181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522863#comment-16522863
]
Yusaku Sako commented on AMBARI-24181:
--
The test failure above is related to Ambari Server and not this patch.
> Build failure due to bower version deprecation
> --
>
> Key: AMBARI-24181
> URL: https://issues.apache.org/jira/browse/AMBARI-24181
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The build is unable to resolve {{bower}} dependency, with HTTP 502 BAD
> GATEWAY.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24181) Build failure due to bower version deprecation
[
https://issues.apache.org/jira/browse/AMBARI-24181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako resolved AMBARI-24181.
--
Resolution: Fixed
Fix Version/s: (was: trunk)
2.7.0
Committed to trunk.
> Build failure due to bower version deprecation
> --
>
> Key: AMBARI-24181
> URL: https://issues.apache.org/jira/browse/AMBARI-24181
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: trunk
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The build is unable to resolve {{bower}} dependency, with HTTP 502 BAD
> GATEWAY.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24155) Ranger and KMS tab still present in Customize ServicesPage even after going back and deselecting them from Choose ServicesPage
[ https://issues.apache.org/jira/browse/AMBARI-24155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24155: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ranger and KMS tab still present in Customize ServicesPage even after going > back and deselecting them from Choose ServicesPage > -- > > Key: AMBARI-24155 > URL: https://issues.apache.org/jira/browse/AMBARI-24155 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > - Navigate to Customize ServicePage of UI install wizard by selecting all > services from ChooseServicesPage. > - Populate credentials tab > - Switch to Databases tab, Noticed that Ranger and Ranger KMS have multiple > properties to be filled in > - Now go back to Choose Services page and deselect Ranger and Ranger KMS > - Proceed through wizard to reach Customize ServicesPage > - Ranger and KMS sub tabs are still present with errors at Databases tab. > (None of the ranger/KMS credential properties are present in Credential tabs) > - Now even if we go back and choose Ranger and KMS - update all necessary > properties for Ranger - Test Connection is hung with error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24153) Customize Service step issues
[ https://issues.apache.org/jira/browse/AMBARI-24153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24153. -- Resolution: Fixed > Customize Service step issues > - > > Key: AMBARI-24153 > URL: https://issues.apache.org/jira/browse/AMBARI-24153 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-06-19 at 6.38.49 AM.png, Screen Shot > 2018-06-19 at 7.02.25 AM.png, > screencapture-104-196-91-59-8080-2018-06-19-06_36_27 (1).png > > Time Spent: 40m > Remaining Estimate: 0h > > There are some issues in Step 7 of the Installer Wizard > 1. Even if there are some *required* changes in the 'Database' tab it allows > to go to the next step. Next should only be enabled if the required property > has been provided with an input > 2. If there are some CRITICAL errors, the top notification bell should be > 'Red' (similar to what we see if there is an empty required property) > 3. If I click on any of the above critical error properties it takes me to a > wrong page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24154) DB Connectivity Warnings for oozie & hive show up even after tests are passed
[ https://issues.apache.org/jira/browse/AMBARI-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24154. -- Resolution: Fixed > DB Connectivity Warnings for oozie & hive show up even after tests are passed > - > > Key: AMBARI-24154 > URL: https://issues.apache.org/jira/browse/AMBARI-24154 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > During initial installation, if both hive and oozie are configured to use > external databases (and therefore both test connection), the test results > seem to get lost. This causes a warning to appear, even though both tests > have passed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24150: - Fix Version/s: (was: trunk) 2.7.0 > Install wizard stuck at Assign Slaves and Clients page > -- > > Key: AMBARI-24150 > URL: https://issues.apache.org/jira/browse/AMBARI-24150 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24150) Install wizard stuck at Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-24150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24150. -- Resolution: Fixed > Install wizard stuck at Assign Slaves and Clients page > -- > > Key: AMBARI-24150 > URL: https://issues.apache.org/jira/browse/AMBARI-24150 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24000) Fix ambari-web pom.xml (version not updated correctly)
[ https://issues.apache.org/jira/browse/AMBARI-24000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-24000. -- Resolution: Fixed Pushed to trunk > Fix ambari-web pom.xml (version not updated correctly) > -- > > Key: AMBARI-24000 > URL: https://issues.apache.org/jira/browse/AMBARI-24000 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > ambari-web/pom.xml is hardcoding the version to 2.99.99. > This needs to be fixed so that it can be overwritten correctly when mvn > versions:set is run from the top-level directory. Current pom.xml leaves the > Ambari Web version to 2.99.99 even after the command is run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24000) Fix ambari-web pom.xml (version not updated correctly)
[ https://issues.apache.org/jira/browse/AMBARI-24000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24000: - Description: ambari-web/pom.xml is hardcoding the version to 2.99.99. This needs to be fixed so that it can be overwritten correctly when mvn versions:set is run from the top-level directory. Current pom.xml leaves the Ambari Web version to 2.99.99 even after the command is run. was: ambari-web/pom.xml is hardcoding the version to 2.99.99. This needs to be fixed so that it can be overwritten dynamically. > Fix ambari-web pom.xml (version not updated correctly) > -- > > Key: AMBARI-24000 > URL: https://issues.apache.org/jira/browse/AMBARI-24000 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.7.0 > > > ambari-web/pom.xml is hardcoding the version to 2.99.99. > This needs to be fixed so that it can be overwritten correctly when mvn > versions:set is run from the top-level directory. Current pom.xml leaves the > Ambari Web version to 2.99.99 even after the command is run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24000) Fix ambari-web pom.xml (version not updated correctly)
[ https://issues.apache.org/jira/browse/AMBARI-24000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-24000: - Summary: Fix ambari-web pom.xml (version not updated correctly) (was: Fix ambari-web pom.xml) > Fix ambari-web pom.xml (version not updated correctly) > -- > > Key: AMBARI-24000 > URL: https://issues.apache.org/jira/browse/AMBARI-24000 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.7.0 > > > ambari-web/pom.xml is hardcoding the version to 2.99.99. > This needs to be fixed so that it can be overwritten dynamically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24000) Fix ambari-web pom.xml
Yusaku Sako created AMBARI-24000: Summary: Fix ambari-web pom.xml Key: AMBARI-24000 URL: https://issues.apache.org/jira/browse/AMBARI-24000 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Yusaku Sako Assignee: Yusaku Sako Fix For: 2.7.0 ambari-web/pom.xml is hardcoding the version to 2.99.99. This needs to be fixed so that it can be overwritten dynamically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23888) 'Component' option missing in the autofill in include filter
[ https://issues.apache.org/jira/browse/AMBARI-23888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-23888. -- Resolution: Duplicate > 'Component' option missing in the autofill in include filter > - > > Key: AMBARI-23888 > URL: https://issues.apache.org/jira/browse/AMBARI-23888 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Major > Fix For: 2.7.0 > > > 'Component' option missing in the autofill in include filter > STR: > 1. Login to Logsearch portal > 2. Try to type word 'Component' in the include filter text box > 3. User should be displayed with Component autofill option in drop down and > the available component list should be displayed if the user hits enter with > Component keyword > 4. No option 'Component' is displayed and 'Message:Component' filter is > enabled when the user hits enter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23918) [Logsearch UI] 'Component' option missing in the autofill in include filter
[ https://issues.apache.org/jira/browse/AMBARI-23918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23918: - Resolution: Fixed Status: Resolved (was: Patch Available) > [Logsearch UI] 'Component' option missing in the autofill in include filter > > > Key: AMBARI-23918 > URL: https://issues.apache.org/jira/browse/AMBARI-23918 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 2h > Time Spent: 2.5h > Remaining Estimate: 0h > > 'Component' option missing in the autofill in include filter > STR: > 1. Login to Logsearch portal > 2. Try to type word 'Component' in the include filter text box > 3. User should be displayed with Component autofill option in drop down and > the available component list should be displayed if the user hits enter with > Component keyword > 4. No option 'Component' is displayed and 'Message:Component' filter is > enabled when the user hits enter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23897) Log Search UI: login with invalid password – no error message is displayed
[ https://issues.apache.org/jira/browse/AMBARI-23897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23897: - Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search UI: login with invalid password – no error message is displayed > -- > > Key: AMBARI-23897 > URL: https://issues.apache.org/jira/browse/AMBARI-23897 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 24h > Time Spent: 1h 10m > Remaining Estimate: 24h > > There is no error message when the user uses invalid auth credentials. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23885) [Logsearch UI] Rows per page drop down not working as expected in the log table
[ https://issues.apache.org/jira/browse/AMBARI-23885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-23885. -- Resolution: Duplicate > [Logsearch UI] Rows per page drop down not working as expected in the log > table > --- > > Key: AMBARI-23885 > URL: https://issues.apache.org/jira/browse/AMBARI-23885 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Major > Fix For: 2.7.0 > > > [Logsearch UI] Logs per page drop down not working as expected in the log > table. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. From the log table, click on Rows per page and select 100 > 4. 100 or the maximum number (If lesser than 100) of logs should be displayed > in the logs table, but still displays only 10 entries which is the default > setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23916) [Logsearch UI] Rows per page drop down not working as expected in the log table
[ https://issues.apache.org/jira/browse/AMBARI-23916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23916: - Resolution: Fixed Status: Resolved (was: Patch Available) > [Logsearch UI] Rows per page drop down not working as expected in the log > table > --- > > Key: AMBARI-23916 > URL: https://issues.apache.org/jira/browse/AMBARI-23916 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 12h > Time Spent: 3.5h > Remaining Estimate: 8.5h > > Logs per page drop down not working as expected in the log table. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. From the log table, click on Rows per page and select 100 > 4. 100 or the maximum number (If lesser than 100) of logs should be displayed > in the logs table, but still displays only 10 entries which is the default > setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23679) Set appropriate s3a properties in core-site per best practice
[ https://issues.apache.org/jira/browse/AMBARI-23679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23679: - Resolution: Fixed Status: Resolved (was: Patch Available) Merged to branch-2.6. > Set appropriate s3a properties in core-site per best practice > - > > Key: AMBARI-23679 > URL: https://issues.apache.org/jira/browse/AMBARI-23679 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add S3-related properties to core-site.xml per best practice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23679) Set appropriate s3a properties in core-site per best practice
[ https://issues.apache.org/jira/browse/AMBARI-23679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23679: - Status: Patch Available (was: Open) > Set appropriate s3a properties in core-site per best practice > - > > Key: AMBARI-23679 > URL: https://issues.apache.org/jira/browse/AMBARI-23679 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23679) Set appropriate s3a properties in core-site per best practice
[ https://issues.apache.org/jira/browse/AMBARI-23679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23679: - Description: Add S3-related properties to core-site.xml per best practice. > Set appropriate s3a properties in core-site per best practice > - > > Key: AMBARI-23679 > URL: https://issues.apache.org/jira/browse/AMBARI-23679 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Add S3-related properties to core-site.xml per best practice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23679) Set appropriate s3a properties in core-site per best practice
[ https://issues.apache.org/jira/browse/AMBARI-23679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-23679: - Fix Version/s: (was: 2.7.0) > Set appropriate s3a properties in core-site per best practice > - > > Key: AMBARI-23679 > URL: https://issues.apache.org/jira/browse/AMBARI-23679 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.6.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23679) Set appropriate s3a properties in core-site per best practice
Yusaku Sako created AMBARI-23679: Summary: Set appropriate s3a properties in core-site per best practice Key: AMBARI-23679 URL: https://issues.apache.org/jira/browse/AMBARI-23679 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.6.2 Reporter: Yusaku Sako Assignee: Yusaku Sako Fix For: 2.6.2, 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21332: - Fix Version/s: (was: 3.0.0) 2.7.0 > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-21332.patch > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21332) Wizard's Minimized State - Show Who Initiated
[ https://issues.apache.org/jira/browse/AMBARI-21332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21332: - Affects Version/s: (was: 3.0.0) 2.7.0 > Wizard's Minimized State - Show Who Initiated > - > > Key: AMBARI-21332 > URL: https://issues.apache.org/jira/browse/AMBARI-21332 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-21332.patch > > > We need to keep track of who initiated the wizard in "persist" and show it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22421) Ambari upgrade is not idempotent if it fails with service not found error
[
https://issues.apache.org/jira/browse/AMBARI-22421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-22421:
Assignee: Dmitry Lysnichenko (was: Sandor Molnar)
> Ambari upgrade is not idempotent if it fails with service not found error
> -
>
> Key: AMBARI-22421
> URL: https://issues.apache.org/jira/browse/AMBARI-22421
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmitry Lysnichenko
>Priority: Major
> Fix For: 2.6.2
>
>
> If Upgrade is failed with below exception and try to upgrade from that point
> after correcting the service not found issue.
> {noformat}
> 06 Nov 2017 04:31:26,823 ERROR [main] SchemaUpgradeHelper:233 - Upgrade
> failed.
> org.apache.ambari.server.ServiceNotFoundException: Service not found,
> clusterName=, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> 06 Nov 2017 04:31:26,826 ERROR [main] SchemaUpgradeHelper:437 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> {noformat}
> Upgrade fails with below exception
> {noformat}
> INFO: Updating Ambari Server properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> INFO: Can not find ambari-env.sh.rpmsave file from previous version, skipping
> restore of environment settings. ambari-env.sh may not include any user
> customization.
> INFO: Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)?
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> cluster_version table does not contain repo_version_id column
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: java.lang.IllegalArgumentException: cluster_version table does not
> contain repo_version_id column
> at
> org.apache.ambari.server.orm.DBAccessorImpl.getIntColumnValues(DBAccessorImpl.java:1536)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:507)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON
[jira] [Resolved] (AMBARI-23172) Build fails for Debian (jdeb plugin not found)
[
https://issues.apache.org/jira/browse/AMBARI-23172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako resolved AMBARI-23172.
--
Resolution: Fixed
Committed to trunk.
> Build fails for Debian (jdeb plugin not found)
> --
>
> Key: AMBARI-23172
> URL: https://issues.apache.org/jira/browse/AMBARI-23172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] No plugin found for prefix 'jdeb'
> in the current project and in the plugin groups [org.sonatype.plugins,
> org.apache.maven.plugins, org.codehaus.mojo] available from the repositories
> [local (/grid/0/jenkins/.m2/repository), public
> (http://nexus-private.hortonworks.com/nexus/content/groups/public)] -> [Help
> 1]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] To see the full stack trace of
> the errors, re-run Maven with the -e switch.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] Re-run Maven using the -X switch
> to enable full debug logging.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] For more information about the
> errors and possible solutions, please read the following articles:
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-22918:
Assignee: Toshihiro Suzuki
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 114, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 55, in decommission
> hbase_decommission(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py",
> line 84, in hbase_decommission
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/mast...@example.com; /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1' returned 1. Error: Could not find or load main class
> org.jruby.Main{code}
> stdout:
> {code:java}
> 2018-02-06 07:25:03,453 - Stack Feature Version Info: Cluster Stack=2.6,
> Cluster Current Version=2.6.2.0-205, Command Stack=None, Command
> Version=2.6.2.0-205 -> 2.6.2.0-205
> 2018-02-06 07:25:03,476 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-02-06 07:25:03,484 - checked_call['hostid'] {}
> 2018-02-06 07:25:03,490 - checked_call returned (0, '1aacc56c')
> 2018-02-06 07:25:03,502 -
> File['/usr/hdp/current/hbase-master/bin/draining_servers.rb'] {'content':
> StaticFile('draining_servers.rb'), 'mode': 0755}
> 2018-02-06 07:25:03,504 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab hbase/mast...@example.com;
> /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1'] {'logoutput': True, 'user': 'hbase'}
> Error: Could not find or load main class org.jruby.Main
> Command failed after 1 tries{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22716) zeppelin.livy.url is not getting updated after moving livy to a new host
[ https://issues.apache.org/jira/browse/AMBARI-22716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22716: - Fix Version/s: (was: 2.6.1) 2.6.2 > zeppelin.livy.url is not getting updated after moving livy to a new host > > > Key: AMBARI-22716 > URL: https://issues.apache.org/jira/browse/AMBARI-22716 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.1 > Environment: ambari-server --version 2.6.1.0-137 > HDP-2.6.4.0-86 >Reporter: Supreeth Sharma >Assignee: Prabhjyot Singh >Priority: Critical > Fix For: 2.6.2 > > Attachments: 0AMBARI-22716_branch-2.6_v1.patch, > 0AMBARI-22716_trunk_v1.patch > > > zeppelin.livy.url is not getting updated after moving livy to a new host > Steps to reproduce : > 1) Create a cluster with both Spark and Spark2 component > 2) Delete livy component from current host. > 3) Add the livy component on a new host > 4) Restart zeppelin server. > 5) Now check the zeppelin interpreter settings. zeppelin.livy.url is still > referring to older livy host. > Its not reflecting the new livy server address. > Note 1 : If I restart zeppelin server after step1 (ie after deleting the livy > host) before performing rest of the steps, then changes are getting reflected > properly. System test was mistakenly doing this step so didn't fail during > nightly run > Note 2 : Issue is happening only when both Spark and Spark2 are installed. If > cluster contains only Spark2, this feature works as expected. > Issue is coming if I add Spark(version 1) to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22512) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/AMBARI-22512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-22512. -- Resolution: Fixed Assignee: Yusaku Sako > Please delete old releases from mirroring system > > > Key: AMBARI-22512 > URL: https://issues.apache.org/jira/browse/AMBARI-22512 > Project: Ambari > Issue Type: Bug >Reporter: Sebb >Assignee: Yusaku Sako > > The ASF relies on volunteers to provide its mirror download service, so it is > important that only current releases served via the ASF mirror system. Older > releases should be archived. > Please can you remove all non-current releases? > It's unfair to expect the 3rd party mirrors to carry old releases. > Note that older releases can still be linked from the download page, but such > links should use the archive server at: > https://archive.apache.org/dist/ambari/ > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-22626:
-
Fix Version/s: 2.6.2
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reopened AMBARI-22626:
--
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-22626:
-
Status: Patch Available (was: Reopened)
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287989#comment-16287989
]
Yusaku Sako commented on AMBARI-22626:
--
Reopening so that we can keep track of committing this to branch-2.6 once 2.6.1
is released.
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22635: - Fix Version/s: 2.6.2 > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.patch, AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22635: - Fix Version/s: (was: 2.6.1) > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk > > Attachments: AMBARI-22635-branch-2.6.patch, AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287814#comment-16287814
]
Yusaku Sako commented on AMBARI-22626:
--
Committed to trunk.
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-22626:
-
Fix Version/s: (was: 2.6.1)
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-22626:
-
Priority: Critical (was: Blocker)
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22578) hive2 queries fails after adding any service to the cluster
[
https://issues.apache.org/jira/browse/AMBARI-22578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-22578:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
+1'd on ReviewBoard.
Committed to trunk and branch-2.6.
> hive2 queries fails after adding any service to the cluster
> ---
>
> Key: AMBARI-22578
> URL: https://issues.apache.org/jira/browse/AMBARI-22578
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Santhosh B Gowda
>Assignee: Jaimin Jetly
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22578.patch
>
>
> After adding beacon component, hive2 queries fail with below exception
> {code}
> select t_hour,count(t_hour) from time_dim group by t_hour;
> INFO : Compiling
> command(queryId=hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013):
> select t_hour,count(t_hour) from time_dim group by t_hour
> INFO : We are setting the hadoop caller context from
> HIVE_SSN_ID:3d33e44f-5f12-40d1-a88c-8cb8e7841885 to
> hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013
> INFO : Semantic Analysis Completed
> INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:t_hour,
> type:int, comment:null), FieldSchema(name:_c1, type:bigint, comment:null)],
> properties:null)
> INFO : Completed compiling
> command(queryId=hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013);
> Time taken: 0.131 seconds
> INFO : We are resetting the hadoop caller context to
> HIVE_SSN_ID:3d33e44f-5f12-40d1-a88c-8cb8e7841885
> INFO : Setting caller context to query id
> hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013
> INFO : Executing
> command(queryId=hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013):
> select t_hour,count(t_hour) from time_dim group by t_hour
> INFO : Query ID = hive_20171117151724_678c0fad-bb02-4a07-9b5b-2f8c6ad34013
> INFO : Total jobs = 1
> INFO : Launching Job 1 out of 1
> INFO : Starting task [Stage-1:MAPRED] in serial mode
> INFO : Tez session hasn't been created yet. Opening session
> INFO : Dag name: select t_hour,count(t_hour) from ti...t_hour(Stage-1)
> INFO : Dag submit failed due to Invalid TaskLaunchCmdOpts defined for Vertex
> Map 1 : Invalid/conflicting GC options found, cmdOpts="-server
> -Djava.net.preferIPv4Stack=true -Dhdp.version=2.6.3.0-222 -XX:+PrintGCDetails
> -verbose:gc -XX:+PrintGCTimeStamps -XX:+UseNUMA -XX:+UseG1GC -XX:+ResizeTLAB
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/grid/0/dumps/hive -server
> -Xmx11469m -Djava.net.preferIPv4Stack=true -XX:NewRatio=8 -XX:+UseNUMA
> -XX:+UseParallelGC -XX:+PrintGCDetails -verbose:gc -XX:+PrintGCTimeStamps
> -Dlog4j.configuratorClass=org.apache.tez.common.TezLog4jConfigurator
> -Dlog4j.configuration=tez-container-log4j.properties
> -Dyarn.app.container.log.dir= -Dtez.root.logger=INFO,CLA " stack
> trace: [org.apache.tez.dag.api.DAG.createDag(DAG.java:1009),
> org.apache.tez.client.TezClientUtils.prepareAndCreateDAGPlan(TezClientUtils.java:720),
> org.apache.tez.client.TezClient.submitDAGSession(TezClient.java:555),
> org.apache.tez.client.TezClient.submitDAG(TezClient.java:522),
> org.apache.hadoop.hive.ql.exec.tez.TezTask.submit(TezTask.java:548),
> org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:198),
> org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:199),
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:100),
> org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1987),
> org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1667),
> org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1414),
> org.apache.hadoop.hive.ql.Driver.run(Driver.java:1211),
> org.apache.hadoop.hive.ql.Driver.run(Driver.java:1204),
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:242),
>
> org.apache.hive.service.cli.operation.SQLOperation.access$800(SQLOperation.java:91),
>
> org.apache.hive.service.cli.operation.SQLOperation$BackgroundWork$1.run(SQLOperation.java:336),
> java.security.AccessController.doPrivileged(Native Method),
> javax.security.auth.Subject.doAs(Subject.java:422),
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866),
>
> org.apache.hive.service.cli.operation.SQLOperation$BackgroundWork.run(SQLOperation.java:350),
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511),
> java.util.concurrent.FutureTask.run(FutureTask.java:266),
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511),
> java.util.concurrent.FutureTask.run(FutureTask.java:266),
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142),
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(T
[jira] [Updated] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22299: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6. > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22299: - Status: Patch Available (was: Reopened) > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-22299: -- > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22299: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. Will commit to branch-2.6 once the 2.6.0 release goes out. > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217593#comment-16217593 ] Yusaku Sako commented on AMBARI-22299: -- No existing tests to check for Storm View. The View compiles successfully with the patch: [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 01:00 min [INFO] Finished at: 2017-10-24T13:07:50-07:00 [INFO] Final Memory: 30M/435M [INFO] > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22299: - Attachment: AMBARI-22299.patch > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22299) Storm View: Update Node version for PPC support
[ https://issues.apache.org/jira/browse/AMBARI-22299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22299: - Status: Patch Available (was: Open) > Storm View: Update Node version for PPC support > --- > > Key: AMBARI-22299 > URL: https://issues.apache.org/jira/browse/AMBARI-22299 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22299.patch > > > Node 5.6.0 is being used for Storm View. > However, there's no Node 5.6.0 for PPC. > Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22299) Storm View: Update Node version for PPC support
Yusaku Sako created AMBARI-22299: Summary: Storm View: Update Node version for PPC support Key: AMBARI-22299 URL: https://issues.apache.org/jira/browse/AMBARI-22299 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.1 Reporter: Yusaku Sako Assignee: Yusaku Sako Priority: Critical Fix For: 2.6.1 Node 5.6.0 is being used for Storm View. However, there's no Node 5.6.0 for PPC. Therefore, the Node version is being updated from 5.6.0 to 5.7.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-21955. -- Resolution: Fixed Thanks for your help offline. I was able to apply the patch properly via "git apply". Ran rat check and it passed this time without modifications. Committed to trunk and branch-2.6. > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch, storm-monitoring-build-error-2.6.txt > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21955: - Priority: Blocker (was: Major) > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch, storm-monitoring-build-error-2.6.txt > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213233#comment-16213233 ] Yusaku Sako edited comment on AMBARI-21955 at 10/20/17 9:04 PM: Reopening since Storm Monitoring fails to build consistently after the patch is applied. Please see the attached for the output. [^storm-monitoring-build-error-2.6.txt] was (Author: u39kun): Reopening since Storm Monitoring fails to build consistently after the patch is applied. Please see the attached for the output. > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch, storm-monitoring-build-error-2.6.txt > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21955: - Attachment: storm-monitoring-build-error-2.6.txt > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch, storm-monitoring-build-error-2.6.txt > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reopened AMBARI-21955: -- Reopening since Storm Monitoring fails to build consistently after the patch is applied. Please see the attached for the output. > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21955: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6. (Modified pom.xml to fix a rat check error.) > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21955) Update React version to 15.6.2 to get MIT license
[ https://issues.apache.org/jira/browse/AMBARI-21955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21955: - Fix Version/s: 2.6.0 > Update React version to 15.6.2 to get MIT license > - > > Key: AMBARI-21955 > URL: https://issues.apache.org/jira/browse/AMBARI-21955 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Sanket Shah >Assignee: Sanket Shah > Fix For: 2.6.0 > > Attachments: AMBARI-21955.patch > > > The Apache Software Foundation Legal Affairs Committee [has announced | > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663]that > the so-called 'Facebook BSD+Patents License' is no longer allowed to be used > as a direct dependency in Apache projects. > Since Storm View is using React.js which is under the same Facebook's > license, needs to get rid of and use Vue.js instead. > cc: [~ggolani] > Update: No need to port to Vue, instead update the version to get MIT license. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22268) Remove "Hotfix" from Admin Register Version
[ https://issues.apache.org/jira/browse/AMBARI-22268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22268: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6. > Remove "Hotfix" from Admin Register Version > --- > > Key: AMBARI-22268 > URL: https://issues.apache.org/jira/browse/AMBARI-22268 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-22268_branch-2.6.patch > > > In the Admin View, change "Add Version or Hotfix ..." to just "Add Version > ..." > We are not going to be explicit in the support of patches for this first > release of 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22268) Remove "Hotfix" from Admin Register Version
[ https://issues.apache.org/jira/browse/AMBARI-22268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210139#comment-16210139 ] Yusaku Sako commented on AMBARI-22268: -- The patch does not directly apply to trunk as shown above, but I've gone ahead and resolved the conflict. Since this is a simple text label change, I'm not waiting for the unit test results. > Remove "Hotfix" from Admin Register Version > --- > > Key: AMBARI-22268 > URL: https://issues.apache.org/jira/browse/AMBARI-22268 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-22268_branch-2.6.patch > > > In the Admin View, change "Add Version or Hotfix ..." to just "Add Version > ..." > We are not going to be explicit in the support of patches for this first > release of 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22250) Upgrade option not showing in stack versions for an upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-22250: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6. > Upgrade option not showing in stack versions for an upgrade > --- > > Key: AMBARI-22250 > URL: https://issues.apache.org/jira/browse/AMBARI-22250 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-22250.patch, AMBARI-22250_branch-2.6.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16132046#comment-16132046 ] Yusaku Sako commented on AMBARI-21751: -- branch-2.6 failure above is not related to this patch. > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21751: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131991#comment-16131991 ] Yusaku Sako commented on AMBARI-21751: -- Committed to branch-2.5 and branch-2.6. > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131989#comment-16131989 ] Yusaku Sako commented on AMBARI-21751: -- The failure above is due to the fact that AMBARI-21045 was never committed to trunk (for some reason). This patch should be applied to branch-2.6 and branch-2.5. > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21751: - Attachment: AMBARI-21751.patch > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21751) Fix regression caused by AMBARI-21045
[ https://issues.apache.org/jira/browse/AMBARI-21751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21751: - Status: Patch Available (was: Open) > Fix regression caused by AMBARI-21045 > - > > Key: AMBARI-21751 > URL: https://issues.apache.org/jira/browse/AMBARI-21751 > Project: Ambari > Issue Type: Bug > Components: service-advisor >Affects Versions: 2.5.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21751.patch > > > AMBARI-21045 caused a regression where it masks the Beacon mpack service > advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21751) Fix regression caused by AMBARI-21045
Yusaku Sako created AMBARI-21751: Summary: Fix regression caused by AMBARI-21045 Key: AMBARI-21751 URL: https://issues.apache.org/jira/browse/AMBARI-21751 Project: Ambari Issue Type: Bug Components: service-advisor Affects Versions: 2.5.2 Reporter: Yusaku Sako Assignee: Yusaku Sako Priority: Critical Fix For: 2.5.2 AMBARI-21045 caused a regression where it masks the Beacon mpack service advisor from getting invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17991) Ambari agent unable to register with server when server response is too big
[
https://issues.apache.org/jira/browse/AMBARI-17991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-17991:
-
Description:
Ambari agent is unable to register with ambari server, failing with:
{code}
INFO 2016-06-09 11:22:00,964 security.py:147 - Encountered communication error.
Details: SSLError('The read operation timed out',)
ERROR 2016-06-09 11:22:00,965 Controller.py:196 - Unable to connect to:
https://localhost:8441/agent/v1/register/host1
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 150,
in registerWithServer
ret = self.sendRequest(self.registerUrl, data)
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 423,
in sendRequest
raise IOError('Request to {0} failed due to {1}'.format(url,
str(exception)))
IOError: Request to https://server1:8441/agent/v1/register/host1 failed due to
Error occured during connecting to the server: The read operation timed out
ERROR 2016-06-09 11:22:00,965 Controller.py:197 - Error:Request to
https://server1:8441/agent/v1/register/host1 failed due to Error occured during
connecting to the server: The read operation timed out
{code}
The problem was fixed by modifying the timeout in
/usr/lib/python2.6/site-packages/ambari_agent/security.py:
{code}
def create_connection(self):
if self.sock:
self.sock.close()
logger.info("SSL Connect being called.. connecting to the server")
sock = socket.create_connection((self.host, self.port), 120)
{code}
Use Jetty 8 instead of 9 in Ambari 2.4.0
was:
Ambari agent is unable to register with ambari server, failing with:
{code}
INFO 2016-06-09 11:22:00,964 security.py:147 - Encountered communication error.
Details: SSLError('The read operation timed out',)
ERROR 2016-06-09 11:22:00,965 Controller.py:196 - Unable to connect to:
https://localhost:8441/agent/v1/register/dvtcbdqd02.corp.cox.com
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 150,
in registerWithServer
ret = self.sendRequest(self.registerUrl, data)
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 423,
in sendRequest
raise IOError('Request to {0} failed due to {1}'.format(url,
str(exception)))
IOError: Request to https://server1:8441/agent/v1/register/host1 failed due to
Error occured during connecting to the server: The read operation timed out
ERROR 2016-06-09 11:22:00,965 Controller.py:197 - Error:Request to
https://server1:8441/agent/v1/register/host1 failed due to Error occured during
connecting to the server: The read operation timed out
{code}
The problem was fixed by modifying the timeout in
/usr/lib/python2.6/site-packages/ambari_agent/security.py:
{code}
def create_connection(self):
if self.sock:
self.sock.close()
logger.info("SSL Connect being called.. connecting to the server")
sock = socket.create_connection((self.host, self.port), 120)
{code}
Use Jetty 8 instead of 9 in Ambari 2.4.0
> Ambari agent unable to register with server when server response is too big
> ---
>
> Key: AMBARI-17991
> URL: https://issues.apache.org/jira/browse/AMBARI-17991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17991_2.patch, AMBARI-17991_3-branch-2.4.patch,
> AMBARI-17991_3-trunk.patch, AMBARI-17991.patch
>
>
> Ambari agent is unable to register with ambari server, failing with:
> {code}
> INFO 2016-06-09 11:22:00,964 security.py:147 - Encountered communication
> error. Details: SSLError('The read operation timed out',)
> ERROR 2016-06-09 11:22:00,965 Controller.py:196 - Unable to connect to:
> https://localhost:8441/agent/v1/register/host1
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 150, in registerWithServer
> ret = self.sendRequest(self.registerUrl, data)
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 423, in sendRequest
> raise IOError('Request to {0} failed due to {1}'.format(url,
> str(exception)))
> IOError: Request to https://server1:8441/agent/v1/register/host1 failed due
> to Error occured during connecting to the server: The read operation timed out
> ERROR 2016-06-09 11:22:00,965 Controller.py:197 - Error:Request to
> https://server1:8441/agent/v1/register/host1 failed due to Error occured
> during connecting to the server: The read operation timed out
> {code}
> The problem was fixed by modifying the timeout in
> /usr/lib/python2.6/site-packages/ambari_agent/security.py:
>
[jira] [Commented] (AMBARI-21657) Ambari does not display metric data on widgets when the JMX path contains the '-' character.
[
https://issues.apache.org/jira/browse/AMBARI-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126601#comment-16126601
]
Yusaku Sako commented on AMBARI-21657:
--
+1 for the patch.
> Ambari does not display metric data on widgets when the JMX path contains the
> '-' character.
>
>
> Key: AMBARI-21657
> URL: https://issues.apache.org/jira/browse/AMBARI-21657
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.6.0
>
> Attachments: AMBARI-21657.patch
>
>
> {code}
> "name" : "Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4",
> "modelerType" : "AzureFileSystemMetrics4",
> "tag.Context" : "azureFileSystem",
> "tag.wasbFileSystemId" : "24f05882-a63a-43d4-9dec-eff23f9fcfa0",
> "tag.accountName" : "<>",
> "tag.containerName" : "xhdinsight-2017-07-24t21-26-36-619z",
> "tag.Hostname" : "zk2-xhdins",
> "wasb_web_responses" : 87824,
> "wasb_files_created" : 8
> {code}
> For example, the above metrics cannot be displayed on widgets due to the '-'
> in *Hadoop:service=azure-file-system,name=AzureFileSystemMetrics4*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21205) Make ToggleKerberos and AddDeleteService experimental features
[ https://issues.apache.org/jira/browse/AMBARI-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21205: - Affects Version/s: (was: 2.5.0) 2.5.2 > Make ToggleKerberos and AddDeleteService experimental features > -- > > Key: AMBARI-21205 > URL: https://issues.apache.org/jira/browse/AMBARI-21205 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0, 2.5.2 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-21205_1.patch, AMBARI-21205.patch > > > Toggling Kerberos and Adding/Deleting Services might not be supported for > some cloud environments (e.g. Azure). This Jira enables the ability to make > these features experimental in those environments. These features are still > enabled by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21205) Make ToggleKerberos and AddDeleteService experimental features
[ https://issues.apache.org/jira/browse/AMBARI-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21205: - Fix Version/s: (was: 2.5.0) 2.5.2 > Make ToggleKerberos and AddDeleteService experimental features > -- > > Key: AMBARI-21205 > URL: https://issues.apache.org/jira/browse/AMBARI-21205 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0, 2.5.0 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-21205_1.patch, AMBARI-21205.patch > > > Toggling Kerberos and Adding/Deleting Services might not be supported for > some cloud environments (e.g. Azure). This Jira enables the ability to make > these features experimental in those environments. These features are still > enabled by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21273) Swagger resources generation for doc purpose should not be part of default maven profile
[
https://issues.apache.org/jira/browse/AMBARI-21273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052388#comment-16052388
]
Yusaku Sako commented on AMBARI-21273:
--
+1
> Swagger resources generation for doc purpose should not be part of default
> maven profile
>
>
> Key: AMBARI-21273
> URL: https://issues.apache.org/jira/browse/AMBARI-21273
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-21273.patch
>
>
> On executing mvn compile on ambari-server and then checking with git status,
> following files are automatically added/edited even when no code changes are
> made
> {code}
> modified: ambari-server/docs/api/generated/index.html
> Untracked files:
> (use "git add ..." to include in what will be committed)
> docs/api/
> {code}
> As a fix to this issue, swagger resources that are presently checked in to
> ambari project at ambari-server/docs/api/generated/ will be updated only when
> mvn command is executed with -Dgenerate.swagger.resources flag.
> This is expected to be done and resources should be checked in just before
> every new ambari release. with this commit, ambari wiki page for release
> guideline will also be updated
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1679) Create ambari agent scripts for Hadoop 2.0 installation, configuration and management
[ https://issues.apache.org/jira/browse/AMBARI-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1679: --- Assignee: Siddharth Wagle > Create ambari agent scripts for Hadoop 2.0 installation, configuration and > management > - > > Key: AMBARI-1679 > URL: https://issues.apache.org/jira/browse/AMBARI-1679 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent >Affects Versions: 1.3.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 1.4.0 > > Attachments: AMBARI-1679.patch > > > Create ambari agent scripts for Hadoop 2.0 installation, configuration and > management based on HDP-1.3.1 stack definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-10484) Expose API endpoint to expose active widget layout for a user
[ https://issues.apache.org/jira/browse/AMBARI-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-10484: Assignee: Ivan Kozlov > Expose API endpoint to expose active widget layout for a user > - > > Key: AMBARI-10484 > URL: https://issues.apache.org/jira/browse/AMBARI-10484 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Siddharth Wagle >Assignee: Ivan Kozlov > Fix For: 2.1.0 > > > Support user endpoint to return active widget layouts for a user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-10543) String matches does not work on metrics property of Widget response
[
https://issues.apache.org/jira/browse/AMBARI-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-10543:
Assignee: Ivan Kozlov
> String matches does not work on metrics property of Widget response
> ---
>
> Key: AMBARI-10543
> URL: https://issues.apache.org/jira/browse/AMBARI-10543
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Siddharth Wagle
>Assignee: Ivan Kozlov
> Fix For: 2.1.0
>
>
> *Following API does not work*
> http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/metrics.matches(\"service_name\":\"HDFS\")
> *Note: Following similar API works*
> http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/widget_name.matches(HOST_DISK_USED)
> {code:title=Response}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets?Widgets/widget_type=HEATMAP&Widgets/widget_name.matches(HOST_DISK_USED)",
> "items" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/widgets/1";,
> "Widgets" : {
> "author" : "ambari",
> "cluster_name" : "c1",
> "display_name" : "Host Disk Space Used %",
> "id" : 1,
> "scope" : "CLUSTER",
> "widget_name" : "HOST_DISK_USED",
> "widget_type" : "HEATMAP"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-5637) Remove Start/Stop Hadoop Cluster Service tasks for Pig and Sqoop services
[ https://issues.apache.org/jira/browse/AMBARI-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5637: --- Assignee: Anatoly Nikonorov > Remove Start/Stop Hadoop Cluster Service tasks for Pig and Sqoop services > - > > Key: AMBARI-5637 > URL: https://issues.apache.org/jira/browse/AMBARI-5637 > Project: Ambari > Issue Type: Task > Components: contrib >Reporter: Anatoly Nikonorov >Assignee: Anatoly Nikonorov > Attachments: AMBARI-5637.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-2341) Installation of hadoop fails when /etc/hadoop/conf is present
[
https://issues.apache.org/jira/browse/AMBARI-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reopened AMBARI-2341:
-
> Installation of hadoop fails when /etc/hadoop/conf is present
> -
>
> Key: AMBARI-2341
> URL: https://issues.apache.org/jira/browse/AMBARI-2341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Reporter: Alexander Alten-Lorenz
>Priority: Blocker
>
> Installation fails when the config directories are present.
> Edit to be more precise (as example):
> {code}
> notice: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Skipping because of failed
> dependencies
> notice: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Skipping
> because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-5296) update Management Pack to support Hadoop MapReduce2 and YARN services
[ https://issues.apache.org/jira/browse/AMBARI-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5296: --- Assignee: Anatoly Nikonorov > update Management Pack to support Hadoop MapReduce2 and YARN services > - > > Key: AMBARI-5296 > URL: https://issues.apache.org/jira/browse/AMBARI-5296 > Project: Ambari > Issue Type: Task > Components: contrib >Reporter: Anatoly Nikonorov >Assignee: Anatoly Nikonorov > Attachments: AMBARI-5296.patch > > > Implement support for MapReduce2 and YARN services -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-2341) Installation of hadoop fails when /etc/hadoop/conf is present
[
https://issues.apache.org/jira/browse/AMBARI-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako resolved AMBARI-2341.
-
Resolution: Invalid
> Installation of hadoop fails when /etc/hadoop/conf is present
> -
>
> Key: AMBARI-2341
> URL: https://issues.apache.org/jira/browse/AMBARI-2341
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Reporter: Alexander Alten-Lorenz
>Priority: Blocker
>
> Installation fails when the config directories are present.
> Edit to be more precise (as example):
> {code}
> notice: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive/Anchor[hdp-hive::end]: Skipping because of failed
> dependencies
> notice: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Dependency
> File[/etc/hive/conf] has failures: true
> warning: /Stage[2]/Hdp-hive::Service/File[/tmp/startMetastore.sh]: Skipping
> because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-6484) HBase RegionServer -Xmn must be configurable
[ https://issues.apache.org/jira/browse/AMBARI-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-6484: --- Assignee: Azwaw OUSADOU > HBase RegionServer -Xmn must be configurable > > > Key: AMBARI-6484 > URL: https://issues.apache.org/jira/browse/AMBARI-6484 > Project: Ambari > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Azwaw OUSADOU >Assignee: Azwaw OUSADOU >Priority: Critical > Labels: features, patch > Fix For: 1.7.0 > > Attachments: AMBARI-6484.diff, AMBARI-6484.diff, > AMBARI-6484-TEST-OUTPUT.txt, MASTER-TEST-OUTPUT.txt, XMN_CONFIGURABLE.diff > > > -Xmn parameter for HBase RegionServer is calculated with hardcoded value. > This patch allows you to configure values used to calculate this parameter > (the maximum value for -Xmn and the ratio between -Xmn and -Xmx). > Without this fix HBase can be crash because of OutOfMemory when you do a YCSB > test for example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3412) Ambari-SCOM MSI have to perform rollback in case of interrupted installation
[ https://issues.apache.org/jira/browse/AMBARI-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3412: --- Assignee: Tom Beerbower > Ambari-SCOM MSI have to perform rollback in case of interrupted installation > > > Key: AMBARI-3412 > URL: https://issues.apache.org/jira/browse/AMBARI-3412 > Project: Ambari > Issue Type: Improvement > Components: contrib >Reporter: Dmitriy Balykin >Assignee: Tom Beerbower > Attachments: 0001-AMBARI-3412.patch, > 0001-Moving-last-changes-to-apache.patch > > > MSI have to perform rollback in case of interrupted installation -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3383) Installation Ambari-SCOM with incorrect DMBS credentials finishes without warning
[ https://issues.apache.org/jira/browse/AMBARI-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3383: --- Assignee: Ivan Malamen (was: Ivan Kozlov) > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning > - > > Key: AMBARI-3383 > URL: https://issues.apache.org/jira/browse/AMBARI-3383 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, MSSQL Server 2008 R2 >Reporter: Dmitriy Balykin >Assignee: Ivan Malamen > Attachments: > 0001-Ambari-SCOM-Installation-with-incorrect-DMBS-credent.patch > > > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning. > DB for Ambari metrics and all tables didn't created, so installed Ambari > cannot work properly until it will be reinstalled with correct credentials, > or DB with all tables will created manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3382) Ambari-SCOM MSI doesn't check if HDP available during installation
[ https://issues.apache.org/jira/browse/AMBARI-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3382: --- Assignee: Ivan Malamen > Ambari-SCOM MSI doesn't check if HDP available during installation > -- > > Key: AMBARI-3382 > URL: https://issues.apache.org/jira/browse/AMBARI-3382 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, no HDP available on current node >Reporter: Dmitriy Balykin >Assignee: Ivan Malamen > Attachments: > 0001-Ambari-SCOM-MSI-doesn-t-check-if-HDP-available-durin.patch > > > Installation started using command line, parameter HDP_LAYOUT skipped. > Installation failed with error: > "No Ambari Properties file found, make sure the file $ENV:AMB_LAYOUT > exists and contains the current cluster layout" > This error could be not clear for user. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-3383) Installation Ambari-SCOM with incorrect DMBS credentials finishes without warning
[ https://issues.apache.org/jira/browse/AMBARI-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-3383: --- Assignee: Ivan Kozlov > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning > - > > Key: AMBARI-3383 > URL: https://issues.apache.org/jira/browse/AMBARI-3383 > Project: Ambari > Issue Type: Bug > Components: contrib > Environment: Windows 2008 R2, MSSQL Server 2008 R2 >Reporter: Dmitriy Balykin >Assignee: Ivan Kozlov > Attachments: > 0001-Ambari-SCOM-Installation-with-incorrect-DMBS-credent.patch > > > Installation Ambari-SCOM with incorrect DMBS credentials finishes without > warning. > DB for Ambari metrics and all tables didn't created, so installed Ambari > cannot work properly until it will be reinstalled with correct credentials, > or DB with all tables will created manually. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5792) Change the container-executor.class for Gluster
[ https://issues.apache.org/jira/browse/AMBARI-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5792: --- Assignee: Erin A Boyd > Change the container-executor.class for Gluster > --- > > Key: AMBARI-5792 > URL: https://issues.apache.org/jira/browse/AMBARI-5792 > Project: Ambari > Issue Type: Bug >Affects Versions: 1.5.0, 1.6.0, 1.6.1 >Reporter: Erin A Boyd >Assignee: Erin A Boyd > Fix For: 1.6.0, 1.6.1 > > Attachments: 5792.patch > > > Update > > yarn.nodemanager.container-executor.class > from : > org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor > to: >org.apache.hadoop.yarn.server.nodemanager.GlusterContainerExecutor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-11046) Update gluster specific fields for oozie and hive
[ https://issues.apache.org/jira/browse/AMBARI-11046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-11046: Assignee: Erin A Boyd > Update gluster specific fields for oozie and hive > - > > Key: AMBARI-11046 > URL: https://issues.apache.org/jira/browse/AMBARI-11046 > Project: Ambari > Issue Type: Bug >Reporter: Erin A Boyd >Assignee: Erin A Boyd > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-2405) Make non-cloud response objects optional
[ https://issues.apache.org/jira/browse/AMBARI-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-2405: --- Assignee: Tom Beerbower > Make non-cloud response objects optional > > > Key: AMBARI-2405 > URL: https://issues.apache.org/jira/browse/AMBARI-2405 > Project: Ambari > Issue Type: Improvement > Components: documentation >Reporter: Brian Swan >Assignee: Tom Beerbower >Priority: Minor > Attachments: AMBARI-2405.patch > > > Several of the Ambari API response schemas > (https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md) > list several objects as required that don't make sense when Ambari is > deployed in a cloud hosting environment. These objects should be made > optional. Specifically, the following properties should be optional (listed > by API call): > /clusters/:clusterName >* cluster_id >* requests >* configurations > /clusters/:clusterName/hosts/:hostname >* public_host_name >* rack_info >* total_mem > /clusters/:clusterName/hosts/:hostName/host_components/:componentName >* desired_stack_id >* stack_id > /clusters//hosts//host_components/datanode (also tasktracker) >* disk >* cpu >* load >* memory >* network > /clusters/:clusterName >* workflows > /clusters//hosts/ >* host_status >* host_state -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-12977) ambari-metrics fails to package from .deb on ubuntu 14.04
[ https://issues.apache.org/jira/browse/AMBARI-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-12977: Assignee: Canan Girgin > ambari-metrics fails to package from .deb on ubuntu 14.04 > - > > Key: AMBARI-12977 > URL: https://issues.apache.org/jira/browse/AMBARI-12977 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Canan Girgin >Assignee: Canan Girgin >Priority: Minor > Fix For: 2.3.0 > > Attachments: AMBARI-12977.patch > > > running "mvn -B clean install package jdeb:jdeb -DskipTests > -Dpython.ver="python >= 2.6" -Preplaceurl" command on ambari directory, shows > failure caused by problems during dep packaging. > if want to package only ambari-metrics and run command on ambari-metrics > directory everything is ok. > [INFO] Ambari Main ... SUCCESS [7.888s] > [INFO] Apache Ambari Project POM . SUCCESS [0.069s] > [INFO] Ambari Web SUCCESS [15.178s] > [INFO] Ambari Views .. SUCCESS [2.366s] > [INFO] Ambari Admin View . SUCCESS [24.536s] > [INFO] ambari-metrics SUCCESS [1.602s] > [INFO] Ambari Metrics Common . SUCCESS [1.215s] > [INFO] Ambari Metrics Hadoop Sink FAILURE [3.265s] > [INFO] Ambari Metrics Flume Sink . SKIPPED > [INFO] Ambari Metrics Kafka Sink . SKIPPED > [INFO] Ambari Metrics Storm Sink . SKIPPED > [INFO] Ambari Metrics Collector .. SKIPPED > [INFO] Ambari Metrics Monitor SKIPPED > [INFO] Ambari Metrics Assembly ... SKIPPED > [INFO] Ambari Server . SKIPPED > [INFO] Ambari Agent .. SKIPPED > [INFO] Ambari Client . SKIPPED > [INFO] Ambari Python Client .. SKIPPED > [INFO] Ambari Groovy Client .. SKIPPED > [INFO] Ambari Shell .. SKIPPED > [INFO] Ambari Python Shell ... SKIPPED > [INFO] Ambari Groovy Shell ... SKIPPED > [ERROR] Failed to create debian package > /home/a/repo/ambariRoot/ambari-metrics/ambari-metrics-hadoop-sink/target/ambari-metrics-hadoop-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambariRoot/ambari-metrics/ambari-metrics-hadoop-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/target/ambari-metrics-flume-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/target/ambari-metrics-flume-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-flume-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-kafka-sink/target/ambari-metrics-kafka-sink_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-kafka-sink/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-timelineservice/target/ambari-metrics-timelineservice_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-timelineservice/src/main/package/deb/control" > is not a valid 'control' directory) > at org.vafer.jdeb.maven.DebMaker.makeDeb(DebMaker.java:186) > * > [ERROR] Failed to create debian package > /home/a/repo/ambari/ambari-metrics/ambari-metrics-host-monitoring/target/ambari-metrics-host-monitoring_2.1.0~SNAPSHOT_all.deb > org.vafer.jdeb.PackagingException: > "/home/a/repo/ambari/ambari-metrics/ambari-metrics-host-monitoring/src/main/package/deb/control" > is not a valid
[jira] [Assigned] (AMBARI-4631) unittest PropertyFile
[ https://issues.apache.org/jira/browse/AMBARI-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-4631: --- Assignee: Iryna Kuzmenko > unittest PropertyFile > - > > Key: AMBARI-4631 > URL: https://issues.apache.org/jira/browse/AMBARI-4631 > Project: Ambari > Issue Type: Bug >Reporter: Iryna Kuzmenko >Assignee: Iryna Kuzmenko > Fix For: 1.5.0 > > Attachments: AMBARI-4631.patch > > > Files to test are in > ambari/agent/src/main/python/resource_management/libraries/providers and > ../resources > Tests are here with some examples of other resources tested: > /ambari-agent/src/test/python/resource_management > Be sure to have unnitest for every attribute of this resource. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5631) Ambari SCOM .msi support for HDP2.1
[ https://issues.apache.org/jira/browse/AMBARI-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5631: --- Assignee: Ivan Malamen > Ambari SCOM .msi support for HDP2.1 > --- > > Key: AMBARI-5631 > URL: https://issues.apache.org/jira/browse/AMBARI-5631 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: > 0001-AMBARI-5631-Ambari-SCOM-.msi-support-for-HDP2.1.patch > > > Comparing HDP2.0.x and HDP2.1.x, some components changed their names. As a > result, corresponding config files that should be edited on .msi installation > also changed. > For example, there are _historyserver_ and _jobhistoryserver_ services in > HDP2.1. > _historyserver_ is not more the same than in HDP2.0.x, it refers to Apache > Hadoop YARN TimelineServer, is disabled by default and shouldn't be affected > by .msi. > _jobhistoryserver_ is required, its config file > _%HADOOP_HOME%\bin\jobhistoryserver.xml_ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5762) Remove MP msi from package
[ https://issues.apache.org/jira/browse/AMBARI-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5762: --- Assignee: Ivan Malamen > Remove MP msi from package > -- > > Key: AMBARI-5762 > URL: https://issues.apache.org/jira/browse/AMBARI-5762 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen > Attachments: AMBARI-5762.patch > > > Remove MSI building and copying from build scripts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5579) Fix build for Ambari-SCOM 2.0
[ https://issues.apache.org/jira/browse/AMBARI-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5579: --- Assignee: Ivan Malamen > Fix build for Ambari-SCOM 2.0 > - > > Key: AMBARI-5579 > URL: https://issues.apache.org/jira/browse/AMBARI-5579 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: 0001-AMBARI-5579-Fix-build-for-Ambari-SCOM-2.0.patch > > > Need to fix failing build for Ambari-SCOM 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5601) Ambari-SCOM build is failing
[ https://issues.apache.org/jira/browse/AMBARI-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5601: --- Assignee: Ivan Malamen > Ambari-SCOM build is failing > > > Key: AMBARI-5601 > URL: https://issues.apache.org/jira/browse/AMBARI-5601 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > > CoreCompile: > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig /unsafe+ > /nowarn:1701,1702 /nostdlib+ /errorreport:prompt /warn:4 /define:TRACE > /highentropyva- /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Core.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Data.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Management.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.ServiceProcess.dll" > /reference:"C:\Program Files (x86)\Reference > Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Xml.dll" > /debug:pdbonly /filealign:512 /optimize+ /out:obj\Release\ServiceHost.exe > /target:exe /utf8output DynamicProxy.cs Main.cs Properties\AssemblyInfo.cs > Wmi.cs WmiSchema.cs > "C:\Users\jenkins\AppData\Local\Temp\.NETFramework,Version=v4.0.AssemblyAttributes.cs" > WmiSchema.cs(77,1): error CS0116: A namespace cannot directly contain members > such as fields or methods > [d:\w\ambari-scom\ambari\contrib\ambari-scom\msi\src\ServiceHost\ServiceHost.csproj] > Done Building Project > "d:\w\ambari-scom\ambari\contrib\ambari-scom\msi\src\ServiceHost\ServiceHost.csproj" > (clean;build target(s)) -- FAILED. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5562) Ambari SCOM server should run as windows service
[ https://issues.apache.org/jira/browse/AMBARI-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5562: --- Assignee: Ivan Malamen > Ambari SCOM server should run as windows service > > > Key: AMBARI-5562 > URL: https://issues.apache.org/jira/browse/AMBARI-5562 > Project: Ambari > Issue Type: Improvement > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen > Attachments: > 0001-AMBARI-5562-Ambari-SCOM-server-should-run-as-windows.patch > > > 1.We should use service name the same with name which displayed after install > of msi in Control Panel\All Control Panel Items\Programs and Features > 2.use manual start type like hadoop services > 3.think we should use OS user -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5630) Ambari SCOM .msi should detect HDP version dynamically
[ https://issues.apache.org/jira/browse/AMBARI-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5630: --- Assignee: Ivan Malamen > Ambari SCOM .msi should detect HDP version dynamically > -- > > Key: AMBARI-5630 > URL: https://issues.apache.org/jira/browse/AMBARI-5630 > Project: Ambari > Issue Type: Bug > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: > 0001-AMBARI-5630-Ambari-SCOM-.msi-should-detect-HDP-versi.patch, > Ambari_GUI.JPG, ambariproperties.txt > > > HDP version is defined by _scom.version.id_ property in > _%AMB_DATA_DIR%\ambari-scom-server-conf\conf\ambari.properties_ file. This > version is then displayed in REST API by > _http://:8080/api/v1/clusters/_ request. > Currently it is hardcoded in .msi. We should avoid having wrong HDP version > in conf file and in API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5675) RECREATE_DB option is ignored by command-line .msi installation
[ https://issues.apache.org/jira/browse/AMBARI-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5675: --- Assignee: Ivan Malamen > RECREATE_DB option is ignored by command-line .msi installation > --- > > Key: AMBARI-5675 > URL: https://issues.apache.org/jira/browse/AMBARI-5675 > Project: Ambari > Issue Type: Bug >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Critical > Attachments: > 0001-AMBARI-5675-RECREATE_DB-option-is-ignored-by-command.patch > > > Hadoop-Metrics-SQLServer-CREATE.ddl isn't executed if .msi is installing from > command line via msiexec with _RECREATE_DB=yes_ or without _RECREATE_DB_ at > all (yes by default). > By the way, it works correctly via GUI installation both with RECREATE_DB=yes > and no. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5550) Create MSI for Ambari-SCOM 2.0.0.0
[ https://issues.apache.org/jira/browse/AMBARI-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5550: --- Assignee: Ivan Malamen > Create MSI for Ambari-SCOM 2.0.0.0 > -- > > Key: AMBARI-5550 > URL: https://issues.apache.org/jira/browse/AMBARI-5550 > Project: Ambari > Issue Type: New Feature > Components: contrib >Reporter: Ivan Malamen >Assignee: Ivan Malamen >Priority: Blocker > Attachments: 0001-AMBARI-5550-Create-MSI-for-Ambari-SCOM-2.0.0.0.patch > > > The MSI should support fresh install as well as upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-7753) DataNode decommision error in secured cluster
[
https://issues.apache.org/jira/browse/AMBARI-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-7753:
---
Assignee: jaehoon ko
> DataNode decommision error in secured cluster
> -
>
> Key: AMBARI-7753
> URL: https://issues.apache.org/jira/browse/AMBARI-7753
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 1.6.1
> Environment: Ambari-1.6.1 with HDP-2.1.5
>Reporter: jaehoon ko
>Assignee: jaehoon ko
> Labels: patch
> Fix For: 2.0.0
>
> Attachments: AMBARI-7753.patch
>
>
> Decommissioning a DataNode from a secured cluster returns errors with the
> following messages
> {code}
> STDERR:
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 111, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
> line 66, in decommission
> namenode(action="decommission")
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 70, in namenode
> decommission()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 145, in
> decommission
> user=hdfs_user
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 148, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 149, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 115, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in
> Kerberos database while getting initial
> credentials
> {code}
> {code}
> STDOUT:
> 2014-10-13 10:37:31,793 - File['/etc/hadoop/conf/dfs.exclude'] {'owner':
> 'hdfs', 'content': Template
> ('exclude_hosts_list.j2'), 'group': 'hadoop'}
> 2014-10-13 10:37:31,796 - Writing File['/etc/hadoop/conf/dfs.exclude']
> because contents don't match
> 2014-10-13 10:37:31,797 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;'] {'user': 'hdfs'}
> 2014-10-13 10:37:31,896 - Error while executing command 'decommission':
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 111, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py",
> line 66, in decommission
> namenode(action="decommission")
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 70, in namenode
> decommission()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py",
> line 145, in
> decommission
> user=hdfs_user
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 148, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 149, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 115, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 239, in action_run
> raise ex
> Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/dn.service.keytab dn/master-
> 6.amber.gbcl@amber.gbcluster.net;' returned 1. kinit: Client not found in
> Kerberos database while getting initial
> credentials
> {code}
> The reason is that Ambar-agent uses DataNode principal to perform HDFS
> refresh, which should be done as NameNode. This error can be solved by
> letting Ambari-agent uses NameNode kerberos principal and keytab. Note that
> [AMBARI-5729|https://issues.apache.org/jira/browse/AMBARI-5729] solves
> similar issue for NodeManager.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1596) Ability for Ambari Agents to run as non-root users
[ https://issues.apache.org/jira/browse/AMBARI-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-1596: --- Assignee: Dmitry Lysnichenko > Ability for Ambari Agents to run as non-root users > -- > > Key: AMBARI-1596 > URL: https://issues.apache.org/jira/browse/AMBARI-1596 > Project: Ambari > Issue Type: Improvement >Affects Versions: 1.2.2 >Reporter: Jeff Sposetti >Assignee: Dmitry Lysnichenko > Fix For: 2.0.0 > > > Give users the ability to have ambari-agent use a sudo account. > ambari-server non-root is supported: > https://issues.apache.org/jira/browse/AMBARI-2370 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-9608) When adding the Oozie service to a kerberized cluster OOZIE_SERVER doesn't start
[
https://issues.apache.org/jira/browse/AMBARI-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-9608:
---
Assignee: Robert Levas
> When adding the Oozie service to a kerberized cluster OOZIE_SERVER doesn't
> start
>
>
> Key: AMBARI-9608
> URL: https://issues.apache.org/jira/browse/AMBARI-9608
> Project: Ambari
> Issue Type: Bug
> Components: security
>Affects Versions: 2.0.0
>Reporter: John Speidel
>Assignee: Robert Levas
>Priority: Critical
> Labels: keberos
> Fix For: 2.0.0
>
>
> Oozie server fails to start with the error: "Fail: Configuration parameter
> 'oozie.service.HadoopAccessorService.kerberos.principal' was not found in
> configurations dictionary!"
> Steps to reproduce:
> Create a non-kerberized cluster
> I used the following blueprint
> {code}
> {
> "host_groups" : [
> {
> "name" : "host_group_1",
> "components" : [
> {
> "name" : "NODEMANAGER"
> },
> {
> "name" : "NAMENODE"
> },
> {
> "name" : "HISTORYSERVER"
> },
> {
> "name" : "ZOOKEEPER_SERVER"
> },
> {
> "name" : "SECONDARY_NAMENODE"
> },
> {
> "name" : "RESOURCEMANAGER"
> },
> {
> "name" : "APP_TIMELINE_SERVER"
> },
> {
> "name" : "DATANODE"
> },
> {
> "name" : "YARN_CLIENT"
> },
> {
> "name" : "ZOOKEEPER_CLIENT"
> },
> {
> "name" : "MAPREDUCE2_CLIENT"
> }
> ],
> "cardinality" : "1"
> }
> ],
> "Blueprints" : {
> "stack_name" : "HDP",
> "stack_version" : "2.2"
> }
> }
> {code}
> - manually unzip UnlimitedJCEPolicy
> - manually install MIT KDC
> - Using UI, kerberize the existing cluster
> - Using the UI, add the Oozie service
> OOZIE_SERVER failed to start and the above noted exception was from the log
> that is exposed via the UI for the oozie start operation.
> According to Robert Levas this property is in the kerberos descriptor it
> should be set.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-1533) Add Nagios check for ambari-agent process for each host in the cluster
[
https://issues.apache.org/jira/browse/AMBARI-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako reassigned AMBARI-1533:
---
Assignee: Sumit Mohanty
> Add Nagios check for ambari-agent process for each host in the cluster
> --
>
> Key: AMBARI-1533
> URL: https://issues.apache.org/jira/browse/AMBARI-1533
> Project: Ambari
> Issue Type: Improvement
>Reporter: Jeff Sposetti
>Assignee: Sumit Mohanty
> Attachments: AMBARI-1533.patch
>
>
> Each host in the cluster runs ambari-agent.
> There should be a Nagios alert to that watches the ambari-agent process.
> Since the system does not allow direct communication to an ambari-agent, this
> check should either a) check the process running on the host or b) ping the
> Ambari Server REST API to confirm agent is still heartbeat'ing.
> This alert should be shown with each Hosts > {host} in Ambari Web.
> Service Description: Ambari Agent (ambari-agent) process down
> Service Group: AMBARI
> Check / Retry Interval: 0.25
> Note: need to add new service group AMBARI for Nagios
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-13494) Ambari generate invalid configuration after namenode move with HA enabled
[ https://issues.apache.org/jira/browse/AMBARI-13494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13494: Assignee: Josh Elser > Ambari generate invalid configuration after namenode move with HA enabled > - > > Key: AMBARI-13494 > URL: https://issues.apache.org/jira/browse/AMBARI-13494 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.2.0 > > Attachments: AMBARI-13494_branch-2.1.patch > > > Noticed that incorrect Accumulo configuration was generated after HA was > enabled, and then a namenode was moved. > Manually verified that, with the patch, moving a namenode with and without HA > enabled works as expected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-5686) iptables host check warning shows on centos 5.9 even if iptables are stopped
[ https://issues.apache.org/jira/browse/AMBARI-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-5686: --- Assignee: Jonathan Hurley > iptables host check warning shows on centos 5.9 even if iptables are stopped > > > Key: AMBARI-5686 > URL: https://issues.apache.org/jira/browse/AMBARI-5686 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 1.6.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley > Fix For: 1.6.1 > > > While adding a host "am5-unsec-m2-4" Ambari shows firewall error even if the > firewall is stopped on that host > -- > [root@am5-unsec-m2-1 tmp]# rpm -qa | grep ambari > ambari-server-1.6.0-17 > ambari-agent-1.6.0-17 > ambari-log4j-1.6.0.17-1 > [root@am5-unsec-m2-1 tmp]# cat /etc/redhat-release > CentOS release 5.9 (Final) > -- > [root@am5-unsec-m2-4 ~]# service iptables status > Firewall is stopped. > -- -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-13889) Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration
[ https://issues.apache.org/jira/browse/AMBARI-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-13889: Assignee: Josh Elser > Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing > Accumulo configuration > - > > Key: AMBARI-13889 > URL: https://issues.apache.org/jira/browse/AMBARI-13889 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.2.0 > > Attachments: AMBARI-13889.001.patch, AMBARI-13889.002.patch, > AMBARI-13889.002.trunk.patch > > > AMBARI-13295 fixed an issue where, with custom usernames/principals, the > Accumulo client was using the default principal to try to authenticate with > the Accumulo services with Kerberos enabled. This failed as the client had > incorrect information to complete the authentication handshake. > This issue still exists in 2.1.2, however, which causes an upgrade from 2.1.2 > to 2.1.3-SNAPSHOT to fail because the incorrect configuration is never > corrected. > [~rlevas] has kindly pointed that the UpgradeCatalog needs to be changed to > ensure that the configuration is updated in the upgrade path out of 2.1.2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
