[Spacewalk-list] issue with new channel

[Yang Li]

I have new channel setup in our spacewalk server. the repo sync looks fine. on 
client side, it yum repolist looks fine, but when I do yum update, it will 
break out with following error:

# yum update  --nogpgcheck
Loaded plugins: rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

failed to retrieve repodata/repomd.xml from ius_rhel7_x86_64
error was [Errno 14] HTTPS Error 404 - Not Found

this is what I see in repo sync log:

# cat ius_rhel7_x86_64.log
2019/01/11 10:45:00 -04:00 Command: ['/usr/bin/spacewalk-repo-sync', 
'--channel', 'ius_rhel7_x86_64', '--type', 'yum']
2019/01/11 10:45:00 -04:00 Sync of channel started.
2019/01/11 10:45:00 -04:00 Repo URL: 
http://archive.linux.duke.edu/ius/stable/Redhat/7/x86_64/
2019/01/11 10:45:01 -04:00 Packages in repo:   737
2019/01/11 10:45:02 -04:00 Packages already synced:  0
2019/01/11 10:45:02 -04:00 Packages to sync:   737
2019/01/11 10:45:02 -04:00 1/737 : apcu-panel56u-4.0.11-2.ius.el7-0.noarch
2019/01/11 10:45:03 -04:00 2/737 : apr15u-1.5.2-2.ius.el7-0.x86_64
2019/01/11 10:45:05 -04:00 3/737 : apr15u-debuginfo-1.5.2-2.ius.el7-0.x86_64
...

2019/01/11 10:58:30 -04:00 731/737 : 
uwsgi-plugin-python35u-debuginfo-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:31 -04:00 732/737 : 
uwsgi-plugin-python35u-debuginfo-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:32 -04:00 733/737 : 
uwsgi-plugin-python36u-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:32 -04:00 734/737 : 
uwsgi-plugin-python36u-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:33 -04:00 735/737 : 
uwsgi-plugin-python36u-debuginfo-2.0.17.1-1.ius.el7-0.x86_64
2019/01/11 10:58:33 -04:00 736/737 : 
uwsgi-plugin-python36u-debuginfo-2.0.16-1.ius.el7-0.x86_64
2019/01/11 10:58:34 -04:00 737/737 : yum-plugin-replace-0.2.7-1.ius.el7-0.noarch
2019/01/11 10:58:35 -04:00 Linking packages to channel.
2019/01/11 10:58:42 -04:00 Repo 
http://archive.linux.duke.edu/ius/stable/Redhat/7/x86_64/ has 0 errata.
2019/01/11 10:58:42 -04:00 Sync of channel completed in 0:13:41.

What could be the issue?

Thanks,
Yang
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

[p.cook...@bham.ac.uk]

Hi Jérôme

Thanks for your feedback. I've read that "spacewalk-clone-by-date" gives some 
unexpected results, really doesn't sound very reliable or therefore, of much 
interest to me!

I've started some testing of "spacewalk-manage-channel-lifecycle" and, 
initially, that seems to be giving more consistent results. As the name 
suggests, maybe it's more likely to manage a dev/test/prod lifecycle/workflow 
better? It seems to just capture the state of the source channel as opposed to 
copying every package, from the related repo, in to new repo's each time. This 
makes me think that you'd have to ensure the source repo's were retained while 
dev/test/prod clones were still referencing it but far less disk space is 
required. I'm waiting to see what happens when the source is re-synced and more 
packages are added to it, as I wouldn't want the clone repo's to get any 
updated packages as well!

Regards
Phil


From: spacewalk-list-boun...@redhat.com  On 
Behalf Of jerome.me...@lcsystems.ch
Sent: 16 January 2019 12:13
To: 'spacewalk-list@redhat.com' 
Subject: Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi Phil,

I'm using the spacewalk-clone-by-date command and there's my point of view and 
experience.
I've created three channels: dev,test and prod with spacewalk-clone-by-date. 
Each month in a specific date I resync these three channels with the same 
commands. In this process errata will be synchronized with their dependencies.
All was perfect until I notice that not all packages will be added. By example 
new package version but not an errata will not be updated. At the end, the 
channels hasn't the same packages number has it's parents.
I'll perhaps make some test with other commands but if you do any more tests on 
your side, I'll be interested in your results.
Unfortunately I didn't any more informations on web regarding this problematic.

