Bug 1216193 - WordPress on OpenShift won't update
Summary: WordPress on OpenShift won't update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Templates
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Michal Fojtik
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-28 17:43 UTC by Eric Christensen
Modified: 2017-05-31 18:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-31 18:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Christensen 2015-04-28 17:43:05 UTC
Description of problem: WordPress can't be upgraded from the Dashboard.

How reproducible:  Always


Steps to Reproduce:
1. See an update is available.
2. Press the update button.
3. See it go through the update process.

Actual results: Get the welcome screen for the existing version.  (AKA, it didn't upgrade.)


Expected results: It updates to the latest version.


Additional info: This is the security blog on a medium gear.

Comment 1 Eric Christensen 2015-05-04 18:38:38 UTC
WP support ticket: https://wordpress.org/support/topic/jetpack-comments-failing?replies=1

I've tried to allocate additional memory in the wp-config.php file (to 96M) but I see no change.  Can't seem to find where it's defined in my gear (or is it?).

Comment 3 Michal Fojtik 2015-05-14 11:53:10 UTC
Eric, can you tell me what version of Wordpress you current run? Also when did you created the gear and how (did you use our quickstart, or you uploaded it using GIT?).

Is there anything interesting in logs (httpd logs?)

Comment 4 Eric Christensen 2015-05-18 13:17:05 UTC
(In reply to Michal Fojtik from comment #3)
> Eric, can you tell me what version of Wordpress you current run? Also when
> did you created the gear and how (did you use our quickstart, or you
> uploaded it using GIT?).

This gear was originally created probably two years ago.  It was moved to a medium gear last September during the Bash vulnerability announcement.  Since it was originally spun up it's been handling the automatic updates without too many troubles.  Sometimes it would fail to update due to some unknown problem and then, maybe a few hours later, it would upgrade and all would be well again.

Currently running version 4.1 trying to upgrade to 4.2.2.

> Is there anything interesting in logs (httpd logs?)

Nope, I've not found anything in the logs, unfortunately.

Comment 5 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.


Note You need to log in before you can comment on or make changes to this bug.