Bug 1620074
Summary: | nfs client fails to install for F28 guests | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tobias Jungel <tobias.jungel> |
Component: | vagrant | Assignee: | Pavel Valena <pvalena> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | egegunes, lmohanty, madam, pvalena, strzibny, thrcka, vondruch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | vagrant-2.1.2-2.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-07 20:59:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tobias Jungel
2018-08-22 11:57:26 UTC
Hello Tobias! Thank you for your report. I do not see any issue for backporting the fix. Unfortunately, I do not have any free cycles to do it now, but feel free to submit a Pull Request[1]. Also, would you be able to test it, in case I get some spare cycles to create the PR? (See the existing one for details.) Just in case you'd be interested: my COPR repository with newer Vagrant[2]. [1] https://src.fedoraproject.org/rpms/vagrant/pull-requests [2] https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/ Hi Pavel, sure I can do a PR (but I guess it will be mid/end next week - cycles are rare ;). Where would have been the correct place to file the issue regarding the backporting as well src.fedoraproject.org? Thanks for the COPR pointer! /tobi > sure I can do a PR (but I guess it will be mid/end next week - cycles are > rare ;). Where would have been the correct place to file the issue regarding > the backporting as well src.fedoraproject.org? I'm not sure what you mean- you do not need to create any issue. Only the PR: https://docs.pagure.org/pagure/usage/pull_requests.html Note, that if you're not in the `packager` group, you have to use a bit different workflow: https://pagure.io/fedora-infrastructure/issue/6361 Feel free to ping me on irc: pvalena in #fedora-devel @Freenode. Hi Pavel, sorry my question was stupid. I somehow thought src.fedoraproject.org comes with an issue tracker like paguere does. Just made the PR: https://src.fedoraproject.org/rpms/vagrant/pull-request/11 Thanks a lot Tobi vagrant-2.1.2-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c676893073 vagrant-2.1.2-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c676893073 vagrant-2.1.2-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |