Install group - Deploys wrong image
-
@tywyn have you tried to asign another image to that group or creating a new group with an assiciated image? Will that work?
-
@x23piracy : Yes, I tried to assign another image to the group. Did not help.
Just found out: When I add a second host to the group, the tasks for the right images are assigned.
When I remove the second host again, the task for the wrong image is then assigned again.So maybe it is a bug concerning the number of hosts in an installgroup?
-
@tywyn possibly thats a bug, i am not sure. Remember your not on the latest version that is maybe already fixed. @Tom-Elliott @Wayne-Workman @Sebastian-Roth
Regards X23
-
@x23piracy : Is there a documentation how to savely update to the latest version? Have you probably got a link for me?
-
@tywyn Hi, you need to update the git source, “git pull” then rerun the setup this will update to the lastest version depending on the branch you are on.
Regards X23
-
@tywyn any news?
-
Having had some trouble to upgrade to 1.5.4 but I finally managed it.
The behaviour is still the same under 1.5.4.
Having 1 host in the group -> wrong image
Adding a second host -> correct image
Removing 1 host -> wrong imageCheers
Rainer -
Moved to bug reports, will look into this soon.
-
@Tywyn I’ve tried to replicate the issue but just cannot get around. For me it works perfectly fine no matter there being only one or several hosts in the group. I am not saying there is no bug but I just couldn’t figure it out. As well looking through the could I could not see where things might go wrong with this.
I know this sounds stupid but can you give me a detailed step by step run down on what exactly you do to make this error happen. I mean the exact things you click and enter. There might be a slight chance that the error only happens if one of the steps is done exactly the way you do it.
-
@Tywyn Is this still an issue? Please let us know.
Have you run the DB maintenance stuff yet? https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands
-
@Sebastian-Roth
Cannot replicate the issue at the moment either. But I did an upgrade from 1.5.2. to 1.5.4. in the mean time.
Maybe this fixed it.Please close it. If it reoccurs, I will show up again.