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.

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

"Last synced" never gets updated/done with "Daily Sync interval" #103

Open
thomas-merz opened this issue Aug 9, 2022 · 9 comments
Open

Comments

@thomas-merz
Copy link

We have chosen/update yesterday on Aug, 8th (8.8.2022) a "daily" sync interval with start-date 8.8.2022 at 22:22:22 - but it didn't update/sync anything yesterday evening. Why?

Currently using Katello 3.18.5 and Foreman 2.3.5 and SCC plugin Version 1.8.10-1.

@thomas-merz
Copy link
Author

Why doesn't the foreman_scc_manager plugin like any time that has not "22" as seconds? (Initial sync date has been set to 22:22:22 and I wanted to change/update)

image

@m-bucher
Copy link
Member

I am not aware that we have such a sophisticated input-field in SCC-Manager 1.8.10 Could this be your browser messing around with the value?

Apart from that, please have a look at Monitor->Recurring Logics and ->Tasks for further information about the Update SUSE repositories-Action/Task, which is created by this setting.

@thomas-merz
Copy link
Author

Monitor->Recurring Logics shows one with these details:

image

Next occurrence should be today, not tomorrow!? So I "faked" it by changing start date to yesterday, so it should start later at 15:45:00:

image

And some minutes later… 🎉

image

But look at this!? This was my manual sync at 15:30 😞

image

Clicking on "Task Count (2)" above shows this:

image

And clicking on the "successfull" task:
"No running steps"
"No errors"
"Raw output: {}"

🤷‍♂️

So it looks like it did run, but did nothing while running!?

@m-bucher
Copy link
Member

OK, now I get it 😅

The automatic re-sync Tasks are only for updating the Access-Tokens used by the Katello-Repos.
This is necessary, because from time to time these Tokens expire and need to be re-synced.

The automatic re-sync does not change the list of available SCC-Products/-Repositories.

I know this is kinda misleading, but we wanted to avoid that SCC-Products disappear from the list without a manual re-sync.

@thomas-merz
Copy link
Author

Hm, so everything works as designed?

I only see these Update URL-token for repository messages for my manual sync (15:30) - not for the planned/schedules sync (15:45).
I expected that this should happen with every SCC-product-sync… 🤔

I really "fear" that SUSE may do something weird every six months so that URL-tokens will change and I have to manually update list of SCC-products which triggers the Update URL-token for repository…?!

@m-bucher
Copy link
Member

From what I remember the tokens do not switch every time they are requested.
As long as the existing ones are still valid they are not changed IIRC.

We only had problems with systems that were not re-synced (re-requested tokens) for long periods of time (n months).

@thomas-merz
Copy link
Author

This is the question:
Is now everything fine again with these settings and the patched scc-plugin?
Or will I get into some trouble in oct/nov when SUSE may change some URL-tokens again?

@m-bucher
Copy link
Member

Since the Recurring Logic is installed and functional (-> creating sync tasks), you should be fine.

@thomas-merz
Copy link
Author

thomas-merz commented Sep 5, 2022

This looks fine now for me 👍

grafik

But this is really confusing:

grafik

324 products

After hitting the "sync" button/dropdown:

grafik

326 products

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants