| Summary: | [GSS](6.4.z) Error while applying CP12 patch in windows environment through CLI command. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Abhijit humbe <abhumbe> |
| Component: | Patching | Assignee: | Radovan Netuka <rnetuka> |
| Status: | CLOSED WONTFIX | QA Contact: | Jiří Bílek <jbilek> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.12 | CC: | bmaxwell, brian.stansberry, jason.greene, jawilson, jbilek, jdoyle, kconner, mgoldman, mkopecky, msimka, olubyans, ppenicka, rhatlapa, rnetuka |
| Target Milestone: | CR1 | ||
| Target Release: | EAP 6.4.15 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-02 15:47:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1450092, 1458672 | ||
*** Bug 1440062 has been marked as a duplicate of this bug. *** Applying patch CP12 gets expected error message, but applying CP15 in CP11 gets error message "patching exception" and applying CP15 in CP14 gets another different error message. Output is below.
Applying CP15 should not get any error message in CP11 nor CP14 -> Reopened
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch info"
{
"outcome" : "success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.4.9.CP",
"patches" : []
}
}
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch apply ..\..\jboss-eap-6.4.12-patch.zip"
{
"outcome" : "success",
"result" : {}
}
'org.jboss.as.cli' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch rollback --reset-configuration=false"
{
"outcome" : "success",
"result" : {}
}
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch info"
{
"outcome" : "success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.4.11.CP",
"patches" : []
}
}
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch apply ..\..\jboss-eap-6.4.15.CP.CR2-patch.zip"
{
"outcome" : "success",
"result" : {}
}
patching exception
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch rollback --reset-configuration=false"
{
"outcome" : "success",
"result" : {}
}
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch info"
{
"outcome" : "success",
"result" : {
"cumulative-patch-id" : "jboss-eap-6.4.14.CP",
"patches" : []
}
}
C:\Users\Administrator\Desktop\jboss-eap-6.4.0\jboss-eap-6.4>bin\jboss-cli.bat "--command=patch apply ..\..\jboss-eap-6.4.15.CP.CR2-patch.zip"
{
"outcome" : "success",
"result" : {}
}
'cter' is not recognized as an internal or external command,
operable program or batch file.
patching exception
|
Description of problem: Below exception occurs while applying CP12 patch in windows environment. ~~~ D:\install\jboss-eap-6.4>bin\jboss-cli.bat "patch apply D:\install\jboss- eap-6.4.12-patch.zip" { "outcome" : "success", "result" : {} } 'org.jboss.as.cli' is not recognized as an internal or external command, operable program or batch file. ~~~ Version-Release number of selected component (if applicable): JBoss EAP 6.4 CP12 How reproducible: In Windows environment. Steps to Reproduce: 1.Download JBoss EAP 6.4.0 and apply JBoss EAP 6.4 CP09 patch first. 2.Now try to apply JBoss EAP 6.4 CP12 patch it will throw exception: ~~~ 'org.jboss.as.cli' is not recognized as an internal or external command, operable program or batch file. ~~~ Actual results: Expected results: Additional info: Patch is applied successfully but it throws exception. This issue occurs only when we try to apply patch through CLI command. It works fine if we apply patch through management console.