Change successfully merged at revision 3117ab5b5c78e26dc6bf3b61205f5f07dd0d33e3
--
https://code.launchpad.net/~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress/+merge/396065
Your team Wordpress Charmers is subscribed to branch charm-k8s-wordpress:master.
--
Mailing list:
The proposal to merge
~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress:maintenance-status into
charm-k8s-wordpress:master has been updated.
Status: Needs review => Approved
For more details, see:
The proposal to merge
~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress:maintenance-status into
charm-k8s-wordpress:master has been updated.
Status: Approved => Needs review
For more details, see:
Failed to merge change (unable to merge source repository due to conflicts),
setting status to needs review.
--
https://code.launchpad.net/~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress/+merge/396065
Your team Wordpress Charmers is subscribed to branch charm-k8s-wordpress:master.
--
The proposal to merge
~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress:maintenance-status into
charm-k8s-wordpress:master has been updated.
Status: Needs review => Approved
For more details, see:
Review: Approve
Ok. I guess the issue here is that we were relying on Juju setting the active
status for us, and it won't do that unless it has done sort of action that
warrants it (such as spinning up new pods with a new spec). I don't think it is
clear when and why Juju updates the workload
This merge proposal is being monitored by mergebot. Change the status to
Approved to merge.
--
https://code.launchpad.net/~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress/+merge/396065
Your team Wordpress Charmers is requested to review the proposed merge of
Tom Haddon has proposed merging
~mthaddon/charm-k8s-wordpress/+git/charm-k8s-wordpress:maintenance-status into
charm-k8s-wordpress:master.
Commit message:
Fix unit status to stay in 'active' once configured
Requested reviews:
Wordpress Charmers (wordpress-charmers)
For more details, see:
8 matches
Mail list logo