# SM3: Failed patch job scheduled for future time **URL:** \ **Category:** SUSE Multi Linux Manager\ **Created:** [April 7, 2017, 5:10pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649 "2017-04-07T17:10:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\ **Post date:** [April 7, 2017, 5:10pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/1 "2017-04-07T17:10:23Z")
I have the latest SM3 version installed and in testing. I attempted to install some patches to a SLES12-SP1 system for a future time. The action was scheduled to begin no earlier than 12:50AM CDT and, according to the event history, it was completed at 01:00AM CDT. The patch attempt failed. However, the event history provides absolutely no detailed information as to why it failed. The details from the job history follow. How can I get detailed information on why this job failed? [QUOTE]This action will be executed after 4/7/17 12:50:00 AM CDT This action’s status is: Failed. The client completed this action on 4/7/17 1:00 AM Client execution returned There was no job cache entry. (code -1) Patches Affected: SUSE-12-SP1-2017-451 - moderate: Security update for wget SUSE-12-SP1-2017-326 - moderate: Security update for libquicktime SUSE-12-SP1-2017-551 - moderate: Security update for jasper SUSE-12-SP1-2017-542 - low: Security update for audiofile[/QUOTE] ---
**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\ **Post date:** [April 7, 2017, 10:11pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/2 "2017-04-07T22:11:38Z")
I am seeing another issue with patches scheduled for a future time. When the scheduled time arrives, the list of patches requested is installed fairly quickly, based on /var/log/zypper.log. However, after the installation of the patch, SM takes awhile before failing the package (in this case, the patches were installed at 13:12 and the package failed at 14:00). Installing the patch immediately does not involve this delay. It is only when the patch is scheduled for a future time. So it seems there is some communication failure between SM and the client when a patch is scheduled in the future. Has anyone experienced this? ---
**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\ **Post date:** [April 8, 2017, 7:19am UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/3 "2017-04-08T07:19:38Z")
On Fri, 07 Apr 2017 14:14:02 +0000, achinayoung waubonsee wrote: [color=blue] > I have the latest SM3 version installed and in testing. I attempted to > install some patches to a SLES12-SP1 system for a future time. The > action was scheduled to begin no earlier than 12:50AM CDT and, according > to the event history, it was completed at 01:00AM CDT. The patch attempt > failed. However, the event history provides absolutely no detailed > information as to why it failed. The details from the job history > follow. How can I get detailed information on why this job failed? > [color=green] > > > This action will be executed after 4/7/17 12:50:00 AM CDT This action’s > > status is: Failed. > > The client completed this action on 4/7/17 1:00 AM Client execution > > returned > > There was no job cache entry. > > (code -1)[/color][/color] That’s a bug (IMHO). I had to open an SR to get through making it work. We did a lot of things, and I’ve been working with support on three or four different SuMa SRs. Minimally, you have to be on the latest version of SuMa, the latest patches for the Minions, and there are some (otherwise undocumented, as far as I can tell) Minion configurations that have to be applied. – David Gersic Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com) If you find this post helpful, please click on the star below. ---
**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\ **Post date:** [April 11, 2017, 6:15pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/4 "2017-04-11T18:15:04Z")
[QUOTE]That’s a bug (IMHO). I had to open an SR to get through making it work. We did a lot of things, and I’ve been working with support on three or four different SuMa SRs. Minimally, you have to be on the latest version of SuMa, the latest patches for the Minions, and there are some (otherwise undocumented, as far as I can tell) Minion configurations that have to be applied.[/QUOTE] We have the latest SuMa installed and therefore the latest salt version for the minions. Guess we’ll have to open a ticket to figure out how to make this work. ---
**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\ **Post date:** [April 12, 2017, 4:41am UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/5 "2017-04-12T04:41:03Z")
On Tue, 11 Apr 2017 15:24:01 +0000, achinayoung waubonsee wrote: [color=blue][color=green] > > That’s a bug (IMHO). I had to open an SR to get through making it work. > > We did a lot of things, and I’ve been working with support on three or > > four different SuMa SRs. Minimally, you have to be on the latest > > version > > of SuMa, the latest patches for the Minions, and there are some > > (otherwise undocumented, as far as I can tell) Minion configurations > > that > > have to be applied.[/color] > > We have the latest SuMa installed and therefore the latest salt version > for the minions. Guess we’ll have to open a ticket to figure out how to > make this work.[/color] What version of SuMa? I’m on 3.0.4 here. What version of the salt and salt-minion packages are installed on the minions? (rpm -qa | grep salt) I’ve been through a bunch of things on several SRs. I’m not actually sure at this point what solved it, but I’m no longer seeing the mysterious “code -1” here. – David Gersic Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com) If you find this post helpful, please click on the star below. ---
**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\ **Post date:** [April 13, 2017, 5:48pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/6 "2017-04-13T17:48:18Z")
[QUOTE=dgersic;37442]On Tue, 11 Apr 2017 15:24:01 +0000, achinayoung waubonsee wrote: [color=blue][color=green] > > That’s a bug (IMHO). I had to open an SR to get through making it work. > > We did a lot of things, and I’ve been working with support on three or > > four different SuMa SRs. Minimally, you have to be on the latest > > version > > of SuMa, the latest patches for the Minions, and there are some > > (otherwise undocumented, as far as I can tell) Minion configurations > > that > > have to be applied.[/color] > > We have the latest SuMa installed and therefore the latest salt version > for the minions. Guess we’ll have to open a ticket to figure out how to > make this work.[/color] What version of SuMa? I’m on 3.0.4 here. What version of the salt and salt-minion packages are installed on the minions? (rpm -qa | grep salt) I’ve been through a bunch of things on several SRs. I’m not actually sure at this point what solved it, but I’m no longer seeing the mysterious “code -1” here.[/QUOTE] SLES11-SP3: salt-2015.8.12-30.1 salt-minion-2015.8.12-30.1 SLES11-SP4: salt-2015.8.12-30.1 salt-minion-2015.8.12-30.1 SLES12-SP1: salt-minion-2015.8.12-33.1.x86\_64 salt-2015.8.12-33.1.x86\_64 ---
**Author:** ![Albert](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Albert](https://forums.suse.com/u/Albert)\ **Post date:** [April 18, 2017, 9:40pm UTC](https://forums.suse.com/t/sm3-failed-patch-job-scheduled-for-future-time/29649/7 "2017-04-18T21:40:40Z")
I opened a support ticket for this issue.