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.

Sign up for GitHub

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

Jump to bottom

pkgrepo.managed fails on Fedora 23 #31240

Closed
toanju opened this issue Feb 16, 2016 · 7 comments
Closed

pkgrepo.managed fails on Fedora 23 #31240

toanju opened this issue Feb 16, 2016 · 7 comments
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P2 Priority 2 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around stale
Milestone
Approved

Comments

@toanju
Copy link
Contributor

toanju commented Feb 16, 2016

adding a new repository using pkgrepo.managed on a salt minion (2015.5.9-2.fc23) fails with this error:

        Comment: Failed to configure repo 'toanju-rofl-common': No suitable yum config file found in: ('/etc/yum/yum.conf', '/etc/yum.conf')

example repo:

toanju-rofl-common:
  pkgrepo.managed:
    - humanname: Copr repo for rofl-common owned by toanju
    - baseurl: https://copr-be.cloud.fedoraproject.org/results/toanju/rofl-common/fedora-$releasever-$basearch/
    - gpgcheck: 0
    - enabled: 1

a workaround is using dnf install yum.

maybe setting basedir would work too, but i have not tested this, yet.
@jfindlay jfindlay added the info-needed waiting for more info label Feb 16, 2016
@jfindlay jfindlay added this to the Blocked milestone Feb 16, 2016
@jfindlay
Copy link
Contributor

@toanju, thanks for reporting. The dnf work has been done mostly on 2015.8 and develop/2016.3. Much of this has been backported to the 2015.5 branch, but it is possible that something hasn't been backported, or that pkgrepo will fail on both 2015.5 and 2015.8. Is it possible for you to reproduce this on 2015.8.5?

@toanju
Copy link
Contributor Author

toanju commented Feb 28, 2016

@jfindlay, sorry for the delay. Neither 2015.8.5 nore 2015.8.7 worked here. Here is the output of the latter:

[INFO    ] Executing state pkgrepo.managed for toanju-rofl-common
[WARNING ] /usr/lib/python2.7/site-packages/salt/states/pkgrepo.py:267: DeprecationWarning: The `enabled` argument has been deprecated in favor of `disabled`.

[ERROR   ] Failed to configure repo 'toanju-rofl-common': No suitable yum config file found in: ('/etc/yum/yum.conf', '/etc/yum.conf')
[INFO    ] Completed state [toanju-rofl-common] at time 22:37:12.458013
local:
----------
          ID: toanju-rofl-common
    Function: pkgrepo.managed
      Result: False
     Comment: Failed to configure repo 'toanju-rofl-common': No suitable yum config file found in: ('/etc/yum/yum.conf', '/etc/yum.conf')
     Started: 22:37:12.451879
    Duration: 6.134 ms
     Changes:   

Summary for local
------------
Succeeded: 0
Failed:    1
------------
Total states run:     1
[root@localhost ~]# salt-call --version
salt-call 2015.8.7 (Beryllium)

@jfindlay jfindlay modified the milestones: Approved, Blocked Feb 29, 2016
@jfindlay jfindlay added Execution-Module Bug broken, incorrect, or confusing behavior severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around P2 Priority 2 Platform Relates to OS, containers, platform-based utilities like FS, system based apps and removed info-needed waiting for more info labels Feb 29, 2016
@jfindlay
Copy link
Contributor

@toanju, thanks for verifying.

@eliezerlp
Copy link

What are the next steps for this item?

@luitzifa
Copy link
Contributor

luitzifa commented Oct 14, 2016 •
edited
Loading

Got the same problem on Fedora 24, but only with salt-ssh (2016.3.3)

EDIT: not salt-ssh is the problem... it's just broken
EDIT2: still broken in 2016.11.0rc1

luitzifa added a commit to luitzifa/salt that referenced this issue Oct 22, 2016
@luitzifa
fixes pkgrepo for fedora>22 saltstack#31240
40ecc46 
This makes modules.yumpkg complete independend from yum. yum is not
installed in fedora>22, so this will actually fix pkgrepo in fedora.
@luitzifa luitzifa mentioned this issue Oct 22, 2016
Merged
gitebra pushed a commit to gitebra/salt that referenced this issue Oct 25, 2016
@jojohans
Merge remote-tracking branch 'upstream/develop' into develop
164bb2a 
* upstream/develop: (31 commits)
  fixes pkgrepo for fedora>22 saltstack#31240
  Pylint fix
  Allow the minion test daemons a couple of tries to connect to the master (saltstack#37150)
  Add note about salt-bootstrap known issue for 2016.3.4 (saltstack#37152)
  Don't fail if host_to_ips returns None.
  pkgbuild.repo: fix GPG signing with `use_passphrase=False`
  Fix example signing policy in salt.states.x509 docs
  fix digital ocean image name in profile (saltstack#37126)
  add 2016.3.4 release notes (saltstack#37125)
  log.setup: only assign user if defined
  tests.integration: pass opts as a dict
  Skip weird_install test on Mac OS X
  Fix test_issue_6833_pip_upgrade_pip test on OSX
  For IPCClient, remove entry from instance map on close
  Fix race condition when returning events from commands
  pkgbuild.repo: add `timeout` parameter for waiting passphrase prompt
  Remove unnecessary sleep from unit.utils.process_test.TestProcessManager.test_restarting
  Add warning about GitPython 2.0.9 incompatibility with Python 2.6 (saltstack#37099)
  Use NotifyAccess=all in all unit files
  Lintfix: E8303 too many blank lines
  ...
rallytime pushed a commit to rallytime/salt that referenced this issue Oct 25, 2016
@luitzifa
fixes pkgrepo for fedora>22 saltstack#31240
a7dbb5b 
This makes modules.yumpkg complete independend from yum. yum is not
installed in fedora>22, so this will actually fix pkgrepo in fedora.
@stale
Copy link

stale bot commented Jul 14, 2018

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 Jul 14, 2018
@toanju
Copy link
Contributor Author

toanju commented Jul 17, 2018

works fine in the meanwhile

@toanju toanju closed this as completed Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug broken, incorrect, or confusing behavior Execution-Module P2 Priority 2 Platform Relates to OS, containers, platform-based utilities like FS, system based apps severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around stale
Projects
None yet
Milestone
Approved
Development

No branches or pull requests
4 participants
@eliezerlp @jfindlay @toanju @luitzifa