Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Group Install - yumpkg.py still broken #15435

Closed
Darth8878 opened this issue Sep 2, 2014 · 6 comments
Closed

Group Install - yumpkg.py still broken #15435

Darth8878 opened this issue Sep 2, 2014 · 6 comments
Labels
Bug broken, incorrect, or confusing behavior P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-low 4th level, cosemtic problems, work around exists stale
Milestone

Comments

@Darth8878
Copy link

I received an updated yumpkg.py (for my 2014.1.7 version of Salt) from one of your esteemed members and today upgraded my Salt installation to 2014.1.10 (CentOS 6.5). All group installs fail and only succeed when I use the attached yumpkg.py and sync_modules. I thought this would have been merged into the 2014.1.10 release. Will this issue be addressed in future releases?

Hmmm, can't attach the file (at least not in this UI). Anyway, the failure is due to the missing --plugins option for the yum-related command line strings.

@basepi
Copy link
Contributor

basepi commented Sep 2, 2014

It's possible that the fix was made in 2014.7 but not backported to 2014.1. Could you perhaps test on the 2014.7 branch?

@basepi basepi added Bug labels Sep 2, 2014
@basepi basepi added this to the Approved milestone Sep 2, 2014
@Darth8878
Copy link
Author

Unfortunately I don't think so. I'm in a secure facility and we only get
what is pushed to EPEL6, which is only 2014.1.10 at this point. I might be
able to try at home this weekend by building a CentOS 6.5 VM and putting
2014.7.x on that.

Sent from my iPhone

On Sep 2, 2014, at 17:44, Colton Myers notifications@github.com wrote:

It's possible that the fix was made in 2014.7 but not backported to 2014.1.
Could you perhaps test on the 2014.7 branch?


Reply to this email directly or view it on GitHub
#15435 (comment).

@basepi
Copy link
Contributor

basepi commented Sep 2, 2014

It would be useful information. In any case, we will investigate this.

@terminalmage
Copy link
Contributor

I think I was the one that addressed this, but I don't recall the actual fix. Can you provide an issue number?

@Darth8878
Copy link
Author

I believe it was #14789.  May the Force be with you...On 09/04/2014 04:23 PM, Erik Johnson
  wrote:

  I think I was the one that addressed this, but I don't recall
    the actual fix. Can you provide an issue number?
  —
    Reply to this email directly or view
      it on GitHub.

@UtahDave UtahDave added P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps labels Jun 30, 2015
@stale
Copy link

stale bot commented Nov 21, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Nov 21, 2017
@stale stale bot closed this as completed Nov 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior P4 Priority 4 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-low 4th level, cosemtic problems, work around exists stale
Projects
None yet
Development

No branches or pull requests

4 participants