FOG 1.3.5 RC 3 Released
(Had mistake when saved proper link is accurate though).
@falko Found the problem. My re-push earlier had me debugging a separate issue. This debugging test was accidentally left in.
@butch2861 Found, patched and published.
cannot get to Create new host link after updating to version 1.3.5-rc-3; says page isnt working…err_empty_response
link broken: http://fogserver/fog/management/?node=host&sub=add
Updated to rc3 and now when I click Create new Host takes me to a dead page…all others seem to work okay.
This link is BROKE: http://fogserver/fog/management/?node=host&sub=add
just installed 1.3.5 RC3, seems to report in fog log as 1.3.5-RC-2 still with an error
08/02/2017 21:58 Client-Info Server Version: 1.3.5-RC-2
08/02/2017 21:58 Middleware::Response ERROR: Unable to get subsection
08/02/2017 21:58 Middleware::Response ERROR: Object reference not set to an instance of an object.
@Tom-Elliott Okay, that makes sense. Thank you.
The idea is dev->test->prod
Dev is current working test is the rcs and prod is the stable
@THEMCV working 135 is the current “dev” branch if you will where devbranch is the public dev branch
@Wayne-Workman Cool, thanks. Wasn’t sure if this was “higher” than working-1.3.5. I’ve made the mistake of accidentally installing an older version before.
Wayne Workman last edited by Wayne Workman
@THEMCV Yes, you can.
Inside of your
git pull;git checkout dev-branch;cd bin;./installfog.sh -y
;just separates out the commands, but if you copy/paste that whole thing then it’ll do all of it in order.
Can we upgrade to 1.3.5 RC3 if we’re on the working-1.3.5 branch?
I think i threw it in for the RC-1 thing.
Basically I’ve set the refind.conf to ensure “internal” as most of you were saying that seemed to work the best.
sudburr last edited by
Whether it is this RC or happened between 1.3.4 and now, I like what you’ve done to the UEFI network boot. It has solved an issue I had with Lenovo M72z being unable to successfully use any EFI exit type from the FOG menu.