Bug 29886 – EC2 image with UCS 3.1-0-errata

Bug 29886 - EC2 image with UCS 3.1-0-errata


Summary:	EC2 image with UCS 3.1-0-errata

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.1
Assigned To:	Janek Walkenhorst
QA Contact:	Stefan Gohmann

URL:
Keywords:	interim-5

Depends on:	29885
Blocks:
	Show dependency tree / graph

Reported:	2012-12-21 22:39 CET by Stefan Gohmann
Modified:	2016-12-07 10:00 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2012-12-21 22:39:35 CET

A new Amazon EC2 image should be created and released.

Comment 1 Janek Walkenhorst

2013-01-15 15:54:40 CET

Updated old image, done "auto remove", reinstalled u-setup-boot.
→ ami-f2f1fe86

Comment 2 Stefan Gohmann

2013-01-16 13:35:49 CET

Tests were successful.

Installing and joining a complete domain: DC Master + DC Backup + DC Slave + Memberserver

The installation via the app center was successful too.

Comment 3 Janek Walkenhorst

2013-01-16 13:43:18 CET

The AMI is now public.

Comment 4 Stefan Gohmann

2013-01-18 13:26:23 CET

Bug #29885#c5 also affects the EC2 image. At least if you use a VPC and change the IP address in UMC appliance.

Please add the following lines and create a new image:

# Ensure s4connector will be restated after the configuration
cat >/usr/lib/univention-system-setup/appliance-hooks.d/s4connector <<__EOF__
#!/bin/sh
test -x /etc/init.d/univention-s4-connector &&
/etc/init.d/univention-s4-connector restart
__EOF__
chmod +x /usr/lib/univention-system-setup/appliance-hooks.d/s4connector

Comment 5 Janek Walkenhorst

2013-01-21 12:10:20 CET

(In reply to comment #4)
> Bug #29885#c5 also affects the EC2 image. At least if you use a VPC and change
> the IP address in UMC appliance.
> 
> Please add the following lines and create a new image:
> 
> # Ensure s4connector will be restated after the configuration
> cat >/usr/lib/univention-system-setup/appliance-hooks.d/s4connector <<__EOF__
> #!/bin/sh
> test -x /etc/init.d/univention-s4-connector &&
> /etc/init.d/univention-s4-connector restart
> __EOF__
> chmod +x /usr/lib/univention-system-setup/appliance-hooks.d/s4connector
Created rev3 image → ami-60515f14

Comment 6 Janek Walkenhorst

2013-01-21 15:33:12 CET

Reopen until a fix is found:
> Bug #29885#c7
> The issue remains unfixed. The script is present, but the connector is still
> not working out-of-the-box (i.e. has to be restarted manually).

Comment 7 Janek Walkenhorst

2013-02-14 14:47:35 CET

Updated old image, extended disk to 10 "GB", applied dbus and appliance-listener fixes, reinstalled uss-boot.
→ ami-82fff6f6

Comment 8 Stefan Gohmann

2013-02-14 15:34:50 CET

(In reply to comment #7)
> Updated old image, extended disk to 10 "GB", applied dbus and
> appliance-listener fixes, reinstalled uss-boot.
> → ami-82fff6f6

OK.

I configured a master, slave and a member. The connector works and I could install xrdp.