- Issue created by @SirClickALot
- πͺπΈSpain marcoscano Barcelona, Spain
I can't really reproduce this myself, are you able to provide the full stack trace to see if we can understand better what's going on?
Thanks!
- π¬π§United Kingdom alexpott πͺπΊπ
I would have thought a drush updatedb might have got you out of this. I think @sirclickalot might need to investigate why drush cr is not rebuilding the container correctly that points to deeper issues on the site in question.
- π¬π§United Kingdom alexpott πͺπΊπ
I've created an MR to add an empty update to force a container rebuild. I think that should address this.
-
marcoscano β
committed 2c9eb7fa on 8.x-2.x authored by
alexpott β
Issue #3509039 by alexpott: Updating to 8.x-2.0-beta20 from 8.x-2.0-...
-
marcoscano β
committed 2c9eb7fa on 8.x-2.x authored by
alexpott β
- πͺπΈSpain marcoscano Barcelona, Spain
Thank you @alexpott!
I have merged the MR since it's harmless and might help others.
@sirclickalot could you please test if this solves the issue for you?
Thanks,
- π¬π§United Kingdom SirClickALot Somerset
@marcoscano,
Yes, I can confirm that after performing a composer update to
2.0.0-beta20
I was still seeing the same error but that a subsequent database update via adrush updatedb
fixes the issue. - πͺπΈSpain marcoscano Barcelona, Spain
OK, thanks for confirming π
I've tagged -beta21 with this fix. - π¦πΊAustralia acbramley
I hit this as well on a GovCMS site. Everything was fine in CI, tests passed, etc but for some reason after deploying, the cron containers were throwing service not found errors. Very curious why a drush cr wouldn't force a container rebuild but thank you for the quick release :)