Munki2 MSC Updates cache not refreshed after failed update.

[GoogleCodeExporter]

What steps will reproduce the problem?

1.  Add a pkg that will likely fail during install to manifest. 
2. Try to update/install the package through Managed Software Center
3. It will fail (as it should)
4. fix the pkginfo/rebuild catalog. 
5. try to update the package again. (it will fail, even though there's a new 
pkginfo on the server).
6. remove the pkg from the update list manually 
7. add the pkg to install list and run MSU again. It will work now. 

What is the expected output? What do you see instead?
I imported a new app to munki, then went to install it on a client machine. I 
forgot to add AdobeAir as a required item to the pkginfo and so the app 
wouldn't install properly. I made the necessary changes to the pkginfo, but the 
client did not get the new pkginfo untill I removed the app from the update 
list and added it again.  

What version of the Munki tools/InstallOSpkg tools are you using? On what
version of OS X?
Munki2 April 10 Build. OS X 10.9.2

Please provide any additional information below.

zalmoxes in IRC.

Not sure if this is a bug or just MSU caching the update list for a specific 
time, but would it be possible for MSU to verify the pkginfo has not been 
changed/catalog rebuilt since the last unsuccessful install? 

Original issue reported on code.google.com by vranc...@gmail.com on 15 Apr 2014 at 9:37

[GoogleCodeExporter]

This behavior is really essentially no different from the current behavior; 
only the timing has changed.

MSU/MSC can't know about server changes until an entire update check run 
happens. (This is the equivalent of `/usr/local/munki/managedsoftwareupdate`).

This check can take some time. With Munki, this happens at launch of MSU.app if 
the last check was more than a minute ago. This lead to several complaints that 
users had to wait "too long" in order to use MSU.app to select and install 
optional installs when they chose to launch it manually to browse for and 
install items.

With MSC.app, the time before an updatecheck run is forced has increased. I 
reserve the right to change the timing, so I'm not going to say what the 
current timing is, but you can easily see it if you browse the MSC.app code.

This is always going to be a trade-off. We can annoy the user by always doing a 
full updatecheck at each launch, or we can annoy the admin by doing an 
updatecheck less often.

There is a mechanism by which the local admin can tune this timing, and it's 
not new to Munki 2:

Munki 2:
https://code.google.com/p/munki/source/browse/code/Managed%20Software%20Center/M
anaged%20Software%20Center/munki.py?name=Munki2#74

Equivalent in munki (1):
https://code.google.com/p/munki/source/browse/code/Managed%20Software%20Update/M
SUAppDelegate.py#121

Original comment by gregnea...@mac.com on 15 Apr 2014 at 10:05

[GoogleCodeExporter]

Closing due to lack of further discussion/feedback.

Original comment by gregnea...@mac.com on 6 Jun 2014 at 8:41

• Changed state: WontFix