Job was rejected because resource class medium, image previous is not a valid resource class
how can I fix it?
Hi @capacytron,
If you would like to pin to a previous version at this time for linux machine you need to pin to a specific tag.
Hi Team,
As i Am still waiting on support ticket created.
Could you please tell the java version used with this image ubuntu-2004:current , and also which cucmber version is best supported to that. maybe used in your projects ?
Thank you.
If you run “java --version” on a ubuntu-2004:current machine image you get
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-120.04)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-120.04, mixed mode, sharing)
As for which version of Cucumber to use it would be best to check their site/forums for a recommendation.
2 Likes
Since hitting a brownout yesterday, I’m now getting the error:
Job was rejected because resource class xlarge, image ubuntu-2204:latest is not a valid resource class
Your docs still imply that the normal machine classes apply and don’t say anything about not being able to use xlarge with some images. Are resource classes changing alongside this as well? Or have we hit a bug?
latest is not a valid tag. Please try current.
d’oh! yes of course, I always forget the machine images use different terminology than the docker side does. 
1 Like
Can CircleCI please fix the documentation at the top of this page??
This old-style machine image clearly uses the tags current, and edge (and does not use the tag previous), but the top of this page says the tags for use are default, previous and edge.
Please provide clear and correct documentation. The problems we run into when our pipelines fail are compounded by this confusion.
^ Note the listing of the tags which do not include default or previous.
Hi @pwillis-eiq,
Thank you for calling this out. I have updated the above discuss post to remove previous.
We do currently support:
ubuntu-2004:current
ubuntu-2004:edge
ubuntu-2204:current
ubuntu-2204:edge
and default
Also could you please downgrade google browser version till Chrome version 114 which supports the latest crhromedriver versions
current browser version is Current browser version is 121.0.6167.139 , which was not the case with previous linux images
Caused by: org.openqa.selenium.SessionNotCreatedException: session not created: This version of ChromeDriver 114.0.5735.90only supports Chrome version 114.
Current browser version is 121.0.6167.139 with binary path /usr/bin/google-chrome
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘ip-10-0-20-240’, ip: ‘10.0.20.240’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘5.15.0-1052-aws’, java.version: ‘17.0.9’
Driver info: driver.version: ChromeDriver
In previous images I believe the crhome browser version was 114 or below .
It would be best if you replied to one of the CircleCI staff members with that request. I’m just an external volunteer, so I can not do anything to change who published images are built.
@Neeraj I would suggest tagging to an older version that is not deprecated for the time being if this is causing you problems.
Hi @brentmmarks could you please suggest which version to use, as i was using previously the version ubuntu-2004:202201-02, which has been deprecated.
ubuntu-2004:2023.07.1 should give you an image with chromedriver 114 I believe
1 Like
hi @brentmmarks
could you elaborate please? “default” failed with
" was rejected because resource class medium, image default is not a valid resource class"
same error… how should I fix it? I need medium ubuntu
Not sure how your config is setup but:
jobs:
test:
machine:
image: default
resource_class: medium
steps:
- run: echo hello
is how I have default setup and should work
Hi, is there a plan to update the image on previous versions of the CircleCI Orbs circleci/aws-cli and circleci/aws-ecr ? We’re on version 3.x.x for aws-cli and version 7.x.x for ecr, we do not want to upgrade major versions just to comply with this new image requirement. CircleCI should push new minor versions to v3 and v7 of those orbs with the new image.
Hi @thejollyrogers,
Believe the orb allows you to override the image for these orbs so a minor version bump should not be needed.
Greetings,
I’ve encountered the same error message:
“Your job is utilizing a deprecated image ‘ubuntu-2004:202010-01’. It’s advised to switch to a more recent image.”
Below, I’ve included my config.yml file and Dockerfile for reference. Any assistance in resolving this issue would be greatly appreciated.
version: 2.1
orbs:
aws-ecr: circleci/aws-ecr@7.0.0
aws-ecs: circleci/aws-ecs@2.2.1
workflows:
build_and_push_image:
jobs:
- aws-ecr/build-and-push-image:
context: AWS
repo: live-data-test
tag: "latest"
dockerfile: Dockerfile
path: .
filters:
branches:
only: main
- aws-ecs/deploy-service-update:
context: AWS
cluster-name: 'SQA'
container-image-name-updates: 'container=live-data-test, tag=latest'
family: 'live-data-test'
requires:
- aws-ecr/build-and-push-image
Dockerfile:
#base Image
FROM node:current-alpine3.18
#current working directory of the project
WORKDIR /usr/src/app
# files necessary for the built
COPY package*.json ./
# command to install node modules
RUN npm install
# modules necessary for the build
RUN npm install -g wscat
RUN npm install -g pm2
# copy the rest of the files into the container that is in the directory
COPY . .
# commands to run on each container deployment
CMD [ "pm2-runtime", "index.js" ]
You can either upgrade your reference to aws-ecr orb to 9.0.3 or override the image param in this orb in your config.