PDA

View Full Version : install-suse-cloud failure



jfonseca
15-May-2016, 21:20
Hi,

While deploying SUSE OpenStack Cloud 6, I got stuck with the following error:

================================================== ==============================
Error executing action `install` on resource 'package[ruby2.1-rubygem-cstruct]'
================================================== ==============================

Chef::Exceptions::Package
-------------------------
zypper failed - #<Process::Status: pid 9711 exit 4>!

Cookbook Trace:
---------------
/var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in `from_file'

Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/ohai/recipes/default.rb

70: package(pkg).run_action(:install)
71:

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in `from_file'

package("ruby2.1-rubygem-cstruct") do
action :install
retries 0
retry_delay 2
package_name "ruby2.1-rubygem-cstruct"
cookbook_name "ohai"
recipe_name "default"
end


================================================== ==============================
Recipe Compile Error in /var/chef/cache/cookbooks/ohai/recipes/default.rb
================================================== ==============================

Chef::Exceptions::Package
-------------------------
package[ruby2.1-rubygem-cstruct] (ohai::default line 70) had an error: Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 9711 exit 4>!

Cookbook Trace:
---------------
/var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in `from_file'

Relevant File Content:
----------------------
/var/chef/cache/cookbooks/ohai/recipes/default.rb:

63: # ruby&rails), we need to run the new cookbook with the old ruby&rails once,
64: # so we need to support this
65: if node["languages"]["ruby"]["version"].to_f == 1.8
66: pkg = "rubygem-cstruct"
67: else
68: pkg = "ruby#{node["languages"]["ruby"]["version"].to_f}-rubygem-cstruct"
69: end
70>> package(pkg).run_action(:install)
71:
72: begin
73: require "cstruct"
74: rescue LoadError
75: # After installation of the gem, we have a new path for the new gem, so
76: # we need to reset the paths if we can't load cstruct
77: Gem.clear_paths
78: end
79:

[2016-05-15T22:14:26+02:00] ERROR: Running exception handlers
[2016-05-15T22:14:26+02:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2016-05-15T22:14:26+02:00] ERROR: Exception handlers complete
[2016-05-15T22:14:26+02:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-05-15T22:14:26+02:00] FATAL: Chef::Exceptions::Package: package[ruby2.1-rubygem-cstruct] (ohai::default line 70) had an error: Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 9711 exit 4>!

Any idea?

Thanks in advance!

smflood
15-May-2016, 21:53
jfonseca Wrote in message:

> While deploying SUSE OpenStack Cloud 6, I got stuck with the following
> error:
>
> ================================================== ==============================
> Error executing action `install` on resource
> 'package[ruby2.1-rubygem-cstruct]'
> ================================================== ==============================
>
> Chef::Exceptions::Package
> -------------------------
> zypper failed - #<Process::Status: pid 9711 exit 4>!
>
> Cookbook Trace:
> ---------------
> /var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in `from_file'
>
> Resource Declaration:
> ---------------------
> # In /var/chef/cache/cookbooks/ohai/recipes/default.rb
>
> 70: package(pkg).run_action(:install)
> 71:
>
> Compiled Resource:
> ------------------
> # Declared in /var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in
> `from_file'
>
> package("ruby2.1-rubygem-cstruct") do
> action :install
> retries 0
> retry_delay 2
> package_name "ruby2.1-rubygem-cstruct"
> cookbook_name "ohai"
> recipe_name "default"
> end
>
>
> ================================================== ==============================
> Recipe Compile Error in
> /var/chef/cache/cookbooks/ohai/recipes/default.rb
> ================================================== ==============================
>
> Chef::Exceptions::Package
> -------------------------
> package[ruby2.1-rubygem-cstruct] (ohai::default line 70) had an error:
> Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 9711
> exit 4>!
>
> Cookbook Trace:
> ---------------
> /var/chef/cache/cookbooks/ohai/recipes/default.rb:70:in `from_file'
>
> Relevant File Content:
> ----------------------
> /var/chef/cache/cookbooks/ohai/recipes/default.rb:
>
> 63: # ruby&rails), we need to run the new cookbook with the old
> ruby&rails once,
> 64: # so we need to support this
> 65: if node["languages"]["ruby"]["version"].to_f == 1.8
> 66: pkg = "rubygem-cstruct"
> 67: else
> 68: pkg =
> "ruby#{node["languages"]["ruby"]["version"].to_f}-rubygem-cstruct"
> 69: end
> 70>> package(pkg).run_action(:install)
> 71:
> 72: begin
> 73: require "cstruct"
> 74: rescue LoadError
> 75: # After installation of the gem, we have a new path for the
> new gem, so
> 76: # we need to reset the paths if we can't load cstruct
> 77: Gem.clear_paths
> 78: end
> 79:
>
> [2016-05-15T22:14:26+02:00] ERROR: Running exception handlers
> [2016-05-15T22:14:26+02:00] FATAL: Saving node information to
> /var/chef/cache/failed-run-data.json
> [2016-05-15T22:14:26+02:00] ERROR: Exception handlers complete
> [2016-05-15T22:14:26+02:00] FATAL: Stacktrace dumped to
> /var/chef/cache/chef-stacktrace.out
> [2016-05-15T22:14:26+02:00] FATAL: Chef::Exceptions::Package:
> package[ruby2.1-rubygem-cstruct] (ohai::default line 70) had an error:
> Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 9711
> exit 4>!
>
> Any idea?

