[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Attachment: AMBARI-21137.patch > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21137.patch > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Status: Patch Available (was: In Progress) > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21137.patch > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Attachment: (was: AMBARI-21137.patch) > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Status: Open (was: Patch Available) > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file
[ https://issues.apache.org/jira/browse/AMBARI-21132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21132: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Export cluster_name in the cluster template file > > > Key: AMBARI-21132 > URL: https://issues.apache.org/jira/browse/AMBARI-21132 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21132.patch > > > Blueprint export from UI installer currently does not export cluster_name in > the clustertemplate file. Adding patch to export the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Fix Version/s: trunk Status: Patch Available (was: In Progress) > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21137.patch > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
[ https://issues.apache.org/jira/browse/AMBARI-21137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21137: --- Attachment: AMBARI-21137.patch > Blueprint export should allow tokenized values in SingleHostUpdater > --- > > Key: AMBARI-21137 > URL: https://issues.apache.org/jira/browse/AMBARI-21137 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-21137.patch > > > During upgrade Biginsights stack tokenizes value for > 'yarn.resourcemanager.webapp.https.address', therefore this property gets > removed by SingleHostUpdater during blueprint export. Next time when the > blueprint is used to create a cluster, this property is assigned default > value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21137) Blueprint export should allow tokenized values in SingleHostUpdater
Amruta Borkar created AMBARI-21137: -- Summary: Blueprint export should allow tokenized values in SingleHostUpdater Key: AMBARI-21137 URL: https://issues.apache.org/jira/browse/AMBARI-21137 Project: Ambari Issue Type: Bug Reporter: Amruta Borkar Assignee: Amruta Borkar During upgrade Biginsights stack tokenizes value for 'yarn.resourcemanager.webapp.https.address', therefore this property gets removed by SingleHostUpdater during blueprint export. Next time when the blueprint is used to create a cluster, this property is assigned default value 'localhost' and exception is thrown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back button
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Customize services shows inconsistent config-groups after clicking on Back > button > - > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file
[ https://issues.apache.org/jira/browse/AMBARI-21132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21132: --- Description: Blueprint export from UI installer currently does not export cluster_name in the clustertemplate file. Adding patch to export the same. > Export cluster_name in the cluster template file > > > Key: AMBARI-21132 > URL: https://issues.apache.org/jira/browse/AMBARI-21132 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21132.patch > > > Blueprint export from UI installer currently does not export cluster_name in > the clustertemplate file. Adding patch to export the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file
[ https://issues.apache.org/jira/browse/AMBARI-21132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21132: --- Attachment: AMBARI-21132.patch > Export cluster_name in the cluster template file > > > Key: AMBARI-21132 > URL: https://issues.apache.org/jira/browse/AMBARI-21132 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21132.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file
[ https://issues.apache.org/jira/browse/AMBARI-21132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21132: --- Status: Patch Available (was: In Progress) > Export cluster_name in the cluster template file > > > Key: AMBARI-21132 > URL: https://issues.apache.org/jira/browse/AMBARI-21132 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21132.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21132) Export cluster_name in the cluster template file
Amruta Borkar created AMBARI-21132: -- Summary: Export cluster_name in the cluster template file Key: AMBARI-21132 URL: https://issues.apache.org/jira/browse/AMBARI-21132 Project: Ambari Issue Type: Technical task Components: ambari-web Reporter: Amruta Borkar Assignee: Amruta Borkar Priority: Minor Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-21104. Resolution: Fixed > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-21104.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: (was: AMBARI-21104_1.patch) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: (was: AMBARI-21104.patch) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Open (was: Patch Available) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-21104_1.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Patch Available (was: In Progress) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Open (was: Patch Available) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back button
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Summary: Customize services shows inconsistent config-groups after clicking on Back button (was: Customize services shows inconsistent config-groups after clicking on Back) > Customize services shows inconsistent config-groups after clicking on Back > button > - > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Patch Available (was: In Progress) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-21104.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: (was: AMBARI-20944.patch) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Open (was: Patch Available) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Patch Available (was: In Progress) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20944.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-20944.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20944.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
Amruta Borkar created AMBARI-21104: -- Summary: Add Confirmation pop up for 'Generate Blueprint' button Key: AMBARI-21104 URL: https://issues.apache.org/jira/browse/AMBARI-21104 Project: Ambari Issue Type: Technical task Components: ambari-web Reporter: Amruta Borkar Assignee: Amruta Borkar Fix For: trunk Add Confirmation pop up for 'Generate Blueprint' button. Notify user that two files will be downloaded and provide information on how to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Status: Patch Available (was: In Progress) > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Status: Open (was: Patch Available) > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Fix Version/s: trunk > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Attachment: AMBARI-21094.patch > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Status: Patch Available (was: In Progress) > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
Amruta Borkar created AMBARI-21094: -- Summary: Customize services shows inconsistent config-groups after clicking on Back Key: AMBARI-21094 URL: https://issues.apache.org/jira/browse/AMBARI-21094 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Amruta Borkar Assignee: Amruta Borkar Steps to reproduce: 1. Go to Customize Services screen 2. Create a Custom HostGroup 3. Click Back button 4. Click Next Button 5. See that Custom Hostgroup still exists, but all the data including assigned hosts is erased. Ambari typically erases all the changes when clicked on Back button, because the Custom HostGroup is not deleted but data related to it is deleted by Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Status: Patch Available (was: In Progress) > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050_1.patch, AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Attachment: AMBARI-21050_1.patch > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050_1.patch, AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Status: Open (was: Patch Available) > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Status: Open (was: Patch Available) > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Status: Patch Available (was: In Progress) > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21049) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-21049. Resolution: Fixed > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21049 > URL: https://issues.apache.org/jira/browse/AMBARI-21049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-21049) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar reopened AMBARI-21049: > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21049 > URL: https://issues.apache.org/jira/browse/AMBARI-21049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Status: Patch Available (was: In Progress) > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21050) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21050: --- Attachment: AMBARI-21050.patch > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21050 > URL: https://issues.apache.org/jira/browse/AMBARI-21050 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21050.patch > > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21049) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-21049. Resolution: Duplicate > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21049 > URL: https://issues.apache.org/jira/browse/AMBARI-21049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-21049) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar reopened AMBARI-21049: > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21049 > URL: https://issues.apache.org/jira/browse/AMBARI-21049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21049) Address config-groups while exporting blueprint from UI
[ https://issues.apache.org/jira/browse/AMBARI-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-21049. Resolution: Fixed > Address config-groups while exporting blueprint from UI > > > Key: AMBARI-21049 > URL: https://issues.apache.org/jira/browse/AMBARI-21049 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > > Exported blueprint should include config-group changes, which should be > exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21050) Address config-groups while exporting blueprint from UI
Amruta Borkar created AMBARI-21050: -- Summary: Address config-groups while exporting blueprint from UI Key: AMBARI-21050 URL: https://issues.apache.org/jira/browse/AMBARI-21050 Project: Ambari Issue Type: Technical task Components: ambari-web Affects Versions: trunk Reporter: Amruta Borkar Assignee: Amruta Borkar Exported blueprint should include config-group changes, which should be exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21049) Address config-groups while exporting blueprint from UI
Amruta Borkar created AMBARI-21049: -- Summary: Address config-groups while exporting blueprint from UI Key: AMBARI-21049 URL: https://issues.apache.org/jira/browse/AMBARI-21049 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Amruta Borkar Assignee: Amruta Borkar Exported blueprint should include config-group changes, which should be exported as host-group level configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-15406) Enhance blueprints to export placeholder/token for password properties
[ https://issues.apache.org/jira/browse/AMBARI-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-15406. Resolution: Unresolved > Enhance blueprints to export placeholder/token for password properties > -- > > Key: AMBARI-15406 > URL: https://issues.apache.org/jira/browse/AMBARI-15406 > Project: Ambari > Issue Type: Technical task > Components: ambari-server, blueprints >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-15406.patch, AMBARI-15406.patch, > AMBARI-15406.patch > > > Secret References acting as tokens to password properties would be replaced > by user with appropriate passwords, > If any Secret references are found during cluster deployment with blueprint, > those will be replaced by default_password provided in blueprint template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15406) Enhance blueprints to export placeholder/token for password properties
[ https://issues.apache.org/jira/browse/AMBARI-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15406: --- Status: Open (was: Patch Available) > Enhance blueprints to export placeholder/token for password properties > -- > > Key: AMBARI-15406 > URL: https://issues.apache.org/jira/browse/AMBARI-15406 > Project: Ambari > Issue Type: Technical task > Components: ambari-server, blueprints >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-15406.patch, AMBARI-15406.patch, > AMBARI-15406.patch > > > Secret References acting as tokens to password properties would be replaced > by user with appropriate passwords, > If any Secret references are found during cluster deployment with blueprint, > those will be replaced by default_password provided in blueprint template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20192) HostCleaup.py throws exception and exits when hostcheck_custom_actions.result not present
[ https://issues.apache.org/jira/browse/AMBARI-20192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-20192. Resolution: Invalid > HostCleaup.py throws exception and exits when hostcheck_custom_actions.result > not present > - > > Key: AMBARI-20192 > URL: https://issues.apache.org/jira/browse/AMBARI-20192 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20192.patch > > > HostCleanup script throws following exception and exits when > hostcheck_custom_actions.result not present > [root@tsar1 ~]# /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py > You have elected to remove all users as well. If it is not intended then use > option --skip "users". Do you want to continue [y/n] (y)y > Host Check results not found. There is no > /var/lib/ambari-agent/data/hostcheck_custom_actions.result. Do you want to > run host checks [y/n] (y)n > Traceback (most recent call last): > File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line > 705, in > main() > File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line > 689, in main > with open(hostcheckfileca, "rb") as f2: > IOError: [Errno 2] No such file or directory: > '/var/lib/ambari-agent/data/hostcheck_custom_actions.result' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20192) HostCleaup.py throws exception and exits when hostcheck_custom_actions.result not present
[ https://issues.apache.org/jira/browse/AMBARI-20192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20192: --- Status: Open (was: Patch Available) > HostCleaup.py throws exception and exits when hostcheck_custom_actions.result > not present > - > > Key: AMBARI-20192 > URL: https://issues.apache.org/jira/browse/AMBARI-20192 > Project: Ambari > Issue Type: Bug >Reporter: Amruta Borkar >Assignee: Amruta Borkar >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20192.patch > > > HostCleanup script throws following exception and exits when > hostcheck_custom_actions.result not present > [root@tsar1 ~]# /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py > You have elected to remove all users as well. If it is not intended then use > option --skip "users". Do you want to continue [y/n] (y)y > Host Check results not found. There is no > /var/lib/ambari-agent/data/hostcheck_custom_actions.result. Do you want to > run host checks [y/n] (y)n > Traceback (most recent call last): > File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line > 705, in > main() > File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line > 689, in main > with open(hostcheckfileca, "rb") as f2: > IOError: [Errno 2] No such file or directory: > '/var/lib/ambari-agent/data/hostcheck_custom_actions.result' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Patch Available (was: In Progress) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: AMBARI-20698.patch > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: (was: AMBARI-20698.patch) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: Generate blueprint via Ambari Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Open (was: Patch Available) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: Generate blueprint via Ambari Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Patch Available (was: In Progress) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: AMBARI-20698.patch > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: (was: AMBARI-20698.patch) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Open (was: Patch Available) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Patch Available (was: Open) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: AMBARI-20698.patch > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: (was: AMBARI-20698.patch) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: Generate blueprint via Ambari Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Open (was: Patch Available) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: Generate blueprint via Ambari Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993317#comment-15993317 ] Amruta Borkar commented on AMBARI-20366: This test failure does not look related to this patch. > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: In Progress) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Summary: Ability to export blueprint via Ambari installer UI (was: Able to export blueprint via Ambari installer UI) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Able to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Patch Available (was: In Progress) > Able to export blueprint via Ambari installer UI > > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Able to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: AMBARI-20698.patch > Able to export blueprint via Ambari installer UI > > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Description: If blueprint is exported from a kerberos enabled cluster Kerberos rules export principal names which contain cluster name and Realm, this patch filter out kerberos rules properties so that hardcoded cluster name and realm are not exported. (was: If blueprint is exported from a kerberos enabled cluster Kerberos rules export principal names which contain cluster name and Realm, this exports existing cluster name and realm name as tokens and replaces those tokens with new values of cluster name and realm during successive cluster deployments.) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Summary: Filter out kerberos rules in exported blueprint (was: Tokenize kerberos principal name appearing in kerberos rules in exported blueprint) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: In Progress) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: In Progress) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Patch Available (was: In Progress) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Open (was: Patch Available) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: AMBARI-20551.patch > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: (was: AMBARI-20551.patch) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: AMBARI-20551.patch > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Open (was: Patch Available) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: (was: AMBARI-20551.patch) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Patch Available (was: In Progress) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: In Progress) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Patch Available (was: In Progress) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Status: Open (was: Patch Available) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: AMBARI-20551.patch > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20551.patch > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20551: --- Attachment: (was: AMBARI-20551.patch) > Blueprint export fails if config-type is not mapped to any service after > upgrade > > > Key: AMBARI-20551 > URL: https://issues.apache.org/jira/browse/AMBARI-20551 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - > Bad request: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186) > at > org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91) > at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar resolved AMBARI-20386. Resolution: Won't Fix > Kerberos principal creation fails during blueprint install when kdc_hosts is > not specified in blueprint > --- > > Key: AMBARI-20386 > URL: https://issues.apache.org/jira/browse/AMBARI-20386 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20386.patch, AMBARI-20386_v2.patch, > AMBARI-20386_v3.patch > > > Blueprint validation does not prompt if kdc_hosts is not specified in the > blueprint. After service installation, deployment fails during Create > Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
