ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010051ClearOSclearos-releasepublic2016-08-11 14:182016-10-24 12:38
Reporteruser2 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.2.0 Updates 
Target Version7.2.0 UpdatesFixed in Version7.2.0 Updates 
Summary0010051: Re-implement CentOS-to-ClearOS bootstrap
DescriptionThe CentOS-to-ClearOS bootstrap support was removed in 0009861. This breaks Linode and potentially other cloud/VPS providers using ClearOS. Re-add support.
Steps To Reproduce- Install CentOS 7.1511
- Install the 0009861 clearos-release build - http://koji.clearos.com/koji/buildinfo?buildID=1014 [^]
- Run "yum repolist"

Result:

# yum repolist
Loaded plugins: fastestmirror
Could not retrieve mirrorlist http://mirrorlist.clearos.com/clearos/mirrorlist/clearos-current-os-7-2.1511.el7.centos.2.10 [^] error was
14: HTTP Error 404 - Not Found


Fix:

Remove the following from /etc/yum.conf:
distroverpkg=centos-release


Result:

Happy "yum repolist" output.





TagsNo tags attached.
Attached Files

- Relationships
related to 0009861closedslords post script (and requires) causes issues with ISO build 
related to 0010381closedslords Change provided centos-release version 

-  Notes
(0003761)
slords (developer)
2016-08-18 13:25

Another option would be to make this change to the clearos-release spec file:

@@ -24,7 +24,7 @@ Provides: clearos-release(upstream) = %{upstream_rel}
 Obsoletes: redhat-release-as redhat-release-es redhat-release-ws redhat-release-de
 Obsoletes: centos-release
 Provides: clearos-release-jws = 1.1
-Provides: centos-release = %{version}-%{centos_rel}.el%{dist_release_version}.centos.2.10
+Provides: centos-release = %{version}
 Provides: centos-release(upstream) = %{upstream_rel}
 Provides: redhat-release = %{upstream_rel}
 Provides: system-release = %{upstream_rel}
(0003771)
user2
2016-08-18 14:05

If this were for a 7.3.0 Beta target, then that would be the way to go. In 7.2.0 maintenance mode, I have always used a minimalist approach (especially for a low-level package like this one). The release manager can make the call... pencil it in for Tuesday, Aug 23.

- Issue History
Date Modified Username Field Change
2016-08-11 14:18 user2 New Issue
2016-08-11 14:18 user2 Assigned To => user2
2016-08-11 14:18 user2 Status new => confirmed
2016-08-18 12:48 user2 Relationship added related to 0009861
2016-08-18 12:58 user2 Description Updated View Revisions
2016-08-18 12:58 user2 Steps to Reproduce Updated View Revisions
2016-08-18 13:25 slords Note Added: 0003761
2016-08-18 14:05 user2 Note Added: 0003771
2016-08-30 12:24 user2 Issue cloned: 0010381
2016-08-30 12:24 user2 Relationship added related to 0010381
2016-08-30 12:29 user2 Status confirmed => resolved
2016-08-30 12:29 user2 Fixed in Version => 7.2.0 Updates
2016-08-30 12:29 user2 Resolution open => fixed
2016-10-24 12:38 user2 Status resolved => closed