from:"William Muriithi"

[cobbler] Re: Error associating a system to a profile

2017-09-15 Thread William Muriithi

Hello,

Just realised I had forgotten the version details when I sent the mail earlier


[root@cobbler ~]# rpm -qa | grep cobbler
cobbler-2.8.0-4.el7.x86_64
cobbler-web-2.8.0-4.el7.noarch

CentOS Linux release 7.3.1611 (Core)
[root@cobbler ~]#

>
> I just imported a new distro/profile but when I attempt to associate
> to a system, I am noticing this error below.  I have also noticed
> that, when I delete the system and associate it with a profile that
> existed before, I don't get any error.
>
> What could be a good cause of investigating what could have caused it?
>
> [root@cobbler ~]# cobbler system add --name=iron
> --hostname=iron.eng.example.com --gateway=192.168.20.168
> --profile=rhel-workstation-7.4-x86_64 --dns-name=iron.eng.example.com
> --mac=0c:c4:7a:43:39:d8 --ip-address=192.168.20.26
> --subnet=255.255.255.0 --status=production --interface=eth0 --static=1
> exception on server: unhashable type: 'list'
> [root@cobbler ~]#
>
Regards,
William
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Error associating a system to a profile

2017-09-15 Thread William Muriithi

Hello.

I just imported a new distro/profile but when I attempt to associate
to a system, I am noticing this error below.  I have also noticed
that, when I delete the system and associate it with a profile that
existed before, I don't get any error.

What could be a good cause of investigating what could have caused it?

[root@cobbler ~]# cobbler system add --name=iron
--hostname=iron.eng.example.com --gateway=192.168.20.168
--profile=rhel-workstation-7.4-x86_64 --dns-name=iron.eng.example.com
--mac=0c:c4:7a:43:39:d8 --ip-address=192.168.20.26
--subnet=255.255.255.0 --status=production --interface=eth0 --static=1
exception on server: unhashable type: 'list'
[root@cobbler ~]#


[root@cobbler ~]# tail -n -50 /var/log/cobbler/cobbler.log
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(profile)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(name)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(hostname)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(interface)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(in_place)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(gateway)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | REMOTE modify_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==);
attribute(modify_interface)
Fri Sep 15 13:35:58 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:58 2017 - INFO | find_items; ['system']
Fri Sep 15 13:35:59 2017 - INFO | find_items; ['system']
Fri Sep 15 13:35:59 2017 - INFO | find_items; ['system']
Fri Sep 15 13:35:59 2017 - INFO | REMOTE save_item(system);
user();
object_id(___NEW___system::WEJnr50ajDQAAcjDvCfKF5iN3XGL07Pfjw==)
Fri Sep 15 13:35:59 2017 - DEBUG | REMOTE CLI Authorized; user(?)
Fri Sep 15 13:35:59 2017 - INFO | add_item(system); ['iron']
Fri Sep 15 13:35:59 2017 - DEBUG | get_items; ['system']
Fri Sep 15 13:35:59 2017 - DEBUG | done with get_items; ['system']
Fri Sep 15 13:35:59 2017 - INFO | Exception occured: 
Fri Sep 15 13:35:59 2017 - INFO | Exception value: unhashable type: 'list'
Fri Sep 15 13:35:59 2017 - INFO | Exception Info:
  File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line
2074, in _dispatch
return method_handle(*params)
   File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line
974, in xapi_object_edit
return self.save_item(object_type, handle, token)
   File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line
988, in save_item
rc = self.api.add_item(what,obj)
   File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 462, in add_item
return 
self.get_items(what).add(ref,check_for_duplicate_names=check_for_duplicate_names,save=save,logger=logger)
   File "/usr/lib/python2.7/site-packages/cobbler/collection.py", line
345, in add
self.lite_sync.add_single_system(ref.name)
   File "/usr/lib/python2.7/site-packages/cobbler/action_litesync.py",
line 157, in add_single_system
self.tftpd.add_single_system(system)
   File "/usr/lib/python2.7/site-packages/cobbler/modules/manage_in_tftpd.py",
line 155, in add_single_system
self.pxegen.write_all_system_files(system, menu_items)
   File "/usr/lib/python2.7/site-packages/cobbler/pxegen.py", line
303, in write_all_system_files
self.write_pxe_file(f2, system, profile, distro, working_arch,
metadata=pxe_metadata)
   File "/usr/lib/python2.7/site-packages/cobbler/pxegen.py", line
