Re: [cobbler] upgrade issue
by Ed Deloye
Orion,
Thanks for the help. I discovered the problem, somehow on character in the path to the initrd and kernel got changed to upper-case. After correcting that I stopped and restarted the cobblerd daemon and all distros and profiles were visible.
Ed
10 years, 2 months
Re: [cobbler] upgrade issue
by Ed Deloye
Message: 2
Date: Fri, 7 Feb 2014 21:14:16 +0000
From: Ed Deloye <EDeloye(a)rfmd.com>
To: "cobbler(a)lists.fedorahosted.org" <cobbler(a)lists.fedorahosted.org>
Subject: [cobbler] upgrade issue
Message-ID:
<58EDF9C9D1469D43A32AE5B5B8C4F83F011411840A(a)rfgbmail2.internal.rfmd.com>
Content-Type: text/plain; charset="utf-8"
Process:
1) Built a new system
2) Install cobbler 2.4.0 on the new system
3) Stopped cobblerd on new system
4) Copied /var/lib/cobbler/config from system running cobbler 2.2.1
5) Started cobblerd on the new system
After this I see all the distros and profiles except the ones for RHEL 5.10. This is true in both the CLI and the web interface. Does anyone have any ideas as to why and what I can do to correct this?
Thanks,
Ed
There are basically two types of people. People who accomplish things, and people who claim to have accomplished things. The first group is less crowded.
Mark Twain<http://www.brainyquote.com/quotes/quotes/m/marktwain393535.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/cobbler/attachments/20140207/d6e...>
------------------------------
Message: 3
Date: Fri, 07 Feb 2014 19:21:04 -0700
From: Orion Poplawski <orion(a)cora.nwra.com>
To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
Subject: Re: [cobbler] upgrade issue
Message-ID: <52F59490.10809(a)cora.nwra.com>
Content-Type: text/plain; charset=UTF-8
On 02/07/2014 02:14 PM, Ed Deloye wrote:
> Process:
>
>
>
> 1) Built a new system
>
> 2) Install cobbler 2.4.0 on the new system
>
> 3) Stopped cobblerd on new system
>
> 4) Copied /var/lib/cobbler/config from system running cobbler 2.2.1
>
> 5) Started cobblerd on the new system
>
>
>
> After this I see all the distros and profiles except the ones for RHEL
> 5.10. This is true in both the CLI and the web interface. Does anyone
> have any ideas as to why and what I can do to correct this?
>
>
>
> Thanks,
>
> Ed
>
Are all of the paths referenced in the RHEL 5.10 configs still present?
cobbler will not display distros/profiles for which various kernel/initrd/etc? items are not found.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Orion,
Yes, the path to both the initrd and kernel are still present. It is that same path that is used in all of the other distros that are being displayed.
Ed
10 years, 2 months
upgrade issue
by Ed Deloye
Process:
1) Built a new system
2) Install cobbler 2.4.0 on the new system
3) Stopped cobblerd on new system
4) Copied /var/lib/cobbler/config from system running cobbler 2.2.1
5) Started cobblerd on the new system
After this I see all the distros and profiles except the ones for RHEL 5.10. This is true in both the CLI and the web interface. Does anyone have any ideas as to why and what I can do to correct this?
Thanks,
Ed
There are basically two types of people. People who accomplish things, and people who claim to have accomplished things. The first group is less crowded.
Mark Twain<http://www.brainyquote.com/quotes/quotes/m/marktwain393535.html>
10 years, 2 months
cobbler_web file does not exist
by Steven Lokie
Hiya all,
Having a weird issue with cobbler_web
I'm trying to get the web interface working - I had some issues with the
cobblerd instance, but found out the correct info.
However now the web interface is no longer working
cobbler_web.conf
<VirtualHost *:80>
ServerName cobbler.domain.corp
ServerAlias cobbler
# This configuration file enables the cobbler web
# interface (django version)
# Force everything to go to https
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} ^/cobbler_web
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI}
WSGIScriptAlias /cobbler_web /usr/share/cobbler/web/cobbler.wsgi
</VirtualHost>
I look in the file system and see the wsgi file
[root@utilserver03 conf.d]# ls -al /usr/share/cobbler/web/
total 60
drwxr-xr-x 3 apache apache 4096 Feb 6 10:53 .
drwxr-xr-x 3 root root 4096 Feb 6 10:53 ..
drwxr-xr-x 4 apache apache 4096 Feb 6 10:53 cobbler_web
-rw-r--r-- 1 apache apache 320 Jun 19 2013 cobbler.wsgi
but when I go to the page I get Not Found and the error in the log displays
as
File does not exist: /var/www/cobbler_web
Any help would be great - thank you
10 years, 2 months
How to override next-server for some tagged hosts
by Bret Wortman
We have a configuration where we'd like to run a single cobbler
instance, but we have nodes that are widely distributed across network
links of varying quality. We need to (and do) host the initial boot
image files locally for those subnets.
What I'd like to do is find a way to tag those subnets by name so that
new systems, when they get added, get told that their next-server at the
group level is our main cobbler server, but their initial next-server at
the system level is the host for the boot files. Here's how one looks
right now, and it does work this way:
dhcp.template (partial)
#for dhcp_tag in $dhcp_tags.keys():
:
group {
next-server $next_server:
host $iface.name {
:
#if $dhcp_tag == "site1"
next-server 192.168.43.18;
#end if
:
What I'd _like_ to do, instead of expanding that "if $dhcp_tag ==" bit
once more for each site and leading to template file brittleness, is to
replace it with something like:
next-server $iface.next-server;
But I have no idea how to influence the value of $iface.next-server.
Where does that come from and how do I set it? It's referenced elsewhere
in dhcp.template, and it appears to be part of the output of cobbler
system dumpvars, but /setting/ it...?
--
*Bret Wortman*
http://damascusgrp.com/
http://about.me/wortmanbret
10 years, 2 months
Kickstart generation failes with "BOOTAPI instance has no attribute 'kickgen'
by Speagle , Andy
Howdy Folks,
I'm working on setting up a remote Cobbler instance that replicates from a master. However, I'm having an issue with the remote. The master Cobbler server doesn't suffer this problem. When I run a simple "getks" ... such as:
cobbler profile getks --name=<some profile>
I get the standard render failure:
# This kickstart had errors that prevented it from being rendered correctly.
# The cobbler.log should have information relating to this failure.
And looking in the cobbler.log ... I see this.
Thu Feb 6 11:39:53 2014 - INFO | REMOTE generate_kickstart; user(?)
Thu Feb 6 11:39:53 2014 - INFO | generate_kickstart
Thu Feb 6 11:39:53 2014 - INFO | Exception occured: <type 'exceptions.AttributeError'>
Thu Feb 6 11:39:53 2014 - INFO | Exception value: BootAPI instance has no attribute 'kickgen'
Thu Feb 6 11:39:53 2014 - INFO | Exception Info:
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 1025, in generate_kickstart
return self.api.generate_kickstart(profile,system)
File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 684, in generate_kickstart
return self.kickgen.generate_kickstart_for_profile(profile)
Can someone point me in the right direction?
Thanks!
Andy Speagle
10 years, 2 months
Replication fails with "connection refused"
by Speagle , Andy
Hi Folks,
I'm having some trouble getting replication going under the latest 2.5 dev release. I suspect there's something up with my configuration, but I can't seem to find what it is. I cloned my master cobbler server to a remote site, change the relevant hostname pieces and the new slave server seems to work in itself locally. But when I attempt to replicate from the master, I get the following.
Can anyone clue me in as to what might be happening?
(servernames replaced to protect the innocent)
Andy Speagle
[root@<slave> ~]# cobbler replicate --master=<master> --sync-all
task started: 2014-02-05_080305_replicate
task started (id=Replicate, time=Wed Feb 5 08:03:05 2014)
cobbler_master = <master>
distro_patterns = []
profile_patterns = []
system_patterns = []
repo_patterns = []
image_patterns = []
mgmtclass_patterns = []
package_patterns = []
file_patterns = []
omit_data = False
sync_all = True
use_ssl = False
XMLRPC endpoint: http://<master>/cobbler_api
test ALPHA
test BETA
Exception occured: <class 'socket.error'>
Exception value: [Errno 111] Connection refused
Exception Info:
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 87, in run
rc = self._run(self)
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 216, in runner
self.logger
File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 1061, in replicate
use_ssl = use_ssl
File "/usr/lib/python2.6/site-packages/cobbler/action_replicate.py", line 358, in run
self.local.ping()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 739, in send
self.connect()
File "/usr/lib64/python2.6/httplib.py", line 720, in connect
self.timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
!!! TASK FAILED !!!
10 years, 3 months
repos on two networks
by Bret Wortman
I've got cobbler instances on two networks. One is connected to the
internet, the other development network is not.
Cobbler on the net-connected network is blissfully happy and syncs its
repos daily. We can use FedUp while pointing at its repos (at least, I'm
90% sure we've done this) and setting up F20 and C6.5 clients is easy as
pie.
What I'd like to do is basically make a copy of
/var/www/cobbler/repo_mirror and copy it to the dev network and "fake
out" its cobbler instance to think that it has the latest repos as well.
(a) Is this possible?
(b) Do I need to do anything special with Cobbler after bringing the
newest repo_mirror contents over to refresh it somehow? I know that
running cobbler reposync would be a mistake....
(c) Short of finding a way to replicate mirrors.kernel.org's complete
directory trees somewhere on my internal network just so Cobbler can see
them, is there another way to accomplish this if my idea's a bust?
Thanks!
--
*Bret Wortman*
http://damascusgrp.com/
http://about.me/wortmanbret
10 years, 3 months
help installing cobbler on Ubuntu 12.04
by Tommy Ash
Hello,
Do you have a step-by-step how-to for installing Cobbler on Ubuntu 12.04? I'm having some issues and can't seem to find any helpful articles.
I was getting some dhcp templating errors after a cobbler system add then cobbler sync
Thanks,
Tommy Ash
10 years, 3 months
Cobbler 2.4.1 released
by Jörgen Maas
Hey all,
It has been quiet for way too long, so i decided to get the ball rolling
again and cut the release for Cobbler 2.4.1. This release contains mostly
bug fixes and minor enhancements to existing features.
Improved Features:
- Many distro_signatures updates
- Anamon logfile support has been extended
- Allow the use of systems without associated kickstart
- Koan now supports the qed disk driver
- Automatic cobbler_web restart after cobblerd restart
- Improved Puppet certificate management
- Cobbler replication now supports ssl
- Koan gained support for --proxy & --server options
- Xen guest provisioning in koan
- Added a Cobbler post install report ignorelist
- Authentication token expiration time is now configurable
- Autentication passthru is now again functional
- SELinux detection in koan
Bugfixes:
- Improved logging and exception handling in many places
- Several fixes for running Cobbler on OpenSUSE and SLES
- Better proxy handling in buildiso
- Concurrency/locking improvements
- Removed some hardcoded paths, making life easier for downstream
packagers
- Add missing (sub)commands to the CLI
- Several Makefile fixes
- Small improvements to cobbler-web
- Many fixes to koan
- Several WSGI related improvements
- Many more...
I'd like to invite everyone to help us out by targeting bugs in the 2.4
branch and/or develop new features on the master branch (which will be
released as 2.6.0 in a couple of weeks).
Cheers,
Jörgen
10 years, 3 months
