Jira (PUP-146) Install multiple packages with one call to the underlying package manager

7 views
Skip to first unread message

Chris Nossing (JIRA)

unread,
Jun 12, 2015, 4:58:01 AM6/12/15
to puppe...@googlegroups.com
Chris Nossing commented on Epic PUP-146
 
Re: Install multiple packages with one call to the underlying package manager

It's been very quiet on this subject for a while now. Just wanted to say there are still people out there who would really appreciate it if this feature would work! Even a way to specify your own batches would be awesome... I wouldn't mind figuring out which packages can go into a batch myself if Puppet provided a way to install these batches.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Atlassian logo

Benjamin Fischer (JIRA)

unread,
Aug 4, 2015, 4:04:12 AM8/4/15
to puppe...@googlegroups.com

Just for a short node: This feature would allow downgrade of packages with dependencies in yum.
When downgrading packages with dependencies, you need to downgrade all packages within a single yum call, otherwise downgrading will fail.

This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Atlassian logo

Roy Williams (JIRA)

unread,
Dec 1, 2015, 9:55:13 AM12/1/15
to puppe...@googlegroups.com
Roy Williams commented on Epic PUP-146

I am annoyed we haven't seen any progress on this and instead we are still forced to use Exec resource hacks to work around the issue hoping later there will be a code re-factor. It seems there have been multiple tickets open on JIRA already on this very issue including "PUP-1061" which seems to be a year old. There was a patch submitted as well some time ago for dealing with this issue with a "combine" option for the package class.

From: https://github.com/phantez/puppet/commit/51ff88c950c172e6060ae63c1c71968e7898b462

I suspect this is no longer applicable given no progress has been made other than a community patch that got re-based at least once since this issue was brought up 4 years. Is there no one looking at this problem?

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Kylo Ginsberg (JIRA)

unread,
Jan 11, 2016, 8:24:04 PM1/11/16
to puppe...@googlegroups.com
Kylo Ginsberg commented on Epic PUP-146

Yes, sadly, there's been no progress on this, and it's not currently planned. So many things to do and somehow this hasn't made it to the top of anyone's list.

Roy Williams I wasn't aware of that patch but that looks like a solid starting point. From a quick look, I do have some questions about it, but probably awkward to discuss here. Do any of the watchers here want to kick off a PR or a thread on puppet-dev? It'd be easier to discuss in one of those venues.

Thanks!!

Bill Niestempski (JIRA)

unread,
Jan 21, 2016, 6:50:04 PM1/21/16
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
May 16, 2017, 1:49:03 AM5/16/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 4.y
Fix Version/s: PUP 5.y
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Josh Cooper (JIRA)

unread,
May 16, 2017, 5:06:07 PM5/16/17
to puppe...@googlegroups.com

Moses Mendoza (JIRA)

unread,
May 18, 2017, 1:45:08 PM5/18/17
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
Jul 22, 2017, 1:52:05 AM7/22/17
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
Sep 27, 2018, 1:47:07 AM9/27/18
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Team/s: Platform Core Coremunity
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Michael Smith (JIRA)

unread,
Sep 27, 2018, 11:24:06 AM9/27/18
to puppe...@googlegroups.com

David Alexander (JIRA)

unread,
Mar 18, 2019, 6:55:03 PM3/18/19
to puppe...@googlegroups.com

Macquarie Group in Australia have requested this functionality. Is it still active? It's this sort of thing that will creep up on us when a competitor brings out better functionality (looking at you Red Hat) as it's not particularly sexy, it's just a fundamental requirement.

Josh Cooper (JIRA)

unread,
Apr 19, 2019, 12:22:04 PM4/19/19
to puppe...@googlegroups.com
Josh Cooper assigned an issue to Unassigned
 
Change By: Josh Cooper
Assignee: Eric Sorenson

Josh Cooper (JIRA)

unread,
Apr 19, 2019, 12:23:09 PM4/19/19
to puppe...@googlegroups.com

Aaron Boudreaux (Jira)