Can I check that you're deploying SUSE OpenStack Cloud 6 (SOC6) on
SLES12 SP1 and not on another version/release? Also, have you
added SOC6 to an existing setup or are you installing the server
afresh with SLES12 SP1 plus SOC6? If adding SOC6 to an existing
server is that server already patched?

The reference to "zypper" and "ruby2.1-rubygem-cstruct" makes me
think is related to that particular package. Is it already
installed (if so what version?) or available in one of the
configured software repos?

HTH.
--
Simon Flood
SUSE Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

jfonseca
15-May-2016, 22:26
Thanks for the quick reply!

It is a fresh SLES12 SP1 plus SOC6:

# cat /etc/os-release
NAME="SLES"
VERSION="12-SP1"
VERSION_ID="12.1"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP1"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp1"

The installation script goes ahead after manually installing ruby2.1-rubygem-cstruct, but it is failing on the installation of several other packages.

For example, from the /var/log/crowbar/install.log:
[2016-05-15T23:09:25+02:00] ERROR: Running exception handlers
[2016-05-15T23:09:25+02:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2016-05-15T23:09:25+02:00] ERROR: Exception handlers complete
[2016-05-15T23:09:25+02:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-05-15T23:09:25+02:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: package[dnsmasq] (resolver::default line 37) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '8'
---- Begin output of zypper-retry --non-interactive install --auto-agree-with-licenses dnsmasq=2.71-10.1 ----
STDOUT: Refreshing service 'SUSE_Enterprise_Storage_2.1_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP1_x86_64'.
Refreshing service 'SUSE_OpenStack_Cloud_6_x86_64'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
dnsmasq

1 new package to install.
Overall download size: 424.9 KiB. Already cached: 0 B. After the operation, additional 1.1 MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package dnsmasq-2.71-10.1.x86_64 (1/1), 424.9 KiB ( 1.1 MiB unpacked)
Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
Retrying in 30 seconds...
Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
Retrying in 30 seconds...
Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
Retrying in 30 seconds...
Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
Retrying in 30 seconds...
STDERR: Timeout exceeded when accessing 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP1/x86_64/update/x86_64/dnsmasq-2.71-10.1.x86_64.rpm?0sLKBynI9ucR1FRb-Ljj3FyFmaj1Dzi90qeSk5nZCwwXmyh1eiruizwdj9mPCGi8JWg 9cFm2wfKR6QBVtnwc3Dzv_INJ09vCKVpT3Z0aX4FSCgOhMQvev qg-jlFkrcYgoBDunkKbeUGqZmk'.

Manual installation:
# zypper install dnsmasq
Actualizando el servicio SUSE_Enterprise_Storage_2.1_x86_64.
Actualizando el servicio SUSE_Linux_Enterprise_Server_12_SP1_x86_64.
Actualizando el servicio SUSE_OpenStack_Cloud_6_x86_64.
Cargando datos del repositorio...
Leyendo los paquetes instalados...
Resolviendo dependencias de paquete...

The following NEW package is going to be installed:
dnsmasq

1 new package to install.
Tama˝o total de descarga: 424,9 KiB. Ya en cachÚ: 0 B. DespuÚs de la operaciˇn, se utilizarßn 1,1 MiB adicionales.
┐Desea continuar? [s/n/? mostrar todas las opciones] (s): s
Recuperando package dnsmasq-2.71-10.1.x86_64 (1/1), 424,9 KiB ( 1,1 MiB desempaquetado)
Recuperando: dnsmasq-2.71-10.1.x86_64.rpm .................................................. .................................................. .................................................. ...................................[TERMINADO]
Buscando conflictos de archivos: .................................................. .................................................. .................................................. ............................................[TERMINADO]
(1/1) Instalando: dnsmasq-2.71-10.1.x86_64 .................................................. .................................................. .................................................. ..................................[TERMINADO]


Then, after running the installation script again, it fails in a different package (same timeout error).

I am wondering why the installation script cannot install the packages successfully. I am using a proxy, being the Admin server IP in the exclusion list.

Thanks!

smflood
16-May-2016, 10:56
On 15/05/16 22:34, jfonseca wrote:

> Thanks for the quick reply!
>
> It is a fresh SLES12 SP1 plus SOC6:
>
> # cat /etc/os-release
> NAME="SLES"
> VERSION="12-SP1"
> VERSION_ID="12.1"
> PRETTY_NAME="SUSE Linux Enterprise Server 12 SP1"
> ID="sles"
> ANSI_COLOR="0;32"
> CPE_NAME="cpe:/o:suse:sles:12:sp1"
>
> The installation script goes ahead after manually installing
> ruby2.1-rubygem-cstruct, but it is failing on the installation of
> several other packages.
>
> For example, from the /var/log/crowbar/install.log:
> [2016-05-15T23:09:25+02:00] ERROR: Running exception handlers
> [2016-05-15T23:09:25+02:00] FATAL: Saving node information to
> /var/chef/cache/failed-run-data.json
> [2016-05-15T23:09:25+02:00] ERROR: Exception handlers complete
> [2016-05-15T23:09:25+02:00] FATAL: Stacktrace dumped to
> /var/chef/cache/chef-stacktrace.out
> [2016-05-15T23:09:25+02:00] FATAL: Mixlib::ShellOut::ShellCommandFailed:
> package[dnsmasq] (resolver::default line 37) had an error:
> Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0],
> but received '8'
> ---- Begin output of zypper-retry --non-interactive install
> --auto-agree-with-licenses dnsmasq=2.71-10.1 ----
> STDOUT: Refreshing service 'SUSE_Enterprise_Storage_2.1_x86_64'.
> Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP1_x86_64'.
> Refreshing service 'SUSE_OpenStack_Cloud_6_x86_64'.
> Loading repository data...
> Reading installed packages...
> Resolving package dependencies...
>
> The following NEW package is going to be installed:
> dnsmasq
>
> 1 new package to install.
> Overall download size: 424.9 KiB. Already cached: 0 B. After the
> operation, additional 1.1 MiB will be used.
> Continue? [y/n/? shows all options] (y): y
> Retrieving package dnsmasq-2.71-10.1.x86_64 (1/1), 424.9 KiB ( 1.1 MiB
> unpacked)
> Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
> Retrying in 30 seconds...
> Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
> Retrying in 30 seconds...
> Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
> Retrying in 30 seconds...
> Retrieving: dnsmasq-2.71-10.1.x86_64.rpm [error]
> Retrying in 30 seconds...
> STDERR: Timeout exceeded when accessing
> 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP1/x86_64/update/x86_64/dnsmasq-2.71-10.1.x86_64.rpm?0sLKBynI9ucR1FRb-Ljj3FyFmaj1Dzi90qeSk5nZCwwXmyh1eiruizwdj9mPCGi8JWg 9cFm2wfKR6QBVtnwc3Dzv_INJ09vCKVpT3Z0aX4FSCgOhMQvev qg-jlFkrcYgoBDunkKbeUGqZmk'.
>
> Manual installation:
> # zypper install dnsmasq
> Actualizando el servicio SUSE_Enterprise_Storage_2.1_x86_64.
> Actualizando el servicio SUSE_Linux_Enterprise_Server_12_SP1_x86_64.
> Actualizando el servicio SUSE_OpenStack_Cloud_6_x86_64.
> Cargando datos del repositorio...
> Leyendo los paquetes instalados...
> Resolviendo dependencias de paquete...
>
> The following NEW package is going to be installed:
> dnsmasq
>
> 1 new package to install.
> Tama´┐Żo total de descarga: 424,9 KiB. Ya en cach´┐Ż: 0 B. Despu´┐Żs de la
> operaci´┐Żn, se utilizar´┐Żn 1,1 MiB adicionales.
> ´┐ŻDesea continuar? [s/n/? mostrar todas las opciones] (s): s
> Recuperando package dnsmasq-2.71-10.1.x86_64
>
> (1/1), 424,9 KiB ( 1,1
> MiB desempaquetado)
> Recuperando: dnsmasq-2.71-10.1.x86_64.rpm
> .................................................. .................................................. .................................................. ...................................[TERMINADO]
> Buscando conflictos de archivos:
> .................................................. .................................................. .................................................. ............................................[TERMINADO]
> (1/1) Instalando: dnsmasq-2.71-10.1.x86_64
> .................................................. .................................................. .................................................. ..................................[TERMINADO]
>
>
> Then, after running the installation script again, it fails in a
> different package (same timeout error).
>
> I am wondering why the installation script cannot install the packages
> successfully. I am using a proxy, being the Admin server IP in the
> exclusion list.

