Bug #17422
closed
Technique editor error
Description
I upgraded rudder 4.3.10 -> 5.0.17 -> 6.0.5 -> 6.1.0 beta 3 to get support for last os.
When I reached 6.0.5, I encountered a reporting bug and so I switched to 6.1.0.beta3. But now, I have a problem with technique, I can't reach the page and I get:
_An Error occured! Error while fetching methods
Details:
Could not get generic methods metadata <- Inconsistency: An error occured while updating generic methods library,
error out:
std out:_
In logs, I get:
2020-05-15T11:58:17+0200 WARNING Failed to execute shell command from Rudder: error=2, No such file or directory[2020-05-15 11:58:17+0200] ERROR com.normation.rudder.rest.RestUtils - "Could not get generic m ethods metadata <- Inconsistency: An error occured while updating generic methods library,\n error out: \n std out: "
Techniques still work.
What can I do?
Original message:
Bonjour,
Afin de prendre en compte les derniers OS, j'ai effectué un upgrade de rudder.
4.3.10 -> 5.0.17 -> 6.0.5 -> 6.1.0 beta 3
Quand je suis arrivé en version 6.0.5, j'ai eu le bug de reporting qui m'a incité a passé en 6.1.0 beta 3.
EN 6.1.0 beta 3, j'ai un problème pour accéder à la partie techniques. Cette page n'est plus accessible avec le message :
_An Error occured! Error while fetching methods
Details:
Could not get generic methods metadata <- Inconsistency: An error occured while updating generic methods library,
error out:
std out:_
Si je vais dans les logs, j'ai ceci :
2020-05-15T11:58:17+0200 WARNING Failed to execute shell command from Rudder: error=2, No such file or directory[2020-05-15 11:58:17+0200] ERROR com.normation.rudder.rest.RestUtils - "Could not get generic m ethods metadata <- Inconsistency: An error occured while updating generic methods library,\n error out: \n std out: "
Mes tehcniques précédemment créées fonctionnent toujours...
Une idée??
Updated by François ARMAND over 4 years ago
- Subject changed from Technique editor erreur to Technique editor error
- Description updated (diff)
(I'm switching to English to let others people be able to undertand tickets).
Hello,
Rudder 6.1.0.beta is not ready for prod but only for testing / validation. Once it will be, we will tell so on user mailing list (and likelly switch to "RC"). Of course, we are glad to have people testing it! It allows to find more problems.
In your case, I see two possibilities:
- switch back to 6.0. We didn't tested it, but AFAIK it should work. What is the reporting bug you were talking about?
- upgrade to last 6.1.0-beta nightly. It is still risky, since we are heavely working on it, and each day a lots of problem get corrected. But sometime, some new are introduced, too.
I think the less risky for now is to switch back to 6.0. We will release a new version at the start of next week (likely monday) if it helps.
Updated by Patrice ROUX over 4 years ago
HI,
THank's for your return.
I think I will wait for the upgrade because my environment is quite small.
In 6.0.5, I had a problem because when I made a "rudder agent reporting" all or almost all my clients were in error for this action. The upgrade has resolved this problem.
Regards
Updated by François ARMAND over 4 years ago
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 51
Hello,
Did you upgraded to newer versions? Did it solved your problems?
Updated by Alexis Mousset almost 3 years ago
- Status changed from New to Rejected
- Priority changed from 51 to 43
closing as it had no answer, feel free to open another issue.