SUSE Openstack Cloud

Archive SUSE OpenStack Cloud
1

Hello,

I am installing SUSE Openstack Cloud 7 in LAB environment. I followed all the steps while installing crowbar and but getting error while executing command " install-suse-cloud" and getting ruby related errors. I am new to SUSE Openstack installation hence request help for how to resolve issues

While checking logs in install.log file …received following error… Kindly help

/usr/lib64/ruby/site_ruby/2.1.0/rubygems/dependency.rb:308:in to_specs': Could not find 'nokogiri' (>= 1.5.9) among 141 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/var/lib/crowbar/.gem/ruby/2.1.0:/usr/lib64/ruby/gems/2.1.0', execute gem envfor more information from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1439:inblock in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in each' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1410:in activate' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1442:in block in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in each' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1410:in activate' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1442:in block in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in each' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1410:in activate' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1442:in block in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in each' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1428:in activate_dependencies’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/specification.rb:1410:in activate' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:68:in block in gem’
from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:67:in synchronize' from /usr/lib64/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:67:in gem’
from /opt/dell/crowbar_framework/config/boot.rb:30:in <top (required)>' from bin/rake:3:in require_relative’
from bin/rake:3:in `’

2

Hi,

do you have the product media (DVD) mounted and defined as repositories? These two are the minimum to set up a lab environment, see this.

3

[QUOTE=eblock;38584]Hi,

do you have the product media (DVD) mounted and defined as repositories? These two are the minimum to set up a lab environment, see this.[/QUOTE]

Hello,

I have copied SLES12 and SUSE Openstack Cloud 7 iso files to /ISO directory and mounted these files to required folder. Below is the output of the command

SUSE-Admin-Node:/ISO # mount -o loop /ISO/SLES12.iso /srv/tftpboot/suse-12.2/x86_64/install/
mount: /dev/loop0 is write-protected, mounting read-only
SUSE-Admin-Node:/ISO # mount -o loop /ISO/SOC7.iso /srv/tftpboot/suse-12.2/x86_64/repos/Cloud/
mount: /dev/loop1 is write-protected, mounting read-only

Still I am facing the issue…Kindly help. Thanks

4

I think, the problem is rather that the ruby2.1-rubygem-nokogiri-1.6.1-3.29.x86_64.rpm package that is available on the cloud7 iso is not installed.
Did you use

zypper in -t pattern cloud_admin

to pull in all required packages?

5

[QUOTE=bmwiedemann;38586]I think, the problem is rather that the ruby2.1-rubygem-nokogiri-1.6.1-3.29.x86_64.rpm package that is available on the cloud7 iso is not installed.
Did you use

zypper in -t pattern cloud_admin

to pull in all required packages?[/QUOTE]

Hi

please find output of zypper in -t pattern cloud_admin

SUSE-Admin-Node:~ # zypper in -t pattern cloud_admin
Refreshing service ‘SUSE_Linux_Enterprise_Server_12_SP2_x86_64’.
Refreshing service ‘SUSE_OpenStack_Cloud_7_x86_64’.
Loading repository data…
Reading installed packages…
‘pattern:cloud_admin’ is already installed.
No update candidate for ‘pattern:cloud_admin-20170124-2.1.x86_64’. The highest available version is already installed.
Resolving package dependencies…

6

And what happens if you run zypper in ruby2.1-rubygem-nokogiri?

7

Hello,

here please find the output of above command

SUSE-Admin-Node:~ # zypper in ruby2.1-rubygem-nokogiri
Refreshing service ‘SUSE_Linux_Enterprise_Server_12_SP2_x86_64’.
Refreshing service ‘SUSE_OpenStack_Cloud_7_x86_64’.
Loading repository data…
Reading installed packages…
‘ruby2.1-rubygem-nokogiri’ is already installed.
No update candidate for ‘ruby2.1-rubygem-nokogiri-1.6.1-3.29.x86_64’. The highest available version is already installed.
Resolving package dependencies…

Nothing to do.

Please help.

Thanks.

8

Have you tried to re-run the install script? Is the same error occuring? Did you compare the checksums of the product media? Is the admin server up to date?

9

[QUOTE=Raviraj38;38598]
SUSE-Admin-Node:~ # zypper in ruby2.1-rubygem-nokogiri
Refreshing service ‘SUSE_Linux_Enterprise_Server_12_SP2_x86_64’.
Refreshing service ‘SUSE_OpenStack_Cloud_7_x86_64’.[/QUOTE]

Could it be, that you are running without update repos?
Sometimes bugs get into the Gold Master version and the only way to fix those is via maintenance updates.
That is why our products are only supported when you have the latest updates installed.

10

[QUOTE=Raviraj38;38598]
SUSE-Admin-Node:~ # zypper in ruby2.1-rubygem-nokogiri
Refreshing service ‘SUSE_Linux_Enterprise_Server_12_SP2_x86_64’.
Refreshing service ‘SUSE_OpenStack_Cloud_7_x86_64’.[/QUOTE]

Could it be that you are running without update repos?
There might have been bugs in the Gold Master (GM) versions which we can only fix via maintenance updates.
That is why usually SUSE products are only supported when you have the latest updates installed.

11

[QUOTE=bmwiedemann;38613]Could it be that you are running without update repos?
There might have been bugs in the Gold Master (GM) versions which we can only fix via maintenance updates.
That is why usually SUSE products are only supported when you have the latest updates installed.[/QUOTE]

Hi Thanks for the response. However I have built new VM with same configuration and tried to run command " install-suse-cloud" after all configurations and updates. I have received following error

Fri Jul 7 01:41:51 IST 2017 /usr/sbin/install-suse-cloud started with args:
WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.4
rake aborted!
could not connect to server: Connection refused
Is the server running on host “localhost” (127.0.0.1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Cannot assign requested address
Is the server running on host “localhost” (::1) and accepting
TCP/IP connections on port 5432?
/opt/dell/crowbar_framework/lib/tasks/database.rake:25:in block (3 levels) in <top (required)>' /opt/dell/crowbar_framework/lib/tasks/database.rake:22:in tap’
/opt/dell/crowbar_framework/lib/tasks/database.rake:22:in `block (2 levels) in <top (required)>’
Tasks: TOP => db:cleanup
(See full trace by running task with --trace)