Since the ruby2.1-rubygem-cstruct package is part of the SOC6 media/pool
I'm wondering whether you've set up the local repo(s) or access to
remote ones as per
https://www.suse.com/documentation/suse-openstack-cloud-6/book_cloud_deploy/data/sec_depl_adm_conf_repos_product.html
although install-suse-cloud should complain if not.

I've certainly had no issues installing a test cloud setup using just
the SLES12 SP1 and SOC6 media (i.e. no updates applied).

Are you using the media to install SOC6 or a network source? It's
possible the SOC6 media is faulty (did you verify the MD5 checksum?) as
I've seen that cause odd things with plain SLES installs.

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

HvdHeuvel
18-May-2016, 10:47
On Sun, 15 May 2016 21:34:01 +0000, jfonseca wrote:

Hi Jfonseca
>
> It is a fresh SLES12 SP1 plus SOC6:
[...]
> The installation script goes ahead after manually installing
> ruby2.1-rubygem-cstruct, but it is failing on the installation of
> several other packages.

[...]

> Then, after running the installation script again, it fails in a
> different package (same timeout error).

yes, after installing this manually, I presume the next one missing was
bridge-utils, than dhcp-server etc ?

> I am wondering why the installation script cannot install the packages
> successfully. I am using a proxy, being the Admin server IP in the
> exclusion list.

