Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Galleon fails updating 23-->23.0.1 (CentOS 7) #295

Open
pejonsson opened this issue Apr 27, 2021 · 4 comments
Open

Galleon fails updating 23-->23.0.1 (CentOS 7) #295

pejonsson opened this issue Apr 27, 2021 · 4 comments

Comments

@pejonsson
Copy link

Version: galleon-4.2.8.Final

[wildfly]$ update
Feature-packs resolved.
Some updates and/or patches are available.
======= ============= ============ ==============
Product Current Build Update Update Channel
======= ============= ============ ==============
wildfly 23.0.0.Final 23.0.1.Final 23.0

Proceed with latest updates [y/n]?
Feature-packs resolved.
Packages installed.
JBoss modules installed.
Configurations generated.
Replaying your changes on top

  • standalone/log/
  • standalone/coordConfig/
  • modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.18.Fixed.jar
  • standalone/tmp/vfs/
  • modules/system/layers/base/org/jboss/logging/main/jboss-logging-3.4.1.Fixed.jar
  • standalone/configuration/standalone_xml_history/
  • modules/com/
  • modules/org/
  • standalone/data/
  • standalone/ismobile/
    C modules/system/layers/base/org/jboss/logging/main/module.xml
    C standalone/configuration/application-users.properties
    C modules/system/layers/base/org/jboss/logmanager/main/module.xml
    C domain/configuration/mgmt-users.properties
    C standalone/configuration/mgmt-users.properties
    C standalone/configuration/application-roles.properties
    C standalone/configuration/logging.properties
    C domain/configuration/application-roles.properties
    C domain/configuration/application-users.properties
    C standalone/configuration/standalone-full.xml
    Error: Update failed.
  • Failed to copy /tmp/68e33f20-8069-437a-bbe9-bb4524513eb2/staged to /opt/wildfly
@jfdenise
Copy link
Contributor

@pejonsson , it could be an issue with the /opt/wildfly directory. Are you allowed to write to this directory? Adding --verbose could possibly help understand what is going on.

@elrasp
Copy link

elrasp commented Jul 23, 2021

I get the same error when I try to update
Version: galleon-4.2.8.Final
OS: Windows 10

I can confirm that I have write privileges on the target location

[wildfly_galleon]$ install wildfly#18.0.1.Final
Feature-packs resolved.
Packages installed.
JBoss modules installed.
Configurations generated.
Feature pack installed.
======= ============ ==============
Product Build        Update Channel
======= ============ ==============
wildfly 18.0.1.Final current

[wildfly_galleon]$ update
Feature-packs resolved.
Some updates and/or patches are available.
======= ============= ============ ==============
Product Current Build Update       Update Channel
======= ============= ============ ==============
wildfly 18.0.1.Final  24.0.0.Final current

[wildfly_galleon]$ update
Feature-packs resolved.
Some updates and/or patches are available.
======= ============= ============ ==============
Product Current Build Update       Update Channel
======= ============= ============ ==============
wildfly 18.0.1.Final  24.0.0.Final current

Proceed with latest updates [y/n]?
Feature-packs resolved.
Packages installed.
JBoss modules installed.
Configurations generated.
Error: Update failed.
 * Failed to copy <userPath>\AppData\Local\Temp\f56c1afb-8afd-4be7-8e56-71b8c0101558\staged to <dir>\wildfly_galleon


[wildfly_galleon]$

@miminno
Copy link

miminno commented Aug 5, 2021

+1

It fails with 'persist-changes' or 'provision' commands as well if the destination --dir is not empty.
--verbose switch does not reveal any additional information.

The OS is Windows 10, full R/W access to the file system.

@jfdenise
Copy link
Contributor

@miminno , is it something that you observe 100% of the time? Do you observe the same when installing 24.0.0.Final and upgrade to 24.0.1.Final?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants