Project

General

Profile

Actions

Bug #28402

closed

Foreman Azure not installable

Added by Adam Cécile over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Hello,

Here is what happens when installing ruby-foreman-azure on Debian Buster running Foreman 1.23.1:

# apt-get install ruby-foreman-azure
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  ruby-foreman-deface
The following NEW packages will be installed:
  ruby-foreman-azure ruby-foreman-deface
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/239 kB of archives.
After this operation, 345 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package ruby-foreman-deface.
(Reading database ... 86523 files and directories currently installed.)
Preparing to unpack .../ruby-foreman-deface_1.5.0-1_all.deb ...
Unpacking ruby-foreman-deface (1.5.0-1) ...
Selecting previously unselected package ruby-foreman-azure.
Preparing to unpack .../ruby-foreman-azure_1.3.1-1_all.deb ...
Unpacking ruby-foreman-azure (1.3.1-1) ...
Setting up ruby-foreman-deface (1.5.0-1) ...
dpkg: error processing package ruby-foreman-deface (--configure):
 subprocess installed post-installation script returned error exit status 6
dpkg: dependency problems prevent configuration of ruby-foreman-azure:
 ruby-foreman-azure depends on ruby-foreman-deface (<< 2.0.0); however:
  Package ruby-foreman-deface is not configured yet.

dpkg: error processing package ruby-foreman-azure (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 ruby-foreman-deface
 ruby-foreman-azure
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I added -x to /bin/sh in /var/lib/dpkg/info/ruby-foreman-deface.postinst and run apt -f install

+ export HOME=/usr/share/foreman
+ cd /usr/share/foreman
+ [ ! -z  ]
+ [ -n  ]
+ /usr/bin/foreman-ruby /usr/bin/bundle install --local --no-prune
+ db_stop
+ echo STOP
dpkg: error processing package ruby-foreman-deface (--configure):

That's interresting, let's try to call bundle by hand:

HOME=/usr/share/foreman /usr/bin/foreman-ruby /usr/bin/bundle install --local --no-prune
Some gems seem to be missing from your vendor/cache directory.
Bundler could not find compatible versions for gem "fog-core":
  In snapshot (Gemfile.lock):
    fog-core (= 2.1.0)

  In Gemfile:
    fog-core (= 2.1.0)

    foreman_azure (= 1.3.1) was resolved to 1.3.1, which depends on
      fog-azure (= 0.0.2) was resolved to 0.0.2, which depends on
        fog-core (~> 1.27)

    fog-google (~> 1.8.2) was resolved to 1.8.2, which depends on
      fog-core (<= 2.1.0)

    fog-openstack (< 2.0.0, >= 1.0.8) was resolved to 1.0.10, which depends on
      fog-core (~> 2.1)

    fog-openstack (< 2.0.0, >= 1.0.8) was resolved to 1.0.10, which depends on
      fog-core (~> 2.1)

    foreman_azure (= 1.3.1) was resolved to 1.3.1, which depends on
      fog-azure (= 0.0.2) was resolved to 0.0.2, which depends on
        fog-xml (~> 0.1) was resolved to 0.1.3, which depends on
          fog-core

    foreman_azure (= 1.3.1) was resolved to 1.3.1, which depends on
      fog-azure (= 0.0.2) was resolved to 0.0.2, which depends on
        fog-xml (~> 0.1) was resolved to 0.1.3, which depends on
          fog-core

    foreman_azure (= 1.3.1) was resolved to 1.3.1, which depends on
      fog-azure (= 0.0.2) was resolved to 0.0.2, which depends on
        fog-xml (~> 0.1) was resolved to 0.1.3, which depends on
          fog-core

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

I can provide additional information if that can help.

Regards, Adam

Actions #1

Updated by Adam Cécile over 4 years ago

  • Description updated (diff)
Actions #2

Updated by Tomer Brisker over 4 years ago

  • Project changed from Foreman to AzureRM
  • Category deleted (Compute resources)

Foreman azure plugin has been deprecated as the azure api has changed and the plugin hasn't been updated for a long time for compatibility with Foreman core.
Support for azure provisioning will be coming back in 1.24 (to be released shortly) using the foreman_azure_rm plugin. Moving this issue to the plugin for further support if needed, or feel free to close it once you have upgrade to 1.24 and configured the new plugin.

Actions #3

Updated by Aditi Puntambekar about 4 years ago

  • Status changed from New to Closed

Hope your issue has been resolved with the above comment. If you still face any similar error, feel free to open this issue. Closing it now.

Actions

Also available in: Atom PDF