582, in write_pxe_file
blended = utils.blender(self.api, True, system)
   File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 607,
in blender
__consolidate(node,results)
   File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 797,
in __consolidate
results[field] = uniquify(results[field])
   File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 753,
in uniquify
if marker in seen:

[root@cobbler ~]#



Regards,
William
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: koan EXSi support

2017-04-04 Thread William Muriithi

Hi Scott,


> I haven’t used cobbler with ESXI in a while, so I don’t exactly remember
> what the parameters were... but I know that you need to have a couple of
> kernel options set in your profile.  I had my setup completely automated,
> but it got erased when my section got reorganized.  Ideally you should be
> able to press the power-button and have your OS installed, updated, and
> setup for you.  Admittedly, what I mostly worked with was kvm or bare-metal,
> but I had some ESXI servers in the loop as well.

Thanks for that info.  It mean its well supported on ESXI, I just have
to figure out how to do it

>
> Let me see if I have any notes from left over from that project.  In the
> meantime if anyone else knows the answer off the top of their head please
> let us know.
> I am at work right now, so it might be ~7 hours or so before I can get back
> to you, but since we are likely in different time-zones, I'm sure that isn't
> a problem.
>
No problem Scott, take your time.  I really appreciate your effort and
look forward to your notes.

I am curious, where one should run the command below, it looks like on
the ESXI, reading between lines, but none of the articles online
highlight that explicitly.

koan --virt --server=cobbler.eng.example.com --profile=rhel7.3-x86_64
--virt-type=vmware   --virt-name=lithium.eng.example.com

If its on ESXi, how do you install koan to virtual machine thats don't
have a operating system yet? I have a system with the virtual machine
already setup on cobbler side as follows:

cobbler system add --name=lithium --hostname=lithium.eng.example.com
--gateway=192.168.20.168 --profile=rhel7.3-x86_64
--dns-name=lithium.eng.example.com --mac=00:50:56:9e:fe:1a
--ip-address=192.168.20.3 --subnet=255.255.255.0 --status=production
--interface=em1 --static=1

Regards,
William
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] koan EXSi support

2017-04-03 Thread William Muriithi

Hello,

I have a hyper-visor EXSi version 6 and I am looking at using cobbler
for virtual machine provisioning.  I had initially scanned the docs
and somehow got a feeling EXSi is supported.

However, after spending the last 4 hours attempting it, and after
researching and reading all I could find, it seem like EXSi isn't
supported.

Have anyone managed provisioning vmware based virtual machine using
koan?  Would be grateful if you can share a link to your notes or any
data that can lead me toward a successful goal

Regards,
William
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Time for a 2.8.1 release?

2017-03-22 Thread William Muriithi

r in.tftpd[8316]: Client 192.168.20.26 finished 
grub//01-0C-C4-7A-43-39-D8
Mar 22 12:39:26 cobbler in.tftpd[8317]: RRQ from 192.168.20.26 filename 
grub//01-0C-C4-7A-43-39-D8
Mar 22 12:39:26 cobbler in.tftpd[8317]: Client 192.168.20.26 finished 
grub//01-0C-C4-7A-43-39-D8
Mar 22 12:39:35 cobbler in.tftpd[8318]: RRQ from 192.168.20.26 filename 
grub//images/RHEL6-x86_64/vmlinuz
Mar 22 12:39:35 cobbler in.tftpd[8318]: tftp: client does not accept options
Mar 22 12:39:35 cobbler in.tftpd[8319]: RRQ from 192.168.20.26 filename 
grub//images/RHEL6-x86_64/vmlinuz
Mar 22 12:39:36 cobbler in.tftpd[8319]: Client 192.168.20.26 finished 
grub//images/RHEL6-x86_64/vmlinuz
Mar 22 12:39:36 cobbler in.tftpd[8320]: RRQ from 192.168.20.26 filename 
grub//images/RHEL6-x86_64/vmlinuz
Mar 22 12:39:38 cobbler in.tftpd[8320]: Client 192.168.20.26 finished 
grub//images/RHEL6-x86_64/vmlinuz
Mar 22 12:39:38 cobbler in.tftpd[8321]: RRQ from 192.168.20.26 filename 
grub//images/RHEL6-x86_64/initrd.img
Mar 22 12:39:38 cobbler in.tftpd[8321]: tftp: client does not accept options
Mar 22 12:39:38 cobbler in.tftpd[8322]: RRQ from 192.168.20.26 filename 
grub//images/RHEL6-x86_64/initrd.img
Mar 22 12:39:52 cobbler in.tftpd[8322]: Client 192.168.20.26 finished 
grub//images/RHEL6-x86_64/initrd.img

