[jira] [Updated] (AMBARI-25162) Oozie Service Check fails with : "NameError: global name 'Fail' is not defined"

[ https://issues.apache.org/jira/browse/AMBARI-25162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25162: Labels: pull-request-available (was: ) > Oozie Service Check fails with : "NameError:

[jira] [Updated] (AMBARI-25162) Oozie Service Check fails with : "NameError: global name 'Fail' is not defined"

[ https://issues.apache.org/jira/browse/AMBARI-25162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Chitlangia updated AMBARI-25162: --- Affects Version/s: 2.7.0 > Oozie Service Check fails with : "NameError: global

[jira] [Commented] (AMBARI-25162) Oozie Service Check fails with : "NameError: global name 'Fail' is not defined"

[ https://issues.apache.org/jira/browse/AMBARI-25162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773480#comment-16773480 ] Dinesh Chitlangia commented on AMBARI-25162: Will post a pull-request soon. I am unable to

[jira] [Created] (AMBARI-25162) Oozie Service Check fails with : "NameError: global name 'Fail' is not defined"

Dinesh Chitlangia created AMBARI-25162: -- Summary: Oozie Service Check fails with : "NameError: global name 'Fail' is not defined" Key: AMBARI-25162 URL: https://issues.apache.org/jira/browse/AMBARI-25162

[jira] [Commented] (AMBARI-25063) Restarting Ambari Server Fails Due to Recursive Injection of STOMPUpdatePublisher

[ https://issues.apache.org/jira/browse/AMBARI-25063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773372#comment-16773372 ] Hudson commented on AMBARI-25063: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #428 (See

[jira] [Commented] (AMBARI-25159) http.strict-transport-security change does not take affect in 2.7.x

[ https://issues.apache.org/jira/browse/AMBARI-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773342#comment-16773342 ] Hudson commented on AMBARI-25159: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #427 (See

[jira] [Updated] (AMBARI-25159) http.strict-transport-security change does not take affect in 2.7.x

[ https://issues.apache.org/jira/browse/AMBARI-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25159: Labels: pull-request-available (was: ) > http.strict-transport-security change does not

[jira] [Assigned] (AMBARI-25155) Backport knox trusted proxy support for ambari for 2.6

[ https://issues.apache.org/jira/browse/AMBARI-25155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar reassigned AMBARI-25155: -- Assignee: Attila Magyar > Backport knox trusted proxy support for ambari for 2.6 >

[jira] [Created] (AMBARI-25161) Cluster deploy fails due to Ambari attempting to create `tez.am.view-acls` as users/groups in the OS.

Sean Roberts created AMBARI-25161: - Summary: Cluster deploy fails due to Ambari attempting to create `tez.am.view-acls` as users/groups in the OS. Key: AMBARI-25161 URL:

[jira] [Commented] (AMBARI-25151) Support SystemD integration of Ambari agent with SLES

[ https://issues.apache.org/jira/browse/AMBARI-25151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772820#comment-16772820 ] Hudson commented on AMBARI-25151: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #426 (See

[jira] [Updated] (AMBARI-25160) update non-default config group in "Ambari Infra" Service will send PUT request for HDFS Service(maybe some services else) non-default config group

[ https://issues.apache.org/jira/browse/AMBARI-25160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Wenzhuang updated AMBARI-25160: --- Docs Text: 1. add Config Group named "hdfs_test" in "HDFS" config 2. override some