Kill off an update that will never work

[David Ross]

I made a mistake and pushed out an update that needed a newer version of
the OS than was installed. And I had not set that minimum OS value in
the package info file. The updates kept trying to install and then
failing. Even after I set the minimum OS on the munki server setup. I
finally killed the "you need to update" forever loop by removing the
contents of:
/Library/Managed Installs/Cache
/Library/Managed Installs/catalogs
/Library/Managed Installs/manifests
on the clients.

Is this a valid way to handle this situation?

Is there a better way?

Thanks
David

[Erik]

Did you not "makecatalogs" ?

[David Ross]

> Did you not "makecatalogs" ?

Yes. But it seems that once the packages are downloaded to the client
and are "pending" the server manifests are not checked until after those
updates install. (ABICT) And they kept trying to install but failing due
to the OS version being too old. Seemed to be an endless loop.

David

[Daniel Moore]

What happens if you temporarily put the update in a catalog other than your production catalog? Does the next run remove it from the cache?

> --
> You received this message because you are subscribed to the Google Groups "munki-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
> To post to this group, send email to munki-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/55361CB7.5000603%40davidrossconsultant.com.
> For more options, visit https://groups.google.com/d/optout.

[David Ross]

Don't know. Apparently Google Groups holds your first email to a group
for 24 hours and this all happened Sunday afternoon.

I removed the items from the manifests and rebuilt catalogs (not sure
that that would impact anything) and they still kept trying to install.
I even restarted the client. I then wiped our the 3 folders on the
client mentioned and then the update went away.

If I have some time later today I can try other options. I was hoping
Greg would have a "best do this" answer.

Thanks

[Gregory Neagle]

On Apr 21, 2015, at 4:54 AM, David Ross <d...@DAVIDROSSCONSULTANT.COM> wrote:

Don't know. Apparently Google Groups holds your first email to a group for 24 hours and this all happened Sunday afternoon.

I removed the items from the manifests and rebuilt catalogs (not sure
that that would impact anything) and they still kept trying to install.
I even restarted the client. I then wiped our the 3 folders on the
client mentioned and then the update went away.

If I have some time later today I can try other options. I was hoping
Greg would have a "best do this" answer.

I do. Any time you make changes to a pkginfo item, run makecatalogs.

Clients won’t pick up your changes, though until they do an update check. That happens either automatically in the background every one-to-two hours, randomized, or manually via `sudo managedsoftwareupdate` at the command-line.

You could eliminate the local client’s knowledge of any pending updates by removing /Library/Managed Installs/InstallInfo.plist.

-Greg

-- 
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/55363A62.4040308%40davidrossconsultant.com.

[David Ross]

On 4/21/15 9:08 AM, Gregory Neagle wrote:
>
>> On Apr 21, 2015, at 4:54 AM, David Ross <d...@DAVIDROSSCONSULTANT.COM

>> <mailto:d...@DAVIDROSSCONSULTANT.COM>> wrote:
>>
>> Don't know. Apparently Google Groups holds your first email to a group
>> for 24 hours and this all happened Sunday afternoon.
>>
>> I removed the items from the manifests and rebuilt catalogs (not sure
>> that that would impact anything) and they still kept trying to install.
>> I even restarted the client. I then wiped our the 3 folders on the
>> client mentioned and then the update went away.
>>
>> If I have some time later today I can try other options. I was hoping
>> Greg would have a "best do this" answer.
>
> I do. Any time you make changes to a pkginfo item, run makecatalogs.
>
> Clients won’t pick up your changes, though until they do an update
> check. That happens either automatically in the background every
> one-to-two hours, randomized, or manually via `sudo
> managedsoftwareupdate` at the command-line.
>
> You could eliminate the local client’s knowledge of any pending updates
> by removing /Library/Managed Installs/InstallInfo.plist.
>
> -Greg

I did. But this was after the client had downloaded and already tried to
run the install from the Managed Software Center and it had failed. MSC
now appeared to be in a loop. (The user kept seeing the update and kept
trying even before I got involved.) I changed the pkginfo and ran the
makecatalogs on my munki server but still the update kept appearing the
the client MSC window after after multiple clicks on the update button.

I think what you are telling me is that if I had waited until the hour
or so update check occurred then MSC would have stopped showing the update.

Or if I had forced the managedsoftwareupdate to run (via ARD or
whatever) then MSC would have stopped showing the update?

I can deal with that.

Thanks

And if this is documented I'm sorry. I've read most of the munki docs I
can find over the last few weeks. Multiple times. I must have missed it.

David

>> On 4/21/15 7:21 AM, Daniel Moore wrote:
>>> What happens if you temporarily put the update in a catalog other
>>> than your production catalog? Does the next run remove it from the
>>> cache?
>>>
>>>
>>>
>>>> On Apr 21, 2015, at 5:47 AM, David Ross

[Gregory Neagle]

> On Apr 21, 2015, at 6:18 AM, David Ross <d...@DAVIDROSSCONSULTANT.COM> wrote:
>
> On 4/21/15 9:08 AM, Gregory Neagle wrote:
>>
>>> On Apr 21, 2015, at 4:54 AM, David Ross <d...@DAVIDROSSCONSULTANT.COM
>>> <mailto:d...@DAVIDROSSCONSULTANT.COM>> wrote:
>>>
>>> Don't know. Apparently Google Groups holds your first email to a group
>>> for 24 hours and this all happened Sunday afternoon.
>>>
>>> I removed the items from the manifests and rebuilt catalogs (not sure
>>> that that would impact anything) and they still kept trying to install.
>>> I even restarted the client. I then wiped our the 3 folders on the
>>> client mentioned and then the update went away.
>>>
>>> If I have some time later today I can try other options. I was hoping
>>> Greg would have a "best do this" answer.
>>
>> I do. Any time you make changes to a pkginfo item, run makecatalogs.
>>
>> Clients won’t pick up your changes, though until they do an update
>> check. That happens either automatically in the background every
>> one-to-two hours, randomized, or manually via `sudo
>> managedsoftwareupdate` at the command-line.
>>
>> You could eliminate the local client’s knowledge of any pending updates
>> by removing /Library/Managed Installs/InstallInfo.plist.
>>
>> -Greg
>
> I did. But this was after the client had downloaded and already tried to run the install from the Managed Software Center and it had failed. MSC now appeared to be in a loop. (The user kept seeing the update and kept trying even before I got involved.) I changed the pkginfo and ran the makecatalogs on my munki server but still the update kept appearing the the client MSC window after after multiple clicks on the update button.

Sure — because clicking the Update button doesn’t trigger a check — it triggers an --installonly run. MSC doesn’t have any new info until an update check has occurred.

>
> I think what you are telling me is that if I had waited until the hour or so update check occurred then MSC would have stopped showing the update.
>
> Or if I had forced the managedsoftwareupdate to run (via ARD or whatever) then MSC would have stopped showing the update?
>
> I can deal with that.
>
> Thanks
>
> And if this is documented I'm sorry. I've read most of the munki docs I can find over the last few weeks. Multiple times. I must have missed it.

You specific scenario is nor specifically documented, no.

> --
> You received this message because you are subscribed to the Google Groups "munki-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
> To post to this group, send email to munki-...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/55364E3F.3000305%40davidrossconsultant.com.