What could I be missing?

Regards,
William

From: Jörgen Maas [mailto:jorgen.m...@gmail.com]
Sent: March-02-17 8:27 AM
To: cobbler mailing list <cobbler@lists.fedorahosted.org>
Subject: [cobbler] Re: Time for a 2.8.1 release?

What's the problem with UEFI ?
I recently updated the grub EFI loaders; get them with

On Thu, Mar 2, 2017 at 1:25 PM, William Muriithi 
<will...@perasotech.com<mailto:will...@perasotech.com>> wrote:
+1

My wish would be to get UEFI working…

Regards,
William

From: Jörgen Maas [mailto:jorgen.m...@gmail.com<mailto:jorgen.m...@gmail.com>]
Sent: March-02-17 4:03 AM
To: cobbler mailing list 
<cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>>
Subject: [cobbler] Re: Time for a 2.8.1 release?

Yes indeed it's about time :) ... there's only one thing i really want sorted 
out... Debian & Ubuntu packaging.
I dont know why, but packaging debs broke with the 2.8.0 release. Hope to take 
a look at it today.
Cheers!

On Wed, Mar 1, 2017 at 10:46 PM, Orion Poplawski 
<or...@cora.nwra.com<mailto:or...@cora.nwra.com>> wrote:
It seems there are several bugfixes checked into the release28 branch.  Time
for a release?

--
Orion Poplawski
Technical Manager  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com<mailto:or...@nwra.com>
Boulder, CO 80301   http://www.nwra.com
___
cobbler mailing list -- 
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
To unsubscribe send an email to 
cobbler-le...@lists.fedorahosted.org<mailto:cobbler-le...@lists.fedorahosted.org>



--
Grtz,
Jörgen Maas

___
cobbler mailing list -- 
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
To unsubscribe send an email to 
cobbler-le...@lists.fedorahosted.org<mailto:cobbler-le...@lists.fedorahosted.org>



--
Grtz,
Jörgen Maas
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Time for a 2.8.1 release?

2017-03-02 Thread William Muriithi

+1

My wish would be to get UEFI working…

Regards,
William

From: Jörgen Maas [mailto:jorgen.m...@gmail.com]
Sent: March-02-17 4:03 AM
To: cobbler mailing list 
Subject: [cobbler] Re: Time for a 2.8.1 release?

Yes indeed it's about time :) ... there's only one thing i really want sorted 
out... Debian & Ubuntu packaging.
I dont know why, but packaging debs broke with the 2.8.0 release. Hope to take 
a look at it today.
Cheers!

On Wed, Mar 1, 2017 at 10:46 PM, Orion Poplawski 
> wrote:
It seems there are several bugfixes checked into the release28 branch.  Time
for a release?

--
Orion Poplawski
Technical Manager  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301   http://www.nwra.com
___
cobbler mailing list -- 
cobbler@lists.fedorahosted.org
To unsubscribe send an email to 
cobbler-le...@lists.fedorahosted.org

--
Grtz,
Jörgen Maas
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Sending keys/files to deployed hosts

2016-10-26 Thread William Muriithi

Hi Tyler,

In your kickstart file, create a post install step that set up a management 
account called chef and also upload chef ssh authorization key

You can then push any sensitives file to the deployed system using ssh tunnel 
between chef and system x at account chef

Regards,

William

From: Tyler Wilson [mailto:k...@linuxdigital.net]
Sent: October-25-16 11:49 PM
To: cobbler@lists.fedorahosted.org
Subject: [cobbler] Sending keys/files to deployed hosts

Hey All,

New Cobbler user here. What is the best method of ensuring deployed nodes have 
sensitive keys (chef keys, ssh, etc) securely uploaded when completed? Am I 
able to send them securely from the cobbler host somehow?

Thanks for any and all tips!
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: teamd support in cobbler

2016-10-19 Thread William Muriithi

Johan

Matt responded to you a while ago with a solution.  Essentially, he
suggested you add some post install configurations on your kickstart
configuration.  I still think its may take more than that as you will
want to use "cobbler system" which extend the basic kickstart
configurations.

