TRITON-2312: update sdc-sdc base image to triton-origin-x86_64-21.4.0

Details

Issue Type:Task
Priority:5 - Low
Status:Resolved
Created at:2022-06-21T02:15:52.134Z
Updated at:2022-06-29T23:36:01.619Z

People

Created by:Brian Bennett
Reported by:Brian Bennett
Assigned to:Brian Bennett

Fix Versions

2022-06-30 Uses... the street finds its own (Release Date: 2022-06-30)

Related Issues

Related Links

Description

A complication is that the tests seem to have never worked, or at least have not worked in a very long time.

Comments

Comment by Brian Bennett
Created at 2022-06-21T02:29:56.275Z
Updated at 2022-06-22T00:21:00.329Z

Things to test (most if this is from the GZ, not in the sdc zone itself):

Things already successfully tested (at least minimally) above will have a green check.


Comment by Jira Bot
Created at 2022-06-23T20:22:14.602Z

sdc-sdc commit 02a103ba9a8a9c901c3dd13c54a7f0f5ecbe89e6 (branch master, by Brian Bennett)

TRITON-2312 update sdc-sdc base image to triton-origin-x86_64-21.4.0 (#23)

TRITON-2312 update sdc-sdc base image to triton-origin-x86_64-21.4.0 (update node only)
TRITON-2312 update sdc-sdc base image to triton-origin-x86_64-21.4.0 (image update)
Reviewed by: Dan McDonald <danmcd@kebe.com>


Comment by Brian Bennett
Created at 2022-06-23T20:34:15.387Z
Updated at 2022-06-23T20:38:22.014Z

This will also require an update to sdc-headnode for the global zone for joyent-imgadm and to add images-imgadm.

This gives us a few options:

  1. Just add images-imgadm as a symlink to wrap.sh
  2. Just add images-imgadm as a copy of wrap.sh like joyent-imgadm is, and leave joyent-imgadm alone
  3. Make images-imgadm a copy of wrap and symlink joyent-imgadm to images-imgadm.
  4. Make both images-imgadm and joyent-imgadm a symlink to wrap.sh

As near as I can tell, there’s no reason that joyent-imgadm is not a symlink.

For these reasons, option 4 above (make both a symlink) makes the most sense to me.