Bug 2117750

Summary:	Cobbler reposync fails on consecutive runs
Product:	[Fedora] Fedora EPEL	Reporter:	Robby Callicotte <rcallicotte>
Component:	cobbler	Assignee:	Orion Poplawski <orion>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	brejoc, jimi, kwizart, matrixfueller, ngompa13, orion, scott, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cobbler-3.2.2-13.fc35 cobbler-3-820220825124528.9edba152	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-04 22:56:22 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 Robby Callicotte 2022-08-11 19:25:05 UTC

Description of problem:
cobbler reposync fails with error /var/www/cobbler/repo_mirror/<reponame>/.origin/repodata: File exists: 'Cannot create output directory'


Version-Release number of selected component (if applicable):
cobbler-3.2.2-11.module_el8+14161+f12890f2.noarch


How reproducible:


Steps to Reproduce:
1.Create new repo
2.Run # cobbler reposync
3.Run again # cobbler reposync

Actual results:
 "/var/www/cobbler/repo_mirror//.origin/repodata: File exists: 'Cannot create output directory'"


Expected results:
Success

Additional info:

Comment 1 Robby Callicotte 2022-08-11 19:26:32 UTC

I opened a PR upstream:
https://github.com/cobbler/cobbler/pull/3227

Comment 2 Robby Callicotte 2022-08-11 19:35:57 UTC

I also opened a PR in fedora package sources:
https://src.fedoraproject.org/rpms/cobbler/pull-request/3

Comment 3 Fedora Update System 2022-08-25 13:33:06 UTC

FEDORA-2022-9f73cd938e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f73cd938e

Comment 4 Fedora Update System 2022-08-25 13:33:07 UTC

FEDORA-EPEL-MODULAR-2022-147325fe1a has been submitted as an update to Fedora Epel 8 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2022-147325fe1a

Comment 5 Fedora Update System 2022-08-26 12:44:46 UTC

FEDORA-2022-9f73cd938e has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9f73cd938e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f73cd938e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-08-26 13:11:56 UTC

FEDORA-EPEL-MODULAR-2022-147325fe1a has been pushed to the Fedora Epel 8 Modular testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2022-147325fe1a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-08-27 01:49:14 UTC

FEDORA-EPEL-MODULAR-2022-32d2c9bf0a has been submitted as an update to Fedora Epel 8 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2022-32d2c9bf0a

Comment 8 Fedora Update System 2022-08-27 21:44:12 UTC

FEDORA-EPEL-MODULAR-2022-32d2c9bf0a has been pushed to the Fedora Epel 8 Modular testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2022-32d2c9bf0a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-09-04 22:56:22 UTC

FEDORA-2022-9f73cd938e has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-09-05 00:06:27 UTC

FEDORA-EPEL-MODULAR-2022-32d2c9bf0a has been pushed to the Fedora Epel 8 Modular stable repository.
If problem still persists, please make note of it in this bug report.