If I was in your shoes though, I wouldn't do this on cobbler.  It fit
better on ansible, so I would just set a role for teaming.  If you are
using ansible or puppet, consider looking for a solution from that
angle

Regards
William

On 19 October 2016 at 12:40,   wrote:
> Sorry for my late reaction and thank you all for all your reaction.
>
> my second question in now answered.
>
> My first question was will there be teamd support in cobbler.
>
> What i mean is will there be teamd bonding config option in cobbler web in 
> the next release.
> (bonding in rhel7 is deprecated )
> ___
> cobbler mailing list -- cobbler@lists.fedorahosted.org
> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] UEFI PXE Installation

2016-09-22 Thread William Muriithi

Hello,

I have read an attempted various suggestion on getting cobber to do
UEFI PXE Installation and I haven't had a break though. I am wondering
if someone here had success and how they went about diagnosing the
problem.

Here is my setup:
[root@cobbler ~]# rpm -qa | grep cobbler
cobbler-2.6.11-1.el6.x86_64

I have checked at the project site and this seem to be the most recent
release.  I have also pulled fresh boot loaders from github, so I am
not sure if there is anything I can do with updating as I am up to
date as far as I am concerned.

I am able to do installation fine with BIOS, but when I flip to UEFI,
the booting fails with very unhelpful error.  I have DHCP server
outside of cobbler management but since I am using static IP, I
thought its fine.

I have looked at the ISC DHCP logs, and don't see anything helpful
there.  When I look at the logs after "cobbler sync", I do see
splash.xpm.gz being pushed to tftp.  I have fixed
/etc/cobbler/pxe/efidefault.template as recommended by this old
article, but no luck yet

https://gist.github.com/cwacek/5910195

Any ideal where I should poke going forward?

Regards,

William
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Second DHCP network?

2016-09-19 Thread William Muriithi

David,

This would likely be  server in /etc/cobbler/settings 

server: 192.168.20.123

William
-Original Message-
From: David Lee [mailto:david@ecmwf.int] 
Sent: September-19-16 11:32 AM
To: cobbler mailing list 
Subject: [cobbler] Second DHCP network?

Cobbler folks,

RHEL6; cobbler 2.6.5 (yes, I know it's old!)

I have a feeling this ought to be a trivial question, but I can't find the 
answer.

We have been using Cobbler for several years.  (Indeed, I've even contributed a 
little to the documentation a few years ago.)  That usage has been over a 
single "provisioning" interface on a single provisioning network (similar to 
"10.old.0.0" with the server address "10.old.srv.addr" and that same value 
being in the "settings" field "next_server:").  Very simple.  Works well.

We are adding a second such network over another interface ("10.new.0.0").  
When I PXE boot a client (say "new-client") over this new network, the TFTP 
stuff works fine.  But I then get "error downloading kickstart file" which 
includes the URL of the server's *old* interface (on the original network).

When I do
   cobbler cobbler system getks --name=new-client

the output is full of references to the *old* network, instead of the new, such 
as:

   # Use network installation
   url --url=http://10.old.srv.addr/cblr/links/rhel67-x86_64
   # If any cobbler repo definitions were referenced in the kickstart profile, 
include them here.
   repo --name=el6-x86_64-local 
--baseurl=http://10.old.srv.addr/local/el6/x86_64
   ...

That "10.old.srv.addr" should be the "10.new.srv.addr".

There are no references to the old address in the client's "system", or its 
profile or the Cobbler "foo.ks" kickstart template.

Yet something, somewhere, somehow is clinging tenaciously to the old network.


The "dhcp.template" contains:
   subnet 10.old.foo.0 netmask 255.255.252.0 {
 ...
 next-server$next_server;   <-- presumably using the 
"next_server" from "settings"
   }

   subnet 10.new.0.0 netmask 255.255.0.0 {
 ...
 #next-server$next_server;
 next-server10.new.srv.addr;   <-- explicit reference to 
new network's server address
   }

The "/etc/cobbler/settings" file still has:
   next_server: 10.old.srv.addr
but we want to keep this for the time being to continue to serve our existing 
estate.


Any clues, please?


If the answer is "not available in 2.6.5 but is available later", then I'll set 
about planning an upgrade.

-- David Lee
-- ECMWF
___
cobbler mailing list -- cobbler@lists.fedorahosted.org To unsubscribe send an 
email to cobbler-le...@lists.fedorahosted.org
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: cobbler system add trigger a crash

2016-09-16 Thread William Muriithi

Rick

Thanks.  Was using CLI.  I sought it out.  I had mangled one of the
template in attempt to get cobbler to use UEFI.

Thanks a lot

Sincerely

William

On 15 September 2016 at 15:28, Rick Leir  wrote:
> You say
> "I can use a profile interactively"
> Are you using the CLI interface or the cobbler_web interface?
> I think you are using cobbler_web, so what do you see in   httpd/error_log ?
> ___
> cobbler mailing list
> cobbler@lists.fedorahosted.org
> https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] cobbler system add trigger a crash

