Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

in-place upgrade using the launcher leaves old jars in place

#554
  • Issue Type: Bug
  • Rundeck version: 1.4.2

Issue:

Upgrading a rundeck server using the launcher can cause incorrect behavior, because the previous version leaves behind some rundeck jar files.


Reproduce:

Install 1.4.2 via the launcher, and start the server.
stop the server.
Install 1.4.3 dev build in the same place and start the server.

there are now rundeck-core-1.4.2.jar and rundeck-core-1.4.3.jar in two locations, the tools/lib dir, and the server/exp/webapp/WEB-INF/lib dir.

Workaround:

Remove the server/exp and tools/lib dir and restart.

Reported by Greg Schueler · April 11th, 2012 @ 09:44 AM

State: resolved
Milestone: Rundeck 1.4.3
Assigned to: Greg Schueler Greg Schueler

Activity

  1. Greg Schueler
    Greg Schueler
    • State changed from open to needs_verification

    (from [e1cc40af2c815b925ca96992914b7d6402368393]) Remove old rundeck-*.jar files on install

    Remove old rundeck jar libs that could cause upgrade issues
    when installing.

    [#554 state:needs_verification] https://github.com/dtolabs/rundeck/commit/e1cc40af2c815b925ca969929...

    April 11th, 2012 @ 10:52 AM

  2. Greg Schueler
    Greg Schueler
    • Milestone order changed from 34 to 0

    after upgrade, the bundled plugins "script-plugin" and "stub-plugin" now exist in libext dir with two versions, and server startup fails to load both plugins

    May 17th, 2012 @ 11:29 AM

  3. Greg Schueler
  4. Greg Schueler
  5. Greg Schueler
  6. Greg Schueler
    Greg Schueler
    • State changed from needs_verification to resolved

    June 21st, 2012 @ 10:16 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.