Hi all,
I found several discussion regarding the same topics, some links are not working anymore and some discussion without any conclusion. I will try to re-propose the topics.
My configuration iTOP 3, Toolikit 3, MariaDB 10.3.31
1)First topic not really important but nice to understand.
Is there a way to remove all the useless messages in the "Check Database" like "varchar(255) and VARCHAR(255)". A lot of warning that make the check a bit unreadble.
2) What is important for me to understand is the data model consistency. I receive a lot of inconsistency (see below). I read that could be the custom extensions that break the lifecycle. Is not really clear for me and I would like to understand better, because I have several custom extension, some of them customizing the class in the list below, but some other classes I never touched and present the inconsistency as well.
Thanks in advance for any suggestion and explanation.
1) We put a lot of work to remove them (especially N°2490 in 2.7.0) but there are some still present. Those last fixes are not top priority in current roadmap.
2) I cannot reproduce. Please give some hints so that we can see the cause of this behavior ? The closest to the iTop Community version the better...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the exact same issue with a brand new iTop community 3.0.2-1 and toolkit v3 (itop-toolkit-community-3.0.0.zip from GitHub).
I have no custom extension nor any itophub extension installed.
Data is just the demo instance stuff added by the setup.
Looking at the error messages a bit further, there is a hint of what is gooing wrong: for each class with a lifecycle, there is a error message for each existing status value, and there is an error about a state "" which is not allowed. A state with no name...
Looking at the code I see that at some point it calls MetaModel::CheckDefinitions(). And at line 5020, this method does a " $aStates = array_keys(self::EnumStates($sClass)); ". I suspect that, for an unknown reason, the result stored in $aStates is empty.
With this assumption, all the error messages make sense: comparing an empty list on known state with a filled-up list of enum values for the status attribute, throw errors for all existing enums and for a no-name state.
To be confirmed and troubleshooted ?
Last edit: Fabrice Vincent 2022-10-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BTW, the last 2 errors, about Unknown attribute code 'application' in the list of reconciliation keys of classes RemoteApplicationConnection and RemoteiTopConnection seems to be real actual bugs in the 3.0 datamodel : there is no 'application' fields defined in these to classes, and neither in their parent class Typology.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Fabrice !
Many thanks for the analysis !
The problem was reproduced thanks to the info given in another thread ([8203a6f142]) and a bug was created in Combodo DB : N°5218. I've reported the info in the bug.
Hi, I'm new with the iTop platform and application, I was also trying to add a new field in an existing class, but I ran into the same problem, I also have iTop 3.0, Toolkitt 3.0, but I keep getting the same messages
The 'status' attribute (object status) has an allowed value (xxxxx) which is not a known status., etc
Is there any update on this since last time, or is there any other solution to add a new field?
Thank you very much.
Best regards.
Last edit: Carlos Anguiano 2023-01-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your answer, what I meant is to know if there is another way to
add a new field to an existing class or I will have to wait for the bug to
be fixed.
Thanks for your answer, what I meant is to know if there is another way to
add a new field to an existing class or I will have to wait for the bug to
be fixed.
Regards.
On Thu, Feb 9, 2023 at 11:28 AM Pierre Goiffon
pgoiffon@users.sourceforge.net wrote:
Hello,
The bug wasn't planned in next releases.
Not sure to understand what you mean by "is there any other solution to
add a new field" ?
Toolkit Data model Inconsistency (iTOP 3 Toolikit 3)
Understood Marco, thanks... however, I am still having problems in adding 2 fields to the Incident class, I could be doing something wrong or I am missing something, I have followed the instructions (https://www.itophub.io/wiki/page?id=3_0_0:customization:add-attribute-sample) for this process, but I can't get it to work..... should i move this topic to a new discussion? at first i thought it was because of the bug already mentioned..... is there any advice you could give me .... I am new with iTop so any guidance on this issue would be greatly appreciated.....
Regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Carlos,
I would say yes, move the topic out from this one for the bug, you will get
more help for sure. (Once you open a new thread you can reply here the
link, so I can follow and help you).
Regarding the help, I think you should provide more information. The link
you posted is the correct one, that I can say, but if you don't post what
you did, or the error you get compiling is hard for me to understand.
Understood Marco, thanks... however, I am still having problems in adding
2 fields to the Incident class, I could be doing something wrong or I am
missing something, I have followed the instructions ( https://www.itophub.io/wiki/page?id=3_0_0:customization:add-attribute-sample)
for this process, but I can't get it to work..... should i move this topic
to a new discussion? at first i thought it was because of the bug already
mentioned..... is there any advice you could give me .... I am new with
iTop so any guidance on this issue would be greatly appreciated.....
Hi all,
I found several discussion regarding the same topics, some links are not working anymore and some discussion without any conclusion. I will try to re-propose the topics.
My configuration iTOP 3, Toolikit 3, MariaDB 10.3.31
1)First topic not really important but nice to understand.
Is there a way to remove all the useless messages in the "Check Database" like "varchar(255) and VARCHAR(255)". A lot of warning that make the check a bit unreadble.
2) What is important for me to understand is the data model consistency. I receive a lot of inconsistency (see below). I read that could be the custom extensions that break the lifecycle. Is not really clear for me and I would like to understand better, because I have several custom extension, some of them customizing the class in the list below, but some other classes I never touched and present the inconsistency as well.
Thanks in advance for any suggestion and explanation.
BR
Marco
Hello,
1) We put a lot of work to remove them (especially N°2490 in 2.7.0) but there are some still present. Those last fixes are not top priority in current roadmap.
2) I cannot reproduce. Please give some hints so that we can see the cause of this behavior ? The closest to the iTop Community version the better...
Bonjour Pierre,
I have the exact same issue with a brand new iTop community 3.0.2-1 and toolkit v3 (itop-toolkit-community-3.0.0.zip from GitHub).
I have no custom extension nor any itophub extension installed.
Data is just the demo instance stuff added by the setup.
Details of my setup:
Error messages:
Hope this could help reproduce and solve the issue.
Last edit: Fabrice Vincent 2022-10-18
Looking at the error messages a bit further, there is a hint of what is gooing wrong: for each class with a lifecycle, there is a error message for each existing status value, and there is an error about a state "" which is not allowed. A state with no name...
Looking at the code I see that at some point it calls MetaModel::CheckDefinitions(). And at line 5020, this method does a " $aStates = array_keys(self::EnumStates($sClass)); ". I suspect that, for an unknown reason, the result stored in $aStates is empty.
With this assumption, all the error messages make sense: comparing an empty list on known state with a filled-up list of enum values for the status attribute, throw errors for all existing enums and for a no-name state.
To be confirmed and troubleshooted ?
Last edit: Fabrice Vincent 2022-10-18
BTW, the last 2 errors, about Unknown attribute code 'application' in the list of reconciliation keys of classes RemoteApplicationConnection and RemoteiTopConnection seems to be real actual bugs in the 3.0 datamodel : there is no 'application' fields defined in these to classes, and neither in their parent class Typology.
Hello Fabrice !
Many thanks for the analysis !
The problem was reproduced thanks to the info given in another thread ([8203a6f142]) and a bug was created in Combodo DB : N°5218. I've reported the info in the bug.
Related
Discussion: 8203a6f142
Hi, I'm new with the iTop platform and application, I was also trying to add a new field in an existing class, but I ran into the same problem, I also have iTop 3.0, Toolkitt 3.0, but I keep getting the same messages
The 'status' attribute (object status) has an allowed value (xxxxx) which is not a known status., etc
Is there any update on this since last time, or is there any other solution to add a new field?
Thank you very much.
Best regards.
Last edit: Carlos Anguiano 2023-01-25
Hello,
The bug wasn't planned in next releases.
Not sure to understand what you mean by "is there any other solution to add a new field" ?
Hi,
Thanks for your answer, what I meant is to know if there is another way to
add a new field to an existing class or I will have to wait for the bug to
be fixed.
Regards.
On Thu, Feb 9, 2023 at 11:28 AM Pierre Goiffon pgoiffon@users.sourceforge.net wrote:
Hi Carlos,
this bug has nothing to do with the class customization. So the answer to
you question is, yes of course you can add.
BR
Marco
Il sab 11 feb 2023, 21:44 Carlos Anguiano cangui1@users.sourceforge.net
ha scritto:
Understood Marco, thanks... however, I am still having problems in adding 2 fields to the Incident class, I could be doing something wrong or I am missing something, I have followed the instructions (https://www.itophub.io/wiki/page?id=3_0_0:customization:add-attribute-sample) for this process, but I can't get it to work..... should i move this topic to a new discussion? at first i thought it was because of the bug already mentioned..... is there any advice you could give me .... I am new with iTop so any guidance on this issue would be greatly appreciated.....
Regards.
Hi Carlos,
I would say yes, move the topic out from this one for the bug, you will get
more help for sure. (Once you open a new thread you can reply here the
link, so I can follow and help you).
Regarding the help, I think you should provide more information. The link
you posted is the correct one, that I can say, but if you don't post what
you did, or the error you get compiling is hard for me to understand.
BR
Marco
Il mer 15 feb 2023, 16:13 Carlos Anguiano cangui1@users.sourceforge.net
ha scritto:
Great Marco , I will move it out of this .... and I will share with you the link..... Thank you very much.
Best regards.
Hi Marco, this is the link that i just posted https://sourceforge.net/p/itop/discussion/customizing-itop/thread/9ae1cbe1b3/#ed16 , hope you can help me..
Thank you,
BR.
Hi Marco, I hope you are well....
Did you get a chance to see the link I shared with you a few days ago?
BR.