unread,
Jan 25, 2021, 5:17:05 PM1/25/21
to puppe...@googlegroups.com
Aaron Boudreaux commented on Epic PUP-146
 
Re: Install multiple packages with one call to the underlying package manager

I just assumed that this is how puppet already worked until digging into why installing many packages with puppet was so much slower than ansible; I then discovered puppet creates a separate yum transaction for every single package even when I have them in the same list for the package resource. I am surprised to see this is still an issue more than 7 years later after being reported. Please add this functionality. The better performance of running masterless puppet with puppet apply over running ansible local is one of the primary reasons we were attempting to move more of our configuration to puppet. However, since a large portion of our configuration involves installing packages, not being able to do that quickly is a problem for us.

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Don (Jira)

unread,
Feb 2, 2021, 11:50:02 AM2/2/21
to puppe...@googlegroups.com
Don commented on Epic PUP-146

Besides of the performance issue I'm phasing the issue that I'm not able to downgrade packages with dependencies e.g. running something equivalent to:

 

# yum downgrade java-1.8.0-openjdk-headless-1.8.0.275.b01-0.el7_9.x86_64 java-1.8.0-openjdk-devel-1.8.0.275.b01-0.el7_9.x86_64 java-1.8.0-openjdk-1.8.0.275.b01-0.el7_9.x86_64

running:

 

# yum downgrade java-1.8.0-openjdk-headless-1.8.0.275.b01-0.el7_9.x86_64 
# yum downgrade java-1.8.0-openjdk-devel-1.8.0.275.b01-0.el7_9.x86_64 
# yum downgrade java-1.8.0-openjdk-1.8.0.275.b01-0.el7_9.x86_64

ends up in errors like:

 

Error: Could not update: Execution of '/bin/yum -d 0 -e 0 -y downgrade java-1.8.0-openjdk-1.8.0.275.b01-0.el7_9.x86_64' returned 1: Error: Package: 1:java-1.8.0-openjdk-devel-1.8.0.282.b08-1.el7_9.x86_64 (@rhel-7-server-rpms)
           Requires: java-1.8.0-openjdk(x86-64) = 1:1.8.0.282.b08-1.el7_9                                                                                                                                                          
           Removing: 1:java-1.8.0-openjdk-1.8.0.282.b08-1.el7_9.x86_64 (@rhel-7-server-rpms)                                                                                                                                                             java-1.8.0-openjdk(x86-64) = 1:1.8.0.282.b08-1.el7_9                                                                  
           Downgraded By: 1:java-1.8.0-openjdk-1.8.0.275.b01-0.el7_9.x86_64 (rhel-7-server-rpms)                                                                                                                                         
               java-1.8.0-openjdk(x86-64) = 1:1.8.0.275.b01-0.el7_9                                                                                                                                                            
Error: Package: 1:java-1.8.0-openjdk-1.8.0.275.b01-0.el7_9.x86_64 (rhel-7-server-rpms)                                                                                                                                     
           Requires: java-1.8.0-openjdk-headless(x86-64) = 1:1.8.0.275.b01-0.el7_9                                                                                                                                                                   Installed: 1:java-1.8.0-openjdk-headless-1.8.0.282.b08-1.el7_9.x86_64 (@rhel-7-server-rpms)                                                                                                                                                   java-1.8.0-openjdk-headless(x86-64) = 1:1.8.0.282.b08-1.el7_9                                                    
           Available: 1:java-1.8.0-openjdk-headless-1.8.0.275.b01-0.el7_9.x86_64 (rhel-7-server-rpms)                                                                                                        
               java-1.8.0-openjdk-headless(x86-64) = 1:1.8.0.275.b01-0.el7_9                 
 You could try using --skip-broken to work around the problem                                                                       
 You could try running: rpm -Va --nofiles --nodigest

Workarounding this with an exec feels not correct.

 

 

 

Martin Petersen (Jira)

unread,
Oct 6, 2022, 5:30:03 AM10/6/22
to puppe...@googlegroups.com

Are there any news about this issue? It is nearly 10 years old and still a very serious performance problem. I would be very glad to see a solution for it.

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages