[jira] [Updated] (AMBARI-19546) Add support for call context to the stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-19546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19546: --- Status: Patch Available (was: Open) > Add support for call context to the stack advisor > - > > Key: AMBARI-19546 > URL: https://issues.apache.org/jira/browse/AMBARI-19546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19546.patch > > > Add support for call context to stack advisor. > Stack advisor coding will be simpler if the calls are aware of the context > with which calls are being made. > Some of the context are: > * Fresh install > * Config editing (landing on a config page) > * Compute attributes > * Add service > * Delete service > * Enable kerberos > * Enable HA > The plan is to add some context fields that can be populated by the caller of > stack recommendation APIs and consumed by the stack advisor code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19546) Add support for call context to the stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-19546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19546: --- Attachment: AMBARI-19546.patch > Add support for call context to the stack advisor > - > > Key: AMBARI-19546 > URL: https://issues.apache.org/jira/browse/AMBARI-19546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19546.patch > > > Add support for call context to stack advisor. > Stack advisor coding will be simpler if the calls are aware of the context > with which calls are being made. > Some of the context are: > * Fresh install > * Config editing (landing on a config page) > * Compute attributes > * Add service > * Delete service > * Enable kerberos > * Enable HA > The plan is to add some context fields that can be populated by the caller of > stack recommendation APIs and consumed by the stack advisor code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16365) Quicken Customer Support Phone Number **))1_844.231_5378=Quicken Tech Support Phone Number USA CANADA
[ https://issues.apache.org/jira/browse/AMBARI-16365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-16365. Resolution: Invalid > Quicken Customer Support Phone Number **))1_844.231_5378=Quicken Tech Support > Phone Number USA CANADA > - > > Key: AMBARI-16365 > URL: https://issues.apache.org/jira/browse/AMBARI-16365 > Project: Ambari > Issue Type: Bug > Components: 2.2.1 >Affects Versions: ambari-186 > Environment: Quickbooks =@@===1-8OO 86O 923O===@@Quickbooks > customer sup.port ph.one num.ber with Quickbooks pro customer sup.port > ph.onenum.ber USAAA here. 1-8OO-86O-923O QuickBooks Enterprise tech sup.port > ph.onenum.ber,..QuickBooks payroll customer sup.port num.ber > Helpline..1-8OO-86O-923O QuickBooks Enterprise sup.port > ph.onenum.ber,..QuickBooks payroll technical sup.port num.ber > File:Helpline..1-8OO-86O-923O QuickBooks Enterprise customer sup.port > num.ber, QuickBooks Enterprise technical sup.port ph.onenum.ber.pdf. > File:Helpline..1-8OO-86O-923O QuickBooks Enterprise sup.port > num.ber,..QuickBooks tech sup.port ph.onenum.ber.pdf. JUST > QB_QB>>>@@(1-8OO-86O-923O) QuickBooks Tech sup.port ph.onenum.ber > 1-8OO-86O-923O,QuickBooks Tech sup.port ph.onenum.ber,, @@, Enterprisevides > online solution for all USA/CANADA clients. For any help of query call 1 8OO > 86O 923O to get all QuickBooks account solution. @@Call, 1-8OO-86O-923O for > all type help by QuickBooks tech sup.port ph.onenum.ber, Intuit QuickBooks > Tech sup.port ph.onenum.ber, QuickBooks Help Desk ph.onenum.ber, QuickBooks > tech sup.port num.ber, QuickBooks technical sup.port ph.onenum.ber,@@@ > QuickBooks ph.onenum.ber, QuickBooks technical sup.port num.ber, QuickBooks > sup.port ph.onenum.ber, QuickBooks technical sup.port, QuickBooks Customer > Service ph.onenum.ber, QuickBooks Customer Service num.ber, QuickBooks > Customer sup.port ph.onenum.ber, QuickBooks Customer sup.port num.ber, > QuickBooks Customer Service Helpline num.ber, QuickBooks Customer Care > num.ber, QuickBooks sup.port team ph.onenum.ber, @ QuickBooks help > num.ber-QuickBooks Helpline num.ber; QuickBooks help ph.onenum.ber-QuickBooks > Helpline num.ber, QuickBooks Tech sup.port Toll free num.ber, QuickBooks > sup.port Teleph.onenum.ber, QuickBooks Tech sup.port Teleph.onenum.ber, > QuickBooks Tech sup.port contact num.ber, QuickBooks sup.port contact > num.ber, QuickBooks technical sup.port contact num.ber. Call, QuickBooks tech > sup.port ph.onenum.ber, Intuit QuickBooks Tech sup.port ph.onenum.ber, > QuickBooks Help Desk ph.onenum.ber, QuickBooks tech sup.port num.ber, > QuickBooks technical sup.port ph.onenum.ber, QuickBooks ph.onenum.ber, > QuickBooks technical sup.port num.ber, QuickBooks sup.port ph.onenum.ber. It > is very popular toll free num.ber which Enterprisevide by QuickBooks > technical sup.port, QuickBooks Customer Service ph.onenum.ber, QuickBooks > Customer Service num.ber, QuickBooks Customer sup.port ph.onenum.ber, > QuickBooks Customer sup.port num.ber, QuickBooks Customer Service Helpline > num.ber, QuickBooks Customer Care num.ber, QuickBooks sup.port team > ph.onenum.ber. Call, QuickBooks tech sup.port ph.onenum.ber, Intuit > QuickBooks Tech sup.port ph.onenum.ber, QuickBooks Help Desk ph.onenum.ber, > QuickBooks tech sup.port num.ber, QuickBooks technical sup.port > ph.onenum.ber, QuickBooks ph.onenum.ber, QuickBooks technical sup.port > num.ber, QuickBooks sup.port ph.onenum.ber, QuickBooks technical sup.port, > QuickBooks Customer Service ph.onenum.ber, QuickBooks Customer Service > num.ber, QuickBooks Customer sup.port ph.onenum.ber, QuickBooks Customer > sup.port num.ber, QuickBooks Customer Service Helpline num.ber, QuickBooks > Customer Care num.ber, QuickBooks sup.port team ph.onenum.ber, QuickBooks > help num.ber-QuickBooks Helpline num.ber; QuickBooks help ph.onenum.ber, > QuickBooks Helpline num.ber, QuickBooks Tech sup.port Toll free num.ber, > QuickBooks sup.port Teleph.onenum.ber, QuickBooks Tech sup.port > Teleph.onenum.ber, QuickBooks Tech sup.port contact num.ber, QuickBooks > sup.port contact num.ber, QuickBooks technical sup.port contact num.ber, > quickbooks Enterprise sup.port ph.onenum.ber, quickbooks payroll sup.port > ph.onenum.ber. quickbooks payroll customer sup.port ph.onenum.ber > 18OO-86O-923O quickbooks technical help teleph.onenum.ber, quickbooks > technical help contact num.ber, quickbooks technical sup.port contact > num.ber, quickbooks contact num.ber, quickbooks contact ph.onenum.ber, > quickbooks contact teleph.onenum.ber, quickbooks 24 hour contact num.ber, > quickbooks customer sup.port contact num.ber, quickbooks customer service > contact num.ber,
[jira] [Updated] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location
[ https://issues.apache.org/jira/browse/AMBARI-19545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-19545: --- Status: Patch Available (was: Open) > Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired > location > -- > > Key: AMBARI-19545 > URL: https://issues.apache.org/jira/browse/AMBARI-19545 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.5.0 > > Attachments: rb55538.patch > > > Ambari agent generates the JCEKS provider files as > /var/lib/ambari-agent/cred/conf//.jceks. > OOZIE and HIVE scripts should specify a location of their choice and set the > desired ACLs, instead of using the default location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location
[ https://issues.apache.org/jira/browse/AMBARI-19545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-19545: --- Attachment: rb55538.patch > Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired > location > -- > > Key: AMBARI-19545 > URL: https://issues.apache.org/jira/browse/AMBARI-19545 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.5.0 > > Attachments: rb55538.patch > > > Ambari agent generates the JCEKS provider files as > /var/lib/ambari-agent/cred/conf//.jceks. > OOZIE and HIVE scripts should specify a location of their choice and set the > desired ACLs, instead of using the default location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19545) Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location
Nahappan Somasundaram created AMBARI-19545: -- Summary: Ambari-agent: In HIVE and OOZIE stack scripts, copy JCEKS file to desired location Key: AMBARI-19545 URL: https://issues.apache.org/jira/browse/AMBARI-19545 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.5.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Priority: Critical Fix For: 2.5.0 Ambari agent generates the JCEKS provider files as /var/lib/ambari-agent/cred/conf//.jceks. OOZIE and HIVE scripts should specify a location of their choice and set the desired ACLs, instead of using the default location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19527) Downgrade executes section if is not defined
[ https://issues.apache.org/jira/browse/AMBARI-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19527: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Downgrade executes section if is not defined > -- > > Key: AMBARI-19527 > URL: https://issues.apache.org/jira/browse/AMBARI-19527 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19527_1.patch > > > When creating the initial upgrade packs, an effort was made to make them as > least-verbose as possible. In that, we assumed that all tasks that occurred > during an Upgrade would also occur on a Downgrade. That assumption led to > some sneaky bugs that are difficult to troubleshoot. > The real fix is to make the XSD enforce "sibling" elements, such that when > PRE-UPGRADE tasks are defined, you can enforce that a PRE-DOWNGRADE element > exist. Unfortunately, the JDK (even 1.8) doesn't support that version of XSD > in JAXB. > The interim solution was to use the afterUnmarshal secret sauce to validate > that the elements exist. Allow a pre-downgrade or post-downgrade element to > indicate that it can reuse the (pre-post)upgrade element definitions. > Many of the changes here are in upgrade packs to add the new required > elements, and the unit test that parses all upgrade packs passes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Attachment: AMBARI-19415.1.patch
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch, AMBARI-19415.1.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