Kindly suggest the further steps for troubleshooting. Thanks

12

[QUOTE=bmwiedemann;38613]Could it be that you are running without update repos?
There might have been bugs in the Gold Master (GM) versions which we can only fix via maintenance updates.
That is why usually SUSE products are only supported when you have the latest updates installed.[/QUOTE]

Hello,

I have tried to launch new VM with similar configuration and tried to run “install-suse-cloud” command and received error messages which I posted in my earlier post. I doubt is there any bug either in base OS or cloud packages. Request you to kindly help how to troubleshoot or are there any bug fix patches available for SUSE Enterprise Linux or SUSE Openstack Cloud package. Kindly help ASAP. Thanks.

13

Before you run the install-suse-cloud command you have to do these steps:

zypper in postgresql94-server systemctl enable postgresql.service && systemctl start postgresql.service systemctl start crowbar-init.service
Also your network setup should be correct, the admin server has to resolve his fqdn. Check hostname -f before starting the script.

14

Hello,

Thanks for the response. I have done the steps mentioned but still received the following error. I have also checked hostname -f and it gives FQDN name. Kindly suggest

Fri Jul 7 19:40:31 IST 2017 /usr/sbin/install-suse-cloud started with args:
WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.4
rake aborted!
FATAL: Ident authentication failed for user “crowbar”
/opt/dell/crowbar_framework/lib/tasks/database.rake:25:in block (3 levels) in <top (required)>' /opt/dell/crowbar_framework/lib/tasks/database.rake:22:in tap’
/opt/dell/crowbar_framework/lib/tasks/database.rake:22:in `block (2 levels) in <top (required)>’
Tasks: TOP => db:cleanup
(See full trace by running task with --trace)

15

On 07/07/17 08:14, Raviraj38 wrote:
[color=blue]

I have tried to launch new VM with similar configuration and tried to
run “install-suse-cloud” command and received error messages which I
posted in my earlier post. I doubt is there any bug either in base OS or
cloud packages. Request you to kindly help how to troubleshoot or are
there any bug fix patches available for SUSE Enterprise Linux or SUSE
Openstack Cloud package. Kindly help ASAP. Thanks.[/color]

Please can you let us know exactly which steps you have followed to
try and install SUSE OpenStack Cloud 7? Since you’re having issues after
redoing your install with the same configuration it’s likely you’ve
missed a step which we can only point out when we know which steps you
have done.

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.

16

Hello Simon,

Thanks for the reply. I have followed document SUSE Openstack Cloud 7 Deployment Guide for doing the installation. Following are the steps I followed

  1. Installed SUSE Enterprise Linux 12 SP2 as a base OS with disk partitions as SWAP - 2 GB, / - 30 GB , /srv – 30 GB , /home - 8 GB.
  2. After installation of base OS I have registered the system to get latest updates & patches with "SUSEConnect -r " command
  3. Then run the following commands Zypper lr and Zypper patch
  4. I have installed SUSE Openstack Cloud extension via YAST tool YaST > Software > Add-On Products & selected SUSE Openstack Cloud 7
  5. After installation of SUSE Cloud extension, installed cloud_admin metapackage through YaST. Yast → Software → Software Management → Filter “Patterns” and add the “cloud_admin” pattern, click on accept
  6. I have installed SMT server on Administration server with this command “sudo zypper in -t pattern smt”
  7. Done configuration of SMT Server through YaST Start such as YaST > Network Services > SMT Configuration Wizard. I have entered the mirror credential ( which I obtained from scc.suse.com with my account) , performed the test , entered my e-mail address and proceed to Step-II where I have entered database password & e-mail address, entered new MariaDB root password and generated new certificate by clicking on " Run CA management " and by entering new password
  8. Added mandatory repositories in SMT server with following command
    " for REPO in SLES12-SP2-{Pool,Updates} SUSE-Openstack-Cloud-7-{Pool,Updates} do; smt-repos $REPO sle-12-x86_64 -e done
  9. Done mirroring of repositories with command “smt-sync” and " smt-mirror -L /var/log/smt/smt-mirror.log
  10. Done software repository setup by copying ISO images on local folder , created two folders with commands
    “mkdir -p /srv/tftpboot/suse-12.2/x86_64/install” for SLES-12.iso and “mkdir -p /srv/tftpboot/suse-12.2/x86_64/repos/Cloud” and mounted iso images in local repository with commands " mount -o loop /ISO/SLES12.iso /srv/tftpboot/suse-12.2/x86_64/install " and “mount -o loop /ISO/SOC7.iso /srv/tftpboot/suse-12.2/x86_64/repos/Cloud”
  11. Also made entries in /etc/fstab files
  12. Configured network interfaces on Administration server " Start YaST > System > Network Settings " . Done configuration for eth0 as Admin network and eth1 as bastation network
  13. Done network configuration in crowbar by following path " YaST > Miscellaneous > Crowbar" and done configuration of admin, bmc, bmc-vlan, nova-fixed, storage networks
  14. Ensured repository selected under crowbar is " Local SMT Server" and ensured that hostname -f gives FQDN name
  15. Ensured that all SUSE Linux Enterprise & SUSE Openstack Cloud updates & patches are up-to date by running command " zypper patch"
  16. Executed following commands " zypper in postgresql94-server" , " systemctl enable postgresql.service && systemctl start postgresql.service" and " systemctl start crowbar-init.service "
    17 Finally run command " install-suse-cloud" but still getting this error " FATAL: Ident authentication failed for user “crowbar” and because of that I am not able to install further. Kindly help ASAP. Thanks
17

I forgot to mention one command. If crowbar-int service is up and running, you have to run crowbarctl database create before running the install-suse-cloud script.

18

Hello,

Thanks for the reply. I executed the command “crowbarctl database create” and then executed command " install-suse-cloud" then I got error saying that run with screen install . After that I run following command “screen /usr/sbin/install-suse-cloud” and then I got following error " failed to validate network.json configuration Please check and fix with yast2 crowbar. Aborting " …Kindly Help.
Attached herewith log file - install.log from /var/log/ folder

=== 2017-07-08 15:44:46 +0530: Error: Not running in screen. Please use “screen /usr/sbin/install-suse-cloud” to avoid problems during network re-configuration. Aborting.
Sat Jul 8 15:45:28 IST 2017 /usr/sbin/install-suse-cloud started with args:
WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.4
== 20161019155242 CreateDelayedJobs: reverting ================================
– drop_table(:delayed_jobs)
0.0015s
== 20161019155242 CreateDelayedJobs: reverted (0.0015s) =======================

== 20160819142156 CreateApiErrors: reverting ==================================
– drop_table(:errors)
0.0012s
== 20160819142156 CreateApiErrors: reverted (0.0036s) =========================

== 20160223200120 ChangeBackupVersionType: reverting ==========================
– change_column(:backups, :version, “float USING version::double precision”)
0.1608s
== 20160223200120 ChangeBackupVersionType: reverted (0.1617s) =================

== 20160215120522 AddMigrationLevelToBackups: reverting =======================
– remove_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
0.0009s
== 20160215120522 AddMigrationLevelToBackups: reverted (0.0011s) ==============

== 20151222144602 CreateBackups: reverting ====================================
– drop_table(:backups)
0.0016s
== 20151222144602 CreateBackups: reverted (0.0017s) ===========================

== 20150806114015 CreateProposalQueues: reverting =============================
– drop_table(:proposal_queues)
→ 0.0010s
== 20150806114015 CreateProposalQueues: reverted (0.0011s) ====================

== 20150312081459 CreateProposals: reverting ==================================
– remove_index(:proposals, {:column=>[:barclamp, :name]})
0.0021s
– drop_table(:proposals)
0.0009s
== 20150312081459 CreateProposals: reverted (0.0033s) =========================

== 20150312081459 CreateProposals: migrating ==================================
– create_table(:proposals)
0.1248s
– add_index(:proposals, [:barclamp, :name], {:unique=>true})
0.0495s
== 20150312081459 CreateProposals: migrated (0.1744s) =========================

== 20150806114015 CreateProposalQueues: migrating =============================
– create_table(:proposal_queues)
→ 0.0450s
== 20150806114015 CreateProposalQueues: migrated (0.0451s) ====================

== 20151222144602 CreateBackups: migrating ====================================
– create_table(:backups)
→ 0.0706s
== 20151222144602 CreateBackups: migrated (0.0707s) ===========================

== 20160215120522 AddMigrationLevelToBackups: migrating =======================
– add_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
→ 0.0372s
== 20160215120522 AddMigrationLevelToBackups: migrated (0.0373s) ==============

== 20160223200120 ChangeBackupVersionType: migrating ==========================
– change_column(:backups, :version, :string)
→ 0.1443s
== 20160223200120 ChangeBackupVersionType: migrated (0.1444s) =================

== 20160819142156 CreateApiErrors: migrating ==================================
– create_table(:errors)
→ 0.0611s
== 20160819142156 CreateApiErrors: migrated (0.0611s) =========================

== 20161019155242 CreateDelayedJobs: migrating ================================
– create_table(:delayed_jobs, {:force=>true})
→ 0.3441s
– add_index(:delayed_jobs, [:priority, :run_at], {:name=>“delayed_jobs_priority”})
→ 0.0247s
== 20161019155242 CreateDelayedJobs: migrated (0.3689s) =======================

=== 2017-07-08 15:45:33 +0530: Performing sanity checks
Cannot validate definition for conduit list 2 with pattern ‘dual/./.’: conduit ‘bastion’ has no list of interfaces

=== 2017-07-08 15:45:34 +0530: Error: Failed to validate network.json configuration. Please check and fix with yast2 crowbar. Aborting.
Sat Jul 8 15:45:49 IST 2017 /usr/sbin/install-suse-cloud started with args:
WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.4
== 20161019155242 CreateDelayedJobs: reverting ================================
– drop_table(:delayed_jobs)
→ 0.0014s
== 20161019155242 CreateDelayedJobs: reverted (0.0015s) =======================

== 20160819142156 CreateApiErrors: reverting ==================================
– drop_table(:errors)
→ 0.0011s
== 20160819142156 CreateApiErrors: reverted (0.0037s) =========================

== 20160223200120 ChangeBackupVersionType: reverting ==========================
– change_column(:backups, :version, “float USING version::double precision”)
→ 0.1103s
== 20160223200120 ChangeBackupVersionType: reverted (0.1109s) =================

== 20160215120522 AddMigrationLevelToBackups: reverting =======================
– remove_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
→ 0.0006s
== 20160215120522 AddMigrationLevelToBackups: reverted (0.0008s) ==============

== 20151222144602 CreateBackups: reverting ====================================
– drop_table(:backups)
→ 0.0010s
== 20151222144602 CreateBackups: reverted (0.0010s) ===========================

== 20150806114015 CreateProposalQueues: reverting =============================
– drop_table(:proposal_queues)
→ 0.0009s
== 20150806114015 CreateProposalQueues: reverted (0.0010s) ====================

== 20150312081459 CreateProposals: reverting ==================================
– remove_index(:proposals, {:column=>[:barclamp, :name]})
→ 0.0023s
– drop_table(:proposals)
→ 0.0012s
== 20150312081459 CreateProposals: reverted (0.0037s) =========================

== 20150312081459 CreateProposals: migrating ==================================
– create_table(:proposals)
→ 0.1585s
– add_index(:proposals, [:barclamp, :name], {:unique=>true})
→ 0.0831s
== 20150312081459 CreateProposals: migrated (0.2418s) =========================

== 20150806114015 CreateProposalQueues: migrating =============================
– create_table(:proposal_queues)
→ 0.1527s
== 20150806114015 CreateProposalQueues: migrated (0.1528s) ====================

== 20151222144602 CreateBackups: migrating ====================================
– create_table(:backups)
→ 0.0739s
== 20151222144602 CreateBackups: migrated (0.0740s) ===========================

== 20160215120522 AddMigrationLevelToBackups: migrating =======================
– add_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
→ 0.2347s
== 20160215120522 AddMigrationLevelToBackups: migrated (0.2348s) ==============

== 20160223200120 ChangeBackupVersionType: migrating ==========================
– change_column(:backups, :version, :string)
→ 0.0339s
== 20160223200120 ChangeBackupVersionType: migrated (0.0339s) =================

== 20160819142156 CreateApiErrors: migrating ==================================
– create_table(:errors)
→ 0.0348s
== 20160819142156 CreateApiErrors: migrated (0.0349s) =========================

== 20161019155242 CreateDelayedJobs: migrating ================================
– create_table(:delayed_jobs, {:force=>true})
→ 0.0354s
– add_index(:delayed_jobs, [:priority, :run_at], {:name=>“delayed_jobs_priority”})
→ 0.0333s
== 20161019155242 CreateDelayedJobs: migrated (0.0689s) =======================

=== 2017-07-08 15:45:53 +0530: Performing sanity checks

=== 2017-07-08 15:45:53 +0530: Error: Not running in screen. Please use “screen /usr/sbin/install-suse-cloud” to avoid problems during network re-configuration. Aborting.
Sat Jul 8 15:46:10 IST 2017 /usr/sbin/install-suse-cloud started with args:
WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.4
== 20161019155242 CreateDelayedJobs: reverting ================================
– drop_table(:delayed_jobs)
→ 0.0015s
== 20161019155242 CreateDelayedJobs: reverted (0.0015s) =======================

== 20160819142156 CreateApiErrors: reverting ==================================
– drop_table(:errors)
→ 0.0010s
== 20160819142156 CreateApiErrors: reverted (0.0029s) =========================

== 20160223200120 ChangeBackupVersionType: reverting ==========================
– change_column(:backups, :version, “float USING version::double precision”)
→ 0.1601s
== 20160223200120 ChangeBackupVersionType: reverted (0.1608s) =================

== 20160215120522 AddMigrationLevelToBackups: reverting =======================
– remove_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
0.0007s
== 20160215120522 AddMigrationLevelToBackups: reverted (0.0009s) ==============

== 20151222144602 CreateBackups: reverting ====================================
– drop_table(:backups)
0.0018s
== 20151222144602 CreateBackups: reverted (0.0019s) ===========================

== 20150806114015 CreateProposalQueues: reverting =============================
– drop_table(:proposal_queues)
0.0015s
== 20150806114015 CreateProposalQueues: reverted (0.0016s) ====================

== 20150312081459 CreateProposals: reverting ==================================
– remove_index(:proposals, {:column=>[:barclamp, :name]})
→ 0.0018s
– drop_table(:proposals)
0.0008s
== 20150312081459 CreateProposals: reverted (0.0028s) =========================

== 20150312081459 CreateProposals: migrating ==================================
– create_table(:proposals)
0.0669s
– add_index(:proposals, [:barclamp, :name], {:unique=>true})
0.0420s
== 20150312081459 CreateProposals: migrated (0.1090s) =========================

== 20150806114015 CreateProposalQueues: migrating =============================
– create_table(:proposal_queues)
0.0777s
== 20150806114015 CreateProposalQueues: migrated (0.0778s) ====================

== 20151222144602 CreateBackups: migrating ====================================
– create_table(:backups)
→ 0.0603s
== 20151222144602 CreateBackups: migrated (0.0604s) ===========================

== 20160215120522 AddMigrationLevelToBackups: migrating =======================
– add_column(:backups, :migration_level, :integer, {:limit=>8, :default=>20151222144602})
0.0779s
== 20160215120522 AddMigrationLevelToBackups: migrated (0.0780s) ==============

== 20160223200120 ChangeBackupVersionType: migrating ==========================
– change_column(:backups, :version, :string)
0.0521s
== 20160223200120 ChangeBackupVersionType: migrated (0.0522s) =================

== 20160819142156 CreateApiErrors: migrating ==================================
– create_table(:errors)
0.0519s
== 20160819142156 CreateApiErrors: migrated (0.0520s) =========================

== 20161019155242 CreateDelayedJobs: migrating ================================
– create_table(:delayed_jobs, {:force=>true})
0.0516s
– add_index(:delayed_jobs, [:priority, :run_at], {:name=>“delayed_jobs_priority”})
0.0247s
== 20161019155242 CreateDelayedJobs: migrated (0.0765s) =======================

=== 2017-07-08 15:46:14 +0530: Performing sanity checks
Cannot validate definition for conduit list 2 with pattern ‘dual/./.’: conduit ‘bastion’ has no list of interfaces

=== 2017-07-08 15:46:14 +0530: Error: Failed to validate network.json configuration. Please check and fix with yast2 crowbar. Aborting.

19

Hello
I fixed the above error - Failed to validate network.json configuration with proper crowbar configuration and executed the same screen install-suse-cloud command. Now I received following error

Job for chef-server.service failed because the control process exited with error code. See “systemctl status chef-server.service” and “journalctl -xe” for details.

Here is the output of systemctl status chef-server.service

chef-server.service - Server component of the Chef systems integration framework
Loaded: loaded (/usr/lib/systemd/system/chef-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-07-09 03:59:52 IST; 24min ago
Process: 1016 ExecStart=/usr/bin/chef-server -u chef -G chef -e production -a thin -p ${PORT} -C ${CONFIG} -L ${LOGFILE} ${OPTIONS} (code=exited, status=1/FAILURE)
Process: 1010 ExecStartPre=/usr/sbin/chef-create-amqp-passwd (code=exited, status=0/SUCCESS)
Main PID: 1016 (code=exited, status=1/FAILURE)

Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/lib64/ruby/gems/2.1.0/gems/merb-core…up’
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/lib64/ruby/gems/2.1.0/gems/merb-core…rt’
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/lib64/ruby/gems/2.1.0/gems/merb-core…rt’
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/lib64/ruby/gems/2.1.0/gems/chef-serv…)>’
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/bin/chef-server:23:in load' Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com chef-server[1016]: from /usr/bin/chef-server:23:in ’
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com systemd[1]: chef-server.service: Main process exited, code=exited, statu…LURE
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com systemd[1]: Failed to start Server component of the Chef systems integra…ork.
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com systemd[1]: chef-server.service: Unit entered failed state.
Jul 09 03:59:52 SUSE-Admin-Node.tbusso.com systemd[1]: chef-server.service: Failed with result ‘exit-code’.
Hint: Some lines were ellipsized, use -l to show in full

20

So at least you see progress :wink:

Chef needs these services to be started prior to chef-server:

=== 2017-05-09 08:43:08 +0200: Starting required services Created symlink from /etc/systemd/system/multi-user.target.wants/rabbitmq-server.service to /usr/lib/systemd/system/rabbitmq-server.service. Created symlink from /etc/systemd/system/multi-user.target.wants/chef-solr.service to /usr/lib/systemd/system/chef-solr.service. Created symlink from /etc/systemd/system/multi-user.target.wants/chef-expander.service to /usr/lib/systemd/system/chef-expander.service. Created symlink from /etc/systemd/system/multi-user.target.wants/chef-server.service to /usr/lib/systemd/system/chef-server.service.
Can you paste the log output of install.log before crowbar tries to start chef-server? Are the other three services started successfully?