Are you deleting all of the contents from /usr/share/openstack-
dashboard/static/ prior to collecting/compressing static assets?
If so, I don't think this is something that you should be doing, since
part of the package install copies the contents of openstack_dashboard/
to /usr/share/openstack-da
I consider 'system-upgrade' as the fix for this.
Either add config that does:
system_updgrade: enabled: True
or run
curtin system-upgrade
as a late_command
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New => Fix Committed
** Changed
** Changed in: cloud-archive
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1563714
Title:
[FFe][SRU] Ceph Jewel stable release
To manage notif
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => Triaged
** Changed in: cloud-archive/mitaka
Importance: Undecided => High
--
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1449099
T
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification b
Public bug reported:
in cloud-init users can install packages via cloud-config:
#cloud-config
packages: [apache2]
Due to some intricacies of systemd and service installation that doesn't work
all that well.
We fixed the issue for simple services that do not have any dependencies on
other servic
** Description changed:
Using the following cloud config, apache2 will fail to start on
installation on Xenial:
#cloud-config
packages:
- apache2
See for example:
$ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image
ubuntu-1604-xenial-v20160420c --image-pro
> This behaviour of installing packages or configuring your system while the
> system isn't booted yet might also bite you in other cases (it certainly bit
> me a number of cases). Maybe we should discuss how to move that after the
> boot? I do that in
> https://git.launchpad.net/~ubuntu-release/+g
Pitti, in reponse to comment 5 above:
> > d.) output of runlevel is stored in RL and then it goes looking for an
> > SLINK or SSLINK (/etc/rc$RL.d/S??apache2 or /etc/rcS.d/S??apache2). Neither
> > of these exist so it exits without starting the service.
> To be sure we are talking about the same t
Thanks for the bug report and the fix.
Committed in trunk. I will try to get this uploaded to yakkety and to xenial
today.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init
Status:
I spoke with cyphermox, and it seems that probably the right way for
this to happen is for cloud-init to prompt at install time at the proper
priority and then the installer will ask. Alternatively, we could seed
the question in the installer preseed so there is no prompt and it is
disabled.
** A
12 matches
Mail list logo