Regards,
Jérôme

From: 
spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of 
p.cook...@bham.ac.uk
Sent: Dienstag, 15. Januar 2019 14:01
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test 
and Production after sufficient testing has been performed. If I never re-sync 
these repositories obviously they'll remain static and could be used for the 
whole workflow. However, other service areas may want their environments 
patched at different times with additional patches. I guess I could just create 
similar Channels/Repositories, at a later time, but that would be time 
consuming and need more disk space. I've seen references to cloning using 
WebUI, spacecmd -- softwarechannel_clone, spacewalk-clone-by-date or 
spacewalk-manage-channel-lifecycle and can research these further but just 
wondering what people have found to be the easiest and most reliable solution 
really?

Regards
Phil

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

[Jérôme Meyer]

Hi Phil,

I'm using the spacewalk-clone-by-date command and there's my point of view and 
experience.
I've created three channels: dev,test and prod with spacewalk-clone-by-date. 
Each month in a specific date I resync these three channels with the same 
commands. In this process errata will be synchronized with their dependencies.
All was perfect until I notice that not all packages will be added. By example 
new package version but not an errata will not be updated. At the end, the 
channels hasn't the same packages number has it's parents.
I'll perhaps make some test with other commands but if you do any more tests on 
your side, I'll be interested in your results.
Unfortunately I didn't any more informations on web regarding this problematic.

Regards,
Jérôme

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of p.cook...@bham.ac.uk
Sent: Dienstag, 15. Januar 2019 14:01
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Managing Channels/Repositories - Patching Workflow

Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test 
and Production after sufficient testing has been performed. If I never re-sync 
these repositories obviously they'll remain static and could be used for the 
whole workflow. However, other service areas may want their environments 
patched at different times with additional patches. I guess I could just create 
similar Channels/Repositories, at a later time, but that would be time 
consuming and need more disk space. I've seen references to cloning using 
WebUI, spacecmd -- softwarechannel_clone, spacewalk-clone-by-date or 
spacewalk-manage-channel-lifecycle and can research these further but just 
wondering what people have found to be the easiest and most reliable solution 
really?

Regards
Phil



smime.p7s
Description: S/MIME cryptographic signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] package install fail

[p.cook...@bham.ac.uk]

Hi

Personally, I’ve only been using Spacewalk for patching, rather than 
provisioning, although that is my next objective. However, it would seem it 
can’t find the package and therefore, you’re not pointing to the right area or 
there’s sort of configuration issue. May be the following link will help or you 
could search for similar?

https://unix.stackexchange.com/questions/284251/centos-kickstart-packages

Good luck
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of rui.a.z...@nokia-sbell.com
Sent: 16 January 2019 02:40
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] FW: package install fail



From: Zhou, Rui A. (NSB - CN/Shanghai)
Sent: 2019年1月16日 10:28
To: 'spacewalk-list@redhat.com' 
mailto:spacewalk-list@redhat.com>>
Cc: Zhu, Ting (NSB - CN/Shanghai) 
mailto:ting@nokia-sbell.com>>
Subject: package install fail

Hi: dears
   I had install the spacewalk2.8,  it all works fine, client can register to 
server and spacewalk can send cmd etc…
But when I use the spacewalk to install os, it always appears the following 
tips, of course the five packages wrote in the KS.
I understand it will find the configured tree path(/var/ftp/pub/CentOS7) to 
install needed packages, but it not work.
So I try to config cobbler repo(rndmirrors), It doesn't seem to work either.  
It's been bothering me for a long time.
Am I missing any configuration? Hope to be helped! Thank you!


[root@splunk-server repo_mirror]# ls -la /var/www/cobbler/repo_mirror/rndmirrors
total 368
drwxr-xr-x  4 root   root   54 Jan 15 23:35 .
drwxr-xr-x  3 apache apache 24 Jan 15 19:12 ..
-rw-r--r--  1 root   root   373476 Jan 15 23:35 comps.xml
drwxr-xr-x  2 root   root   29 Jan 15 19:12 .origin
drwxr-xr-x 33 root   root  285 Jan 15 23:35 Packages


[cid:image001.png@01D4AD76.B0D82B10]
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list