search

anilkumar61 / munki

Automatically exported from code.google.com/p/munki
Other
0 stars 0 forks source link

Munki 2 - Process client_resources and icons before managed installs/managed updates #333

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Munki 2 currently processes/installs m_i and m_u before updating the 
client_resources and icons.

This requires an additional run (post installation) to downloaded the new 
information. 

This could also lead to client_resources never updating if the items are not 
marked unattended/forced and the user delays installation.

Original issue reported on code.google.com by eriknico...@gmail.com on 19 Jun 2014 at 12:42

GoogleCodeExporter commented 9 years ago 
I don't think this is an accurate description.

During an updatecheck run, the manifest is downloaded and processed, including 
checks/downloads for managed_installs, managed_uninstalls, managed_updates and 
optional_installs. After this is complete, icons for any items to be installed 
(and maybe removed) and all optional installs are downloaded (unless already 
cached). Finally, custom client resources are downloaded if available.

https://code.google.com/p/munki/source/browse/code/client/munkilib/updatecheck.p
y?name=Munki2#3043

The updatecheck session then ends.
If there are any unattended installs, they are attempted at this point, after 
the updatecheck session is completed.

During an install only session, the server is not contacted; Munki merely 
installs and/or removes items using the information downloaded during an 
earlier updatecheck session. Yes, if resources are updated on the server at 
this time, the Munki client won't know about them. This is no different than 
the current Munki 1 behavior and is be design.

I don't see a scenario where this could "lead to client_resources never 
updating if the items are not marked unattended/forced and the user delays 
installation.". If you have actually _seen_ unexpected behavior, I'd like to 
see a log demonstrating it.

Original comment by gregnea...@mac.com on 19 Jun 2014 at 1:24

GoogleCodeExporter commented 9 years ago 
Erik: can you clarify or should this be closed?

Original comment by gregnea...@mac.com on 23 Jun 2014 at 3:22

GoogleCodeExporter commented 9 years ago 
Keep open please. I can't retest for a bit but I will as soon as I have an 
opportunity.

Original comment by eriknico...@gmail.com on 23 Jun 2014 at 4:17

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Okay I have verified what you said. Once an auto run has been performed (with 
pending updates), the client resources will update, however If MSC is still 
open, issue 330 pops up again.

Original comment by eriknico...@gmail.com on 29 Jun 2014 at 9:51

GoogleCodeExporter commented 9 years ago 
Closing this.

Original comment by gregnea...@mac.com on 30 Jun 2014 at 3:27