nstarzynski / munki

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

Munki 2 - Cancel install #362

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?

1. Begin the install of a pice of software.
2. Cancel the download.
3. Repo machine indicates it is still sending data to client.
4. Restart client.
5. Launch MSC, software is once more an option to install with no indication it 
is trying to download it again.
6. Click on the Updates tab and it appears it begins to download the software 
once more.

What is the expected output? What do you see instead?

- Cancelling a install would stop it from continuing the download, even if it 
doesn't actually install in the end.

What version of the Munki tools/InstallOSpkg tools are you using? On what
version of OS X?

- MunkiTools 2.0.0.2118
- Mac OS 10.8.5

Original issue reported on code.google.com by stuartin...@gmail.com on 7 Aug 2014 at 9:30

GoogleCodeExporter commented 8 years ago
Okay I have just realised what has been going on, this relates to Issue 361 as 
well.

As mentioned in Issue 361 the first manifest loaded, lets call it Manifest1, I 
loaded up and checked all was present.

I then logged out and changed the clientID so it would load Manifest2, logged 
back in and in seeing manifest1 still there attempted to install something, 
which appeared to refresh and display to Manifest2 content. I then tried to 
install some software from it, and then canceled it, the download from the repo 
continued even though MSC showed it was canceled.

I restarted the client, logged back in and the download had stopped and the 
repo indicated the same too.

Restarted the client, updated the clientID back to using Manifest1. Logged into 
the client, it was still showing Manifest2 content, check the update tab and it 
began to download some software again, let it finish and it appears it had 
remembered the original pice of software I tried at the start of this testing. 
Clicking back on the Software tab had also updated to display all Manifest1 
software.

I hope that makes sense, but has probably confused matters more. 

I will try and make clearer if required.

Original comment by stuartin...@gmail.com on 7 Aug 2014 at 9:47

GoogleCodeExporter commented 8 years ago
"I will try and make clearer if required."

Please.

Original comment by gregnea...@mac.com on 7 Aug 2014 at 1:10

GoogleCodeExporter commented 8 years ago
Forgetting the tangle I got myself into above; I believe what I am seeing is, 
if I start an install and then cancel it, the client carries on downloading 
from the repo, even though it will not do the install.

I wondered, if this is what is happening, if it could be stopped for bandwidth 
sake?

Original comment by stuartin...@gmail.com on 7 Aug 2014 at 2:48

GoogleCodeExporter commented 8 years ago
When you choose to install something from the Software list, that something is 
added to the local SelfServeManifest and an updatecheck is started (if one is 
not already in progress).

If you click Cancel on that same item, the item is removed from the 
SelfServeManifest. No attempt is made to stop the updatecheck, as you could 
have chosen to install multiple items and had cancelled only one.

If you really want to stop the updatecheck, switch to the updates tab and click 
the Cancel button.

Closing this since it works as designed.

Original comment by gregnea...@mac.com on 7 Aug 2014 at 3:07