I think I have run into this exact same problem earlier this week. In my
case the problem was that during the install, my repositories were no
longer accessible, and these must be available as additional packages are
installed.

It is an educated guess, that earlier in the log file, you will also see
for example the following messages :
--- cut here ---
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '104'
---- Begin output of zypper-retry --non-interactive install --auto-agree-
with-licenses ruby2.1-rubygem-cstruct ----
--- cut here ---

Fortunately, I was running the setup in a VM, and I just added two CDROMS
devices, one for the SLE12 SP1 iso, and one for the ClOUD6 iso.

After this, installation run through just fine.

Thanks
Hans

smflood
18-May-2016, 23:06
On 18/05/2016 10:47, Hans van den Heuvel wrote:

> I think I have run into this exact same problem earlier this week. In my
> case the problem was that during the install, my repositories were no
> longer accessible, and these must be available as additional packages are
> installed.
>
> It is an educated guess, that earlier in the log file, you will also see
> for example the following messages :
> --- cut here ---
> Mixlib::ShellOut::ShellCommandFailed
> ------------------------------------
> Expected process to exit with [0], but received '104'
> ---- Begin output of zypper-retry --non-interactive install --auto-agree-
> with-licenses ruby2.1-rubygem-cstruct ----
> --- cut here ---
>
> Fortunately, I was running the setup in a VM, and I just added two CDROMS
> devices, one for the SLE12 SP1 iso, and one for the ClOUD6 iso.
>
> After this, installation run through just fine.

Do you recall whether you had copied the contents of the attached media
as per section 5.1 of the SUSE OpenStack Cloud 6 Deployment Guide[1]?

I did then pointed YaST/zypper at those directories in preference to the
attached media so that I could then detach them.

HTH.

[1]
https://www.suse.com/documentation/suse-openstack-cloud-6/book_cloud_deploy/data/sec_depl_adm_conf_repos_product.html
--
Simon
SUSE Knowledge Partner

HvdHeuvel
19-May-2016, 07:40
On Wed, 18 May 2016 22:06:12 +0000, Simon Flood wrote:

[...]
>
> Do you recall whether you had copied the contents of the attached media
> as per section 5.1 of the SUSE OpenStack Cloud 6 Deployment Guide[1]?
>
> I did then pointed YaST/zypper at those directories in preference to the
> attached media so that I could then detach them.

Yes, I did most definitely follow the Deployment guide :-)
Just don┬┤t recall any more if I modified the repo preferences.

But I am convinced the problems for jfonseca will be resolved if the
repositories are properly available during ┬┤install-suse-cloud┬┤


[...]

Thanks
Hans

smflood
19-May-2016, 09:03
On 19/05/16 07:40, Hans van den Heuvel wrote:

> Yes, I did most definitely follow the Deployment guide :-)
> Just don┬┤t recall any more if I modified the repo preferences.

I may be able to test that myself.

> But I am convinced the problems for jfonseca will be resolved if the
> repositories are properly available during ┬┤install-suse-cloud┬┤

That was also my thought.

Thanks.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

jfonseca
20-May-2016, 16:18
As per you comments, I have probably missed any steps. I tried to follow the guide and I recall to copy the media. I will repeat the installation to see if there is any difference.

Thanks,

Juanjo.