Description of problem:
The generated RHEL7 image for MapR don't work because they try to start mariadb.service, but mariadb-server is not installed so it fails because the unit is not found. That is probably due to mapping issues regarding mysql and RHEL (https://github.com/openstack/sahara-image-elements/blob/3446f21130a137eb02c642fe086454c8ef754f57/elements/mysql/pkg-map#L23).
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
This looks like a blocker for the two Sahara RFEs, that are targeted for OSP11:
Is this an image different than a regular overcloud image? If so, where is this generated?
These are the packages that are installed by default on an overcloud image:
And there is a systemctl service "mariadb.service" as well.
Are there any other logs available, showing the error you saw?
I will leave more details to Raissa, but:
- this is not an overcloud image. This is a user image, the one you run inside an existing overcloud. No tripleo involvement here.
- this was generated with sahara-image-elements. My guess is the mapping of the components in the mysql element of DIB is incorrect for RHEL7 and mariadb-server is not installed (it tries to install mysql-server and it fails during the building process). Interesting to know that this was informally tested for Newton and it was working, so not sure what happened (maybe a change in DIB).
Luigi summed it up, it is the RHEL 7 image we use to spawn a cluster in Sahara - in this case using the MapR plugin. I logged into the instances created with the image and checked that mariadb-server wasn't installed, so the log is pretty straightforward:
Details: Cluster in Error state with a message below:
Creating cluster failed for the following reason(s): RemoteCommandException: Error during command execution: "service mariadb restart"
Return code: 5
Redirecting to /bin/systemctl restart mariadb.service
Failed to restart mariadb.service: Unit not found.
MapR clusters spawned with RHEL images generated with sahara-image-elements now start successfully.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.