Your message dated Tue, 18 Nov 2014 08:13:04 +0800
with message-id <546a8f10.1040...@debian.org>
and subject line Re: [PKG-Openstack-devel] Bug#769764: ironic-common: fails to 
upgrade from 'sid': No support for ALTER of constraints in SQLite dialect
has caused the Debian Bug report #769764,
regarding ironic-common: fails to upgrade from 'sid': No support for ALTER of 
constraints in SQLite dialect
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
769764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ironic-common
Version: 2014.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

>From the attached log (scroll to the bottom...):

  Setting up ironic-common (2014.2-2) ...
  Installing new version of config file 
/etc/ironic/rootwrap.d/ironic-utils.filters ...
  PKG-Openstack now calling: dbc_go ironic-common configure 2014.1-10
  dbconfig-common: writing config to /etc/dbconfig-common/ironic-common.conf
  INFO  [alembic.migration] Context impl SQLiteImpl.
  INFO  [alembic.migration] Will assume non-transactional DDL.
  INFO  [alembic.migration] Running upgrade 3cb628139ea4 -> 31baaf680d2b, Add 
Node instance info
  INFO  [alembic.migration] Running upgrade 31baaf680d2b -> 3bea56f25597, add 
unique constraint to instance_uuid
  CRITI [ironic] NotImplementedError: No support for ALTER of constraints in 
SQLite dialect
  Traceback (most recent call last):
    File "/usr/bin/ironic-dbsync", line 10, in <module>
      sys.exit(main())
    File "/usr/lib/python2.7/dist-packages/ironic/cmd/dbsync.py", line 100, in 
main
      CONF.command.func()
    File "/usr/lib/python2.7/dist-packages/ironic/cmd/dbsync.py", line 36, in 
upgrade
      migration.upgrade(CONF.command.revision)
    File "/usr/lib/python2.7/dist-packages/ironic/db/migration.py", line 36, in 
upgrade
      return get_backend().upgrade(version)
    File "/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/migration.py", 
line 56, in upgrade
      alembic.command.upgrade(config, revision or 'head')
    File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 125, in 
upgrade
      script.run_env()
    File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 203, in 
run_env
      util.load_python_file(self.dir, 'env.py')
    File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 212, in 
load_python_file
      module = load_module_py(module_id, path)
    File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 58, in 
load_module_py
      mod = imp.load_source(module_id, path, fp)
    File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/env.py", line 
54, in <module>
      run_migrations_online()
    File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/env.py", line 
51, in run_migrations_online
      context.run_migrations()
    File "<string>", line 7, in run_migrations
    File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 688, 
in run_migrations
      self.get_context().run_migrations(**kw)
    File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 258, in 
run_migrations
      change(**kw)
    File 
"/usr/lib/python2.7/dist-packages/ironic/db/sqlalchemy/alembic/versions/3bea56f25597_add_unique_constraint_to_instance_uuid.py",
 line 33, in upgrade
      ["instance_uuid"])
    File "<string>", line 7, in create_unique_constraint
    File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 621, in 
create_unique_constraint
      schema=schema, **kw)
    File "/usr/lib/python2.7/dist-packages/alembic/ddl/sqlite.py", line 21, in 
add_constraint
      "No support for ALTER of constraints in SQLite dialect")
  NotImplementedError: No support for ALTER of constraints in SQLite dialect
  dpkg: error processing package ironic-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.19-13) ...
  Errors were encountered while processing:
   ironic-common


cheers,

Andreas

Attachment: ironic-common_2014.2-2.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
On 11/16/2014 06:35 PM, Andreas Beckmann wrote:
> Package: ironic-common
> Version: 2014.2-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails.
> 
> cheers,
> 
> Andreas

Andreas,

First, thanks a lot for all of your bug reports. It is very helpful.

But for this particular one, I don't think this helps, because Ironic
2014.1.x should be considered a techno. preview only. In Icehouse, there
was not even a driver for Nova so that it could use Ironic, making
Ironic effectively useless.

So I don't think there was even one person what used Ironic for Icehouse
in production.

I also asked for Ironic to be removed from Jessie for this reason.

Therefore, I'm sorry, but I will not work on fixing this bug (largely,
because I don't think it will help any users, because there is no user
for Ironic 2014.1.x). For me, the only time when Ironic starts to be
useful is with the Juno release (ie: 2014.2.x), so I will only put some
upgrades efforts starting on this release.

More over, this issue is, I believe, only happening when using SQLite,
which anyway, nobody uses (I maintain it only so that piuparts of this
kind can succeed...).

Therefore, closing this bug, without attempting to solve it.

If anyone differs *AND* cares enough to provide a patch, then I will
consider reopen this bug, apply the patch, and upload the fix.

Cheers,

Thomas Goirand (zigo)

P.S: I do care a lot more about the other reports, like the ones for
Trove, which I'll try to fix ASAP.

--- End Message ---

Reply via email to