You are correct, using the repodata from the DVD will prevent you from adding packages to the base channel and installing them with Anaconda. Your options are either to add the packages to a child channel, and include that child channel in the kickstart (not activation keys), or to generate new repodata using the packages that are actually in your base channel.
To generate a new set of repodata, you will need to put all the packages in the base channel in a directory tree and run createrepo. Anaconda requires you to have the comps.xml file, which is not generated by Spacewalk. You can safely copy the comps.xml from the DVD and give it to createrepo. Jonathan On Jan 24, 2013, at 3:49 PM, Jon Miller <[email protected]<mailto:[email protected]>> wrote: (As I inch closer to a solution, I'll keep replying here... tell me if I should stop) My current theory, as to why I can't seem to pull down "rhnlib" and "spacewalk-koan" from my Spacewalk channel is that my distribution's repodata/ was created from the original FC18 DVD which wouldn't have those two packages. The implication is that I've setup my distribution incorrectly or I've missed a step? Does that pretty plausible? If so, any ideas / suggestions about getting around that? Here is how I setup my distribution: 1. Create a Distribution Path - Need to keep distributions available to enable kickstarts #+begin_src shell sudo mkdir -p /var/satellite/distros/fedora18-x86_64 cd /local/mnt/workspace/isos sudo mount -o loop Fedora-18-x86_64-DVD.iso /mnt sudo rsync -a --exclude="*.rpm" /mnt/ /var/satellite/distros/fedora18-x86_64 sudo umount /mnt #+end_src 2. Create a Kickstart Distribution in Spacewalk (Systems -> Kickstart -> Distributions -> "create new distribution") a. Enter the fields using the information from the ISO mount point created + Distribution Label: fedora-18-x86_64 + Tree Path: /var/satellite/distros/fedora18-x86_64 + Base Channel: Fedora 18 Core x86_64 + Installer Generation: Fedora b. Submit via "Create Kickstart Distribution" Thanks, Jon Miller On Thu, Jan 24, 2013 at 9:16 AM, Jon Miller <[email protected]<mailto:[email protected]>> wrote: Okay, next test... trying to simplify my question / issue by taking kickstart out of the equation. I believe the real question is why are the packages I uploaded via "rhnpush" not available to my client? This time around, I kickstarted a machine and it was setup with the normal Fedora repos available and I installed rhnlib & spacewalk-koan, registered the client to my Spacewalk server so that I would also have it as a repo, then disabled the Fedora repos, erased rhnlib & spacewalk-koan and finally testing that I can not find those packages on my Spacewalk server from a client perspective. Here is the puzzling part: If I go to my FC18 channel in the UI, click on packages and then search for spacewalk I find the spacewalk-koan package. I can even click the download from the UI. So, the real question is how can I upload a package via rhnpush, see it available within the UI but client not see it as being available? My rhnpush command: rhnpush -u "${SPACEWALK_USER}" -p "${SPACEWALK_PASS}" -v --channel=$CHANNEL --server=http://localhost<http://localhost/> --dir=$dir Thanks, Jon Miller P.S. My procedure to help isolate the client using only the spacewalk repo: $ yum repolist repo id repo name status fedora/18/x86_64 Fedora 18 - x86_64 33,868 updates/18/x86_64 Fedora 18 - x86_64 - Updates 9,074 repolist: 42,942 repolist: 47,120 $ yum -y install rhnlib spacewalk-koan $ rhnreg_ks --activationkey=2-espresso-test --username admin --password mypass --serverUrl http://spacewalk.example.com/XMLRPC $ yum repolist repo id repo name status fedora/18/x86_64 Fedora 18 - x86_64 33,868 fedora18-x86_64 Fedora 18 Core x86_64 4,178 updates/18/x86_64 Fedora 18 - x86_64 - Updates 9,074 $ sed -i 's/enabled=1/enabled=0/g' /etc/yum.repos.d/*repo $ yum repolist repo id repo name status fedora18-x86_64 Fedora 18 Core x86_64 4,178 repolist: 4,178 $ yum -y erase rhnlib spacewalk-koan $ yum search rhnlib spacewalk-koan Warning: No matches found for: rhnlib Warning: No matches found for: spacewalk-koan No Matches found On Wed, Jan 23, 2013 at 6:47 PM, Jon Miller <[email protected]<mailto:[email protected]>> wrote: I'm hoping by attaching some extra KS logs, captured during a kickstart, that someone would be able to notice something about not being able to use the "rhnlib" and "spacewalk-koan" RPMs. Any ideas or suggests are appreciated. Thanks, Jon Miller On Wed, Jan 23, 2013 at 2:03 PM, Jon Miller <[email protected]<mailto:[email protected]>> wrote: Of the required client packages, "pyOpenSSL" and "libxml2-python" were available from the base set of packages on the 4G DVD where as "rhnlib" and "spacewalk-koan" were not. I'm able to kickstart a FC18 client but it is obviously not registering with Spacewalk automatically. I then used the yum command "yum install --downloadonly --downloaddir=/tmp rhnlib spacewalk-koan" to get a local copy of the missing RPMs along with their dependencies. Finally, I re-used the rhnpush command to upload an extra 28 packages into my FC18 channel and while I can confirm they are there via the Spacealk UI, re-kickstarting still complains about missing the same two packages. Is there some sort of sync, cache flush or the like that I need to perform before a new kickstart can see that those packages are now available for installation? Thanks, Jon Miller #------ More Details about what I did to resolve my dependencies -------- # From the freshly installed FC18 client mkdir /tmp/rmps && yum install -y --downloadonly --downloaddir=/tmp/rmps rhnlib spacewalk-koan # Then from your Spacewalk server, scp those RPMs to your current directory: CHANNEL=fedora18-x86_64 # Your channel probably varies from mine read -p "What is your spacewalk user name: " -e -i "admin-crad" SPACEWALK_USER read -p "What is your spacewalk ${SPACEWALK_USER} password: " -s -e SPACEWALK_PASS rhnpush -u "${SPACEWALK_USER}" -p "${SPACEWALK_PASS}" -v --channel=$CHANNEL --server=http://localhost<http://localhost/> --dir=. On Mon, Jan 21, 2013 at 1:40 AM, Jan Pazdziora <[email protected]<mailto:[email protected]>> wrote: On Mon, Jan 21, 2013 at 10:32:21AM +0100, Miroslav Suchy wrote: > On 19.1.2013 03:28, Jon Miller wrote: > >I tried looking for available client download URLs but was unsuccessful. > >What is the current timeline for making those packages available? > > Spacewalk client is already part of Fedora. So it is already > available there (and also in rawhide). > Just do: > yum groupinstall 'Spacewalk Client' Nightly client repos are now available for Fedora 18 as well: http://yum.spacewalkproject.org/nightly-client/Fedora/18/ -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list Jonathan DeHaan IT Manager Nexstar Broadcasting Group
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
