Feature #3733: deploy SLES with Foreman - Foreman

Actions

Copy link

Feature #3733

closed

deploy SLES with Foreman

Added by Anonymous about 11 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Unattended installations

Target version:

1.4.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

I want Foreman also to be able to provision SLES 11.3, however after trying alot of combination/associations I'm still always having the problem that in the "Operating System" tab on the "New Host" page the Media dropdown is greyed out. The Parameters in production.log:

Started POST "/hosts/current_parameters" for 62.128.1.22 at 2013-11-22 17:21:26 +0100
Processing by HostsController#current_parameters as */*
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"aDSBsfeHRimg4UGPohWTTferabkHOQDElqzRkyjkY9Y=", "host"=>{"name"=>"tmptst", "organization_id"=>"9", "location_id"=>"1", "hostgroup_id"=>"", "compute_resource_id"=>"", "environment_id"=>"3", "puppet_ca_proxy_id"=>"1", "puppet_proxy_id"=>"1", "puppetclass_ids"=>[""], "managed"=>"true", "progress_report_id"=>"[FILTERED]", "type"=>"Host::Managed", "mac"=>"01:23:45:67:89:0a", "domain_id"=>"3", "subnet_id"=>"1", "ip"=>"10.4.8.48", "interfaces_attributes"=>{"new_interfaces"=>{"_destroy"=>"false", "type"=>"Nic::Managed", "mac"=>"", "name"=>"", "domain_id"=>"", "ip"=>"", "provider"=>"IPMI"}}, "architecture_id"=>"1", "operatingsystem_id"=>"14", "provision_method"=>"build", "build"=>"1", "ptable_id"=>"7", "disk"=>"", "root_pass"=>"[FILTERED]", "is_owned_by"=>"", "enabled"=>"1", "model_id"=>"", "comment"=>"", "overwrite"=>"false"}, "host_id"=>"null"}

I'm having the impression that SuSE support has bitrotted away in the last two years, because nobody is using it. As I'm forced now to also support SuSE with my Foreman/Puppet installation, I'd really like to see this getting into shape for 1.4 and can contribute OS templates but still need developer's help with Foreman's inner workings.

Actions

Copy link

Updated by Lukas Zapletal about 11 years ago

Michael,

can you describe how exactly have you associated all the required objects?

Suse should be working fine, although I was not testing that recently. Patches are welcomed, but I guess this must be some mis-configuration there. Is this Foreman 1.3.1?

Actions

Copy link

Updated by Anonymous about 11 years ago

Yes, Foreman 1.3.1, I think all associations are there:

$ hammer medium info --id 4
Id:          4
Name:        OpenSuSE mirror
Path:        http://mirror.isoc.org.il/pub/opensuse/distribution/$major.$minor/repo/oss
OS Family:   Suse
OS IDs:      14
Created at:  2013/10/21 16:28:38
Updated at:  2013/11/21 23:35:50

$ hammer medium info --id 7
Id:          7
Name:        SuSE Mirror
Path:        http://xxx.xxx.net/iso/suse/$major.$minor/$arch
OS Family:   Suse
OS IDs:      14
Created at:  2013/11/21 17:54:46
Updated at:  2013/11/21 23:10:57

$ hammer os info --id 14
Id:                  14
Name:                SLES 11.3
Release name:        
Family:              Suse
Installation media:  OpenSuSE mirror, SuSE Mirror
Architectures:       x86_64
Partition tables:    SuSE Entire SCSI Disk
Config templates:    YaST2 Default, YaST2 default PXELinux
Parameters:

Actions

Copy link

Updated by Anonymous about 11 years ago

OK, media is selectable now. Was a thinko with Locations (thanks to lzap getting me on the right track via IRC).
Taking this ticket for now while trying to get SLES 11.3 support into Foreman.

Actions

Copy link

Updated by Anonymous about 11 years ago

Tracker changed from Bug to Feature
Subject changed from Media not selectable for SLES to deploy SLES with Foreman
Assignee set to Anonymous