2016-09-13 Thread William Muriithi

Good afternoon,

[root@cobbler ~]# rpm -qa | grep cobbler
cobbler-2.6.11-1.el6.x86_64
cobbler-web-2.6.11-1.el6.noarch
[root@cobbler ~]#


I am running into an odd issue where I can use a profile interactively
and have a successful install.  However, if I use that profile and
create a system specific profile, I am not able to have a successful
install for both RHEL6 and RHEL7.  I am getting the following error
from cobbler logs



Tue Sep 13 17:40:59 2016 - INFO | REMOTE save_item(system);
user();
object_id(___NEW___system::gOQ9mTSmZVfODQWldpv/MPykzLe6WuH9Ew==)
Tue Sep 13 17:40:59 2016 - DEBUG | REMOTE CLI Authorized; user(?)
Tue Sep 13 17:40:59 2016 - INFO | add_item(system); ['silicon']
Tue Sep 13 17:40:59 2016 - DEBUG | get_items; ['system']
Tue Sep 13 17:40:59 2016 - DEBUG | done with get_items; ['system']
Tue Sep 13 17:40:59 2016 - WARNING | errors were encountered rendering
the template
Tue Sep 13 17:40:59 2016 - WARNING |
[{'code': u'VFFSL(SL,"grub_menu_items",True)',
  'exc_val': NotFound("cannot find 'grub_menu_items'",),
  'lineCol': (6, 1),
  'rawCode': u'$grub_menu_items',
  'time': 'Tue Sep 13 17:40:59 2016'}]
Tue Sep 13 17:40:59 2016 - INFO | generating:
/var/lib/tftpboot/pxelinux.cfg/01-d4-ae-52-af-7d-da
Tue Sep 13 17:40:59 2016 - INFO | generating:
/var/lib/tftpboot/grub/01-D4-AE-52-AF-7D-DA

The resulting pxelinux.cfg is incomplete as seen below:

[root@cobbler ~]# cat  /var/lib/tftpboot/pxelinux.cfg/01-d4-ae-52-af-7d-da
default=0
timeout=5
splashimage=(nd)/splash.xpm.gz

$grub_menu_items


Have anybody seen this before?
Regards,

William
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org

[cobbler] Networking snippnet with new network style names

2016-09-12 Thread William Muriithi

Hello

I have been struggling attempting to get cobbler to work with RHEL6.
The problem is, RHEL 6.8 is coming up with the interface name as em1,
but somehow, the kickstart snippet below end up assigning the
interface the name eth0.  I have temporarily  commented the snippet as
show below and was able to have a successful installation after that.

# Network information
#$SNIPPET('network_config')
network --onboot no --device em1 --bootproto dhcp --noipv6
network --onboot no --device em2 --bootproto dhcp --noipv6

Have anybody been able to get cobbler working with interface names
like em1 or p3p1?   My problem is,  I have different hardware and
therefore don't have flexibility of hard coding the interface name in
the kickstart.  Any pointer would be highly appreciated

Regard,

William
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org

[cobbler] Re: Error associating a system to a profile

[cobbler] Error associating a system to a profile

[cobbler] Re: koan EXSi support

[cobbler] koan EXSi support

[cobbler] Re: Time for a 2.8.1 release?

[cobbler] Re: Time for a 2.8.1 release?

[cobbler] Re: Sending keys/files to deployed hosts

[cobbler] Re: teamd support in cobbler

[cobbler] UEFI PXE Installation

[cobbler] Re: Second DHCP network?

[cobbler] Re: cobbler system add trigger a crash

[cobbler] cobbler system add trigger a crash

[cobbler] Networking snippnet with new network style names

13 matches

Site Navigation

Mail list logo

Footer information