I know I’ve been out of this for a little bit. I check in here or there, but just been extremely busy.

I don’t want to stop contributing, I just am taking time for myself after my workly duties.

I have to give a big gratitude and thanks for everyone here trying to help out whether by code, by helping the rest of the community, or documentation.

@Sebastian-Roth I know you’re busy but you’ve kept the project rolling even with the minimal availability you have. Thank you.
@george1421 I’m sure you’re busy, but I still see you posting and helping where possible and amenible. Thank you.
@Wayne-Workman I know you’re helping where you can as well. (Of course I can’t exactly post everybody because I’ve been busy and honestly not keeping up with the forums as much as I probably should.)

@everyone Thank you. Thank you for still believing in this project. We’re doing the best with what we have. Please understand in we’re lacking, it’s most likely unintentional. I know I’m just busy.

https://news.fogproject.org/fog-1-3-5-and-client-0-11-11-officially-released/

https://news.fogproject.org/fog-1-5-0-rc-11/

TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

The quickest fix is to simply rerun the fog installer which should correct the problem.

As a note, it seems this problem is specific only when the mysql account is the 'root' user AND the password is blank.

The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T then sudo -i (in most cases).

From there, open mysql with mysql -u root

NOTE: MySQL MUST be run with ROOT.

Run:

ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY ''; AND
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';

It’s okay if one of them fails. This is going to fix Most people’s issues.

I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

To prevent this problem from happening in the future you could run:

apt-get -y remove unattended-upgrades (AS Root again).

FOG is still actively being developed. It’s not necessarily readily apparent, but we can assure you things are still being worked on. These updates may not be communicated in a way that everybody just knows, but can easily be seen if one were to look at our repository site.

Between our own schedules and lives, we can get very busy. We try to keep things updated and help out on the forums even during lull periods. This might mean we aren’t pushing an RC or release as frequently. It may mean we’re working on other things for the project, such as can be seen if looking at our github site.

Our forums are heavily active, and this should point as an indicator to our “status” as well.

If anybody would like to see an increase in developers donating their time to making this free software, consider donating either with monetary support or by spending personal time to help with development.

FOG is an open source project - it’s even in the name. It is driven by people donating their time and resources. The releases of FOG revolve around when developers can spare a few hours throughout the week. Sometimes that will mean releases will be further, sometimes that will mean releases will be faster. That’s just the nature of our project, and many other open source projects.

Hey everybody,

I know you see me here on occasion from time to time. Life decisions have made it more difficult for me to do things I would normally be doing. Rest assured, I am still around, and while I’m not quite as active as I was in the past, it’s not because I don’t want to be.

I had to move, and as part of that I have none of my normal development stuff readily available. Part of the move made me not have a laptop, until today.

I need to setup my dev environment again, so it may take a little bit, but I will be back up.

https://news.fogproject.org/fog-1-5-10-41-officially-released/

While this maybe spur of the moment, it should officially release 1.5.10 with all relevant bug/security fixes encapsulated (among a few other features.)

This has brought a new methodology of releases in that bug/security releases should be done much more regularly.

dev-branch, historically, was a place where new development occurred (hence its name) but over the last couple of years or so it’s mainly been a bug/security thing, not really a true development approach.

This is OKAY, in my head. Why:

Well we have the master branch which is the ‘baseline’ of a verions. We have the dev-branch, which allows us to work on bugs/security issues. We have the working branches for what will eventually become master. Working is our “dev branch” but keeps proper seperation of things in my opinion.

Basically:
master -> basis for dev-branch (which merges into stable on a regular cadence - still being worked out)
working -> basis of forward development

So we effectively have:
production
staging
development well seperated.

THis may mean on the regular automated releases, no announcement or news article will be created, and I think that’s okay.

Hopefully exciting we have a release after 1.25 years

Thank you!

That’s correct. The main reason fog is constantly moving forward is because the codebase is improved upon. Major bugs tend to be addressed for the next release. We don’t do an LTS because there’s really two main people working on fog in a consistent manor. Those two are @Joe-Schmitt and myself. Debian and Libreoffice have the team too be able to perform such a feat. Their product is Opensource but they have an employment team which can afford them that luxury. FOG has a team but we make no money and as such are required to work full time jobs. We work on FOG in our free time. I’ve had the ability to even work on it from work because we used the software.

