OpenSuse deployment not working

Hi,

I have posted couple of posts related to OpenSuse provisioning errors. But
after multiple combinations and check looks like the OpenSuse provisioning
has some issues. I could not deploy any version of OpenSuse.

Even, hard coding the repo path to 11.4 or 13.2 mirror location gives
"installation media error"

Did someone deployed opensuse using foreman with latest code 1.8.1 ? Even
with the old code can someone share the template and installation media
setting ?

Thanks in Advance.

Thanks
Gagan

Hi,

··· On Mon, Jun 01, 2015 at 09:19:18PM -0700, Gagan wrote: > Did someone deployed opensuse using foreman with latest code 1.8.1 ? Even

Try the following change to the PXELinux template: http://git.io/vkIJD

Regards

Michael Moll

> Hi,
>
> I have posted couple of posts related to OpenSuse provisioning errors. But
> after multiple combinations and check looks like the OpenSuse provisioning
> has some issues. I could not deploy any version of OpenSuse.
>
> Even, hard coding the repo path to 11.4 or 13.2 mirror location gives
> "installation media error"
>

its hard to debug / troubleshoot this way, do you get more information at
the logs? it looks like a pure opensuse issue ? maybe the mirrors you are
using?

Ohad

··· On Tue, Jun 2, 2015 at 7:19 AM, Gagan wrote:

Did someone deployed opensuse using foreman with latest code 1.8.1 ? Even
with the old code can someone share the template and installation media
setting ?

Thanks in Advance.

Thanks
Gagan


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Thanks Mike, At least this time it did not fail with repo not found. I was
able to proceed.

But at one point the installation fails with "Fail to add add-on product".
I was trying Opensuse 12.3.

I am using AutoYaST SLES default provision template for this. My Foreman
version is 1.8.1 so looks like the template has the changes as suggested in

Even with 11.4 it fails but i am sure this is because i don't have a SDK on
my system. I don't need this so can i comment this out from the template

*<!-- you have to update the next line with the actual URL of your SDK –>*media_url>http://<your_server_here>/iso/suse/SDK/<%=
os_major %>.<%= os_minor %>/<%= @host.architecture %>/</media_url>
<product>SuSE-Linux-SDK</product>

Thanks
Gagan

Hi,

··· On Tue, Jun 02, 2015 at 02:38:16PM -0700, Gagan wrote: > I am using AutoYaST SLES default provision template for this. My Foreman

The SLES template is for SLES only, as some Puppet related things are
different there, OpenSUSE needs the AutoYAST default template.

I’m unsure if OpenSUSE 11.4 still works with the latest template
versions, at least according to my notes in http://git.io/gDlBSg
it was working, but not unattended anymore.

Regards

Michael Moll

Thanks Michael appreciate your help with this issue. I am making progress
with this now

I am interested in OpenSuse 13.2 and that's what i tried this time with
AutoYast default. But this time it fails with
"Package not found in the software repositary Yast2-runlevel"

I have to try older version but not sure if this is something specific to
13.2

Thanks
Gagan

Hi,

··· On Tue, Jun 02, 2015 at 08:20:23PM -0700, Gagan wrote: > I am interested in OpenSuse 13.2 and that's what i tried this time with > AutoYast default. But this time it fails with > "Package not found in the software repositary Yast2-runlevel" > > I have to try older version but not sure if this is something specific to > 13.2

It is. Please try this change to the autoyast template and report back:
http://git.io/vkhcf

As far as I can tell only 13.1 and 13.2 are supported at this time
from the SUSE community anyway and in a quick test I even had
problems with 12.3 here.

Regards

Michael Moll

Awesone !! this worked like a charm.

Another question regarding the packages. We want the GUI and the some
development packages as part of installation. What should i do for that. In
case of kickstart default we have added this at @kde-desktop etc.

Which section should i look for in case of AutoYAST default? I have a
manually installed OpenSuse server with desired packages installed, Is
there a way i can look at the packages list.

Thanks
Gagan Vyas

Hi Michel,

Is there a way to find the package name which i can use with the template
for additional packages while installation. For example I need KDE or Gnome
Installed along with development tools

Zypper command on an existing system (that i installed manually) doesn'r
give the same name as we need to repo packages in template

Thanks
Gagan

Hi,

I was able to install the GUI by changing run level to 5 and adding pattern
"kde" in the template.

Thanks for all you help.

However, after installation i see that the network configuration (IP
details) are lost. It just show lo interface with 127.0.0.1 IP.

Thanks
Gagan

Hi,

··· On Mon, Jun 08, 2015 at 05:32:14PM -0700, Gagan wrote: > However, after installation i see that the network configuration (IP > details) are lost. It just show lo interface with 127.0.0.1 IP.

I saw this on SLES 12 and newer OpenSUSEs with network interfaces that
are not named “eth0”. Pull requests to the community-templates
repository are very welcome! As SUSE is not very common amongst Foreman
devs, this is something that really has to come from a broader community,
maybe the solution for this is already in recent autoyast docs.

Regards

Michael Moll

Thanks Michael, I will let you know if i can make it work.

BTW, is foreman capable of deploying ESXi server. We work on a lot of VM's
but we have to deal with ESX installation as well

Thanks
Gagan