EAP 6 patch rollback fails after patch 6.2.3 is applied

Solution Verified - Updated -

Issue

We applied 6.2.4 to our JBoss installation running on 6.2.0. Afterwards we try to rollback to 6.2.0 by

  1. jboss-cli.sh --command="patch rollback --patch-id=jboss-eap-6.2.4.CP --reset-configuration=true"
  2. jboss-cli.sh --command="patch rollback --patch-id=jboss-eap-6.2.3.CP --reset-configuration=true"
  3. jboss-cli.sh --command="patch rollback --patch-id=jboss-eap-6.2.2.CP --reset-configuration=true"

This last step will fail with the following error:

java.io.FileNotFoundException: /opt/jboss/modules/system/layers/base/org/jboss/as/web/main/lib/README.txt (No such file or directory)
  • I executed the rollback command but only went from 6.2.4 > 6.2.3. When I ran rollback again, i went from 6.2.3 > 6.2.2. When i tried
    rolling back from 6.2.2 i get an error:
[domain@localhost:9999 /] patch rollback --patch-id=jboss-eap-6.2.2.CP  --host=slave --reset-configuration=TRUE       
{"host-failure-descriptions" => [("slave" => "java.io.FileNotFoundException: /opt/app/jboss/jboss-eap/modules/system/layers/base/org/jboss/as/web/main/lib/README.txt (No such file or directory)")]}                                          

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.2 cp2
    • 6.2 cp3
    • 6.2 cp4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content