fabric:delete-version does not always work correctly in Fuse 6.1/Fabric8

Solution Verified - Updated -

Issue

Red Hat JBoss Fuse 6.1.0 GA; Fabric8 1.1.0.Beta6: version-delete has no effect, when a fabric and containers have been created.

Steps to reproduce:

> fabric:create --wait-for-provisioning
> container-create-child root test1
> container-create-child root test2

(wait for child containers to provision)

> version-list
[version]       [default] [# containers]
1.0             true      3

> version-create
Created version: 1.1 as copy of: 1.0

> version-delete 1.1

> version-list
[version]       [default] [# containers]
1.0             true      3
1.1             false     0

This situation is potentially problematic if a version-create is issued without specifying a parent, as it may create a version derived from one that is assumed to have been deleted.

Fabric8 versions later than 1.1.0-Beta6 and later also show problems related to version-delete, but the symptoms are not necessarily exactly the same.

  • When executing the 'version-delete' command on a fabric version, sometimes the version does not get permanently deleted. If I run a version-list right after the command, the version is gone. However, a few seconds later it shows up. Sometimes stopping and starting the container and retrying the command will allow the command to succeed. No logs are seen during the action in karaf.log or external git commit log.

Environment

  • Red Hat JBoss Fuse
    • 6.1 GA
  • Fabric8
    • 1.1.0.Beta6 and later

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