Maintaining many different versions is difficult. And we don’t have a support team. WYSIWYG and I think we’ve done pretty well on support, even if we don’t have the ability to do dedicated support for our product. 1.5 was a major step toward modernizing the GUI. 1.6 will vastly improve on this. It was only recently we kind of came up with a road map on how best to proceed. Of note, 1.5 will be maintained until 1.6 is released. 1.6 is focused on making he GUI much more modern. 1.7 will be focused mostly toward fixing and refactoring the FOG client. 1.8 will focus on making the FOS system more modular and usable. I don’t know yet for 1.9. 2.0 will bridge the gap for our rewrite based on the work from 1.5 and up. While we do plan to try to do backports where possible, it’s much easier to ask people to update to the latest version than it is to try to maintain many different versions with backports in mind. At least for what FOG does.

I doubt this will appease anybody, but it’s what I think needs to be said. We are working hard and provide support for our product as best we can. The community makes fogs support system, I think, one of the best around. Add to that and you can almost always have a developer working side by side to help and fix issues as they come up, I don’t think it’s unfair to ask users to update to a specific version. Even if there are bugs, we will always try to correct what we can, when we can. (And normally it’s a pretty quick turn around).

I’m not perfect and I’ll give you that. We don’t even have a test suite to know if things are working as intended. We have to rely on the community and suggestions are great, just understand our answers won’t always be what people want to hear.

https://news.fogproject.org/fog-1-4-0-officially-released/

https://news.fogproject.org/fog-1-4-4-officially-released/

@Clebboii Following up if you’d be willing to let us know?

Thank you!

@AUTH-IT-Center Please try the latest pull?

It addresses a potential security issue as well which partially what took me so long, my apologies

Placeholder

@AUTH-IT-Center Sorry moved these items to a new topic.

I want to get this addressed, but this is different from the double quotes issue:

Also:

please hit up your sql database:

SELECT * FROM fog.history;

likely it will see the latest entry of something along the lines if:

Task ID:  Name: Single Snapin Task - test321 has failed to save. Error: Save completed but no valid ID was assigned (insertId=0). Possible duplicate-key update or missing auto-increment.

This is what I’m seeing when I try to create a single snapin task (i’ve not tried with all-snapins yet, but one thing at a time. I am working to fix it, just trying to narrow down the why.

@AUTH-IT-Center I added another update but the error you’re seeing is a little strange because it should’ve bene addressed, I don’t know. The min() item is saying it requires a value and the approach I took was to check if there is data in the array, pass it to the min funciton otherwise set it to null (which should work if true)

Of course i don’t have much time to dig deep into this today, but my testing seemed to work without much issue.

Let me see if I can create a host without an image associated, tie a snapin and make a snapin task.

Okay thanks for that, that helped me fix that particular problem and address another elephant I didn’t realize still existed:

Non-Imaging tasks should not require an Image to create a task - which is partly (i believe) why you saw that error.

I’m only guessing here that this was a machine that did not have an image defined to it? If not there’s another rabbit hole I’m not sure I’m ready to dig into right away, but I did add corrections that non-imaging tasks shouldn’t require an image being set on the host level to create the tasking in the first place as well added some failsafes around that particular error:

$assocID = @min((array) $assocID);

Was the error it was hitting at line 496, basically with PHP 8, they made min function require a value and if assocID is empty (set just earlier) that’s why you were seeing an error. The assocID here specifically represented the image association on a storage group.

I corrected this specifically by setting assocID to null if there’s nothing in the returned assocIDs previously.

Apologies for the long winded answer.

@AUTH-IT-Center Since it’s writing a 500 can you provide the php-fpm www-error.log (if redhat based or apache2.log if debian)?

There’s likely some syntax issue I’m unaware of:

For the htmlspecialchars it’s only display representation:

When the HTML forms are built, we encode things which allows the fields to display correctly, and when you hit safe we decode them to ensure they’re stored in the DB correctly.

This leads me to believe this isn’t really the problem but there’s some other syntax issue that I may have missed/added unsuspectingly?

@The-Dealman Awesome thank you! and we did publish 1754 specifically due to this issue (manually running the automated processes just in case your org is worried at all )

@jmeyer As a matter of fact, the task requirement for storagegroupID has already been fixed it seems, I am on 2267 for working-1.6

Can you please try updating and see if you still have the same issue and if so, accurate/current screenshots of those errors please?

So thank you I can fix the requirement of the storagegroupID (likely meaning we can remove the need for the storagenodeID - which means I need to figure out a way to dynamically change required fields based on the task, but that’s not a major problem I can think through quickly.

If you can post actual screen shots/images of the error that goes a lot further because what you did made me just discard things because somehow you showed a 1.5.10.1688 image saying “it’s this problem” but that problem isn’t really true. Your issue is completely different (albeit from your side it may seem similar)

Context actually matters with these things otherwise I go down thinking “Yeah, no wonder it’s not working, they say they’re on working-1.6-beta.2262 but the image I see says totally different thing, that must be the issue.”