When I try to run the following command /usr/bin/spacecmd -y
--username=$USERNAME --password=$PASSWORD softwarechannel_adderratabydate -p
$SOURCE_CHANNEL $CLONE_CHANNEL $FROMDATE $TODATE >> $LOGFILE 2>&1 I get an
error saying that credentials are invalid.
When I remove the –p option this work
check the taskomatic logs
there may be one of two things happening.
1 there is a delay after you add a package before it becomes visible
to the target servers because taskomatic needs to generate new XML
files for yum.
2 if you have a very large channel then occasionally you may see the
repodata jo
You are not using osad, that would run the job instantly. rhnsd default
interval is 240 minutes. Can be set to minimum of 60 in /etc/sysconfig/rhn/rhnsd
Am 16.11.2016 16:49 schrieb Oucema Bellagha :
>
> Hi folks,
>
>
> I implemented a test environment for Spacewalk [spacewalk server + Spacewalk
All systems are subscribing the same channel that packages have been pushed to?
Am 16.11.2016 11:01 schrieb Artem Pastukhov :
>
> Hi all!
> I'm truing to make CI/CD system with spacewalk 2.5
>
> There is three seps
> make rpm
> push it to spacewalk with rhnpush
> Schedule to install it to group of
Hi folks,
I implemented a test environment for Spacewalk [spacewalk server + Spacewalk
proxy], everything is working good; I added new channel for updates and added
the client to the server and so on, but the problem is when I schedule any
event (update, install or whatever) the server deploy
Hi all!
I'm truing to make CI/CD system with spacewalk 2.5
There is three seps
1. make rpm
2. push it to spacewalk with rhnpush
3. Schedule to install it to group of hosts with schedulePackageInstall
API call
And i have troubles with last step. Sometime approximately 10% of cases i'm
