Hello, 

please see the snippet of my kickstart file: 

# Kickstart config file generated by Spacewalk Config Management
# Profile Label : CentOS7-x86_64-ks
# Date Created  : 2015-11-16 11:37:49.854506

install
text
url --url http://spacewalk.domain.de/ks/dist/org/1/CentOS7-x86_64-dist
lang en_US
keyboard de
zerombr
clearpart --all
bootloader --location mbr
timezone Europe/Berlin
auth --enableshadow --passalgo=sha256
rootpw --iscrypted ...
selinux --enforcing
reboot
skipx
repo --name=centos7-x86_64-extra 
--baseurl=http://spacewalk.domain.de/ks/dist/child/centos7-x86_64-extra/CentOS7-x86_64-dist
repo --name=centos7-x86_64-updates 
--baseurl=http://spacewalk.domain.de/ks/dist/child/centos7-x86_64-updates/CentOS7-x86_64-dist
repo --name=centos7-x86_64 
--baseurl=http://spacewalk.domain.de/ks/dist/child/centos7-x86_64/CentOS7-x86_64-dist
repo --name=centos7-x86_64-centosplus 
--baseurl=http://spacewalk.domain.de/ks/dist/child/centos7-x86_64-centosplus/CentOS7-x86_64-dist
repo --name=spacewalkclient-x86_64-rhel7 
--baseurl=http://spacewalk.domain.de/ks/dist/child/spacewalkclient-x86_64-rhel7/CentOS7-x86_64-dist
repo --name=epel7-x86_64 
--baseurl=http://spacewalk.domain.de/ks/dist/child/epel7-x86_64/CentOS7-x86_64-dist
autopart --type=lvm

%packages 
@ Base
perl
wget
rhn-setup
rhn-check
rhn-client-tools
%end

%pre 

I cant see any dependency. But IF there is a dependency to vim, why does it 
fail to install? 

I currently running Version 2.3 - I thought maybe the update would help 
kickstarting CentOS. 


kind regards, 
Philipp 
----- Original Message -----

From: "Jeffery Kalchik" <[email protected]> 
To: [email protected] 
Sent: Monday, November 16, 2015 7:55:15 PM 
Subject: Re: [Spacewalk-list] Kickstarting CentOS 



Packages will get auto-selected when they’re listed a prerequisites or 
requirements of requested packages. A package that you’re installing has vim as 
a dependency somewhere in its prerequisites tree. 



As far as the rest of it goes, I’m not sure where I’d start. Is this on your 
existing 2.3 server? Or on your 2.4 server? (I see you’ve got another message 
in about upgrades.) 



Jeff Kalchik 

Systems Engineering 

Land O’Lakes 




From: [email protected] 
[mailto:[email protected]] On Behalf Of Philipp Wehling 
Sent: Monday, November 16, 2015 5:24 AM 
To: [email protected] 
Subject: Re: [Spacewalk-list] Kickstarting CentOS 





Hello, 





please see the logs attached. 





Im clueless ... 








kind regards, 


Philipp 



----- Original Message -----



From: "Philipp Wehling" < [email protected] > 
To: [email protected] 
Sent: Monday, November 16, 2015 9:26:09 AM 
Subject: Re: [Spacewalk-list] Kickstarting CentOS 





Hello, 





the idea with the network tracing app was already in my mind. Before doing 
that, I checked a working kickstart of ScientificLinux 6/7. There it is the 
same: The packages are downloaded partially at first. After that, they are 
downloaded and installed completly. 





Facing the problem, I have no idea, why the kickstart-profile wants to install 
vim. There is no configuration to do that. I will get the logs and provide them 
to you for analysis soon. 








kind regards, 


Philipp 



----- Original Message -----



From: "Jeffery Kalchik" < [email protected] > 
To: [email protected] 
Sent: Saturday, November 14, 2015 7:13:26 PM 
Subject: Re: [Spacewalk-list] Kickstarting CentOS 





Whether or not the package is essential doesn’t matter. Any package in the 
configured channels or repositories should be usable. 



I’ve had issues where multiple packages exist that are named identically 
(different channels,) but compiled or built from different sources, leading to 
different checksums. My only workaround for this particular problem is to 
identify those package name collisions, and remove the packages that I do not 
want to use. 



Philipp, your issue looks a bit different. The error you’re getting seems like 
a network transmission issue. I’d be tempted to fire up wireshark (or some 
other network tracing app) to check traffic in/out of your Spacewalk server. 
It’d be interesting to see what differences exist in the network captures 
between the anaconda download and the wget. 



Jeff Kalchik 

Systems Engineering 

Land O’Lakes 




From: [email protected] [ 
mailto:[email protected] ] On Behalf Of Deepjoy Choudhury 
Sent: Friday, November 13, 2015 8:40 AM 
To: [email protected] 
Subject: Re: [Spacewalk-list] Kickstarting CentOS 




Please try excluding this package in the Kickstart. 

Vim is not an essential package. 



Br 

Deepjoy 




From: [email protected] [ 
mailto:[email protected] ] On Behalf Of Philipp Wehling 
Sent: Thursday, November 12, 2015 9:23 PM 
To: [email protected] 
Subject: [Spacewalk-list] Kickstarting CentOS 





Hello, 





I have problems kickstarting CentOS 6/7. 





I already googled and found this discussion: 


http://comments.gmane.org/gmane.linux.redhat.spacewalk.user/12920 








I have got the same problems. 





During the kickstarting, anaconda tries to get the vim-package: 





192.168.0.241 - - [12/Nov/2015:16:30:45 +0100] "GET 
/ks/dist/org/1/CentOS7-x86_64-dist/Packages/vim-common-7.4.160-1.el7.x86_64.rpm 
HTTP/1.1" 206 252040 "-" "urlgrabber/3.10 yum/3.4.3" 





If I do a wget to the same url (from the same host): 





192.168.0.241 - - [12/Nov/2015:16:38:54 +0100] "GET 
/ks/dist/org/1/CentOS7-x86_64-dist/Packages/vim-common-7.4.160-1.el7.x86_64.rpm 
HTTP/1.1" 200 6211720 "-" "Wget/1.14 (linux-gnu)" 








In packaging.log I can see following errors: 





error populating transaction after 10 retries: failure: 
Packages/vim-common...rpm from anaconda: [Errno 256] No more mirrors to try. 


http://<URL>/Packages/vim-common...rpm: [Errno -1] Header is not complete. 





The solution mentioned above isnt working for me. 





Are there any other ideas? 








kind regards, 


Philipp 


This message may contain confidential material from Land O'Lakes, Inc. (or its 
subsidiary) for the sole use of the intended recipient(s) and may not be 
reviewed, disclosed, copied, distributed or used by anyone other than the 
intended recipient(s). If you are not the intended recipient, please contact 
the sender by reply email and delete all copies of this message. 
_______________________________________________ 
Spacewalk-list mailing list 
[email protected] 
https://www.redhat.com/mailman/listinfo/spacewalk-list 






_______________________________________________ 
Spacewalk-list mailing list 
[email protected] 
https://www.redhat.com/mailman/listinfo/spacewalk-list 



This message may contain confidential material from Land O'Lakes, Inc. (or its 
subsidiary) for the sole use of the intended recipient(s) and may not be 
reviewed, disclosed, copied, distributed or used by anyone other than the 
intended recipient(s). If you are not the intended recipient, please contact 
the sender by reply email and delete all copies of this message. 
_______________________________________________ 
Spacewalk-list mailing list 
[email protected] 
https://www.redhat.com/mailman/listinfo/spacewalk-list 

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to