-
Notifications
You must be signed in to change notification settings - Fork 26
Updating CCV terminates with error: #35
Comments
Quoting from IRC:
Line 223 reads: ids = Array.new(ccv['component_ids']) and that will error out if can you add the following lines before line 223 and show us the output? puts ccv['component_ids']
puts ccv['components'] |
Changed the code to:
Output result:
|
Any idea how to find out what's causing the problem? |
Well, I would have expected the |
Can you try: - ids = Array.new(ccv['component_ids'])
+ ids = Array.new(ccv['components'].flat_map{|i| i['id']}) This should get the IDs from components, not from component_ids. |
Might be related to http://projects.theforeman.org/issues/18820? |
@evgeni this patch made it work but not quite. It's not throwing an error any more but it's not updating nor promoting anything.
publish command works as expected tho. |
Good that the patch helped. |
I've seen this issue a few days ago, so I've updated my names to match my labels. Makes no difference. |
Can you post |
No difference. Gives me the same output. |
Do you have the latest version? |
Sorry, I thought you were asking about promote --verbose.
At this point I would expect it to create a new version for ALL_CentOS6_Updates and ALL_CentOS7_Updates but it doesn't.
|
So it thinks that all the components are already at the latest version, and thus no update is required. Can you post the output of |
When I manually create a new version of CCV, promote action works as expected. It seems that only --update action is not playing ball. I will have to demote and remove newly (manually) created CCV to post the logs you requested. |
I think I know where you issue is coming from. Will post a test-patch later. |
The list you requested:
|
Did you have any luck with the patch? |
So I was thinking of something like this:
However, your output above suggests that |
ok, I've added a few more versions for each CV. The output now:
After the patch, update actions hasn't changed.
Maybe I don't understand how it's supposed to work. I believe - based on the docs I've read - that "update" should publish a new version of CCV matching the latest versions of CV and promote should push this new version to DEV or PROD env. Am I wrong here? |
So the idea is that you have CVs for your content parts, serve CCVs to your clients, and cvmanager keeps the CVs in the CCVs uptodate. So the workflow would be:
So taking But in your paste it seems that |
My setup matches your description. All hosts use CCV - either ALL_CentOS6_Updates or ALL_CentOS7_Updates. I based my setup on "Fully automated CCV for automated patching" example So what I've done is:
The client has no new updates available. What am I missing? |
I encountered this issue recently while trying to set up the tool. Solution ( for me) was to change the component versions of my composite content view from "latest" to a version number. the publish, update,promote workflow worked perfectly after that. |
hi @sandersr, i have the same Problem with the CCVs update. I have all my repos in CCV_ALL_6 and CCV_ALL_7. The CV are already up to date, but the CCVs, what my clients will see don't have the latest version. Do you have allready a solution for this Problem? Checking cv_mariadb_6 Checking cv_icinga2_6 |
my config file:
The text was updated successfully, but these errors were encountered: