Your question on chroma/IML might be better serviced over at https://gitter.im/intel-hpdd/intel-manager-for-lustre . Good luck. -Cory
-- From: Yugendra Guvvala <[email protected]> Date: Thursday, May 31, 2018 at 3:08 PM To: Cory Spitz <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [lustre-discuss] Upgrading IEEL from 2.5 to 2.10.4 Hi, We are following https://github.com/intel-hpdd/intel-manager-for-lustre/issues/152 to upgrade from LUSTRE 2.5.34.1 to Lustre 2.10.4 LTS & IML 4.0.6 but ran into this issue while migrating database. I also opened a issue but if any one has more information please let us know . [root@iml chroma]# chroma-config setup -v Starting setup... DB already accessible Creating database tables... Syncing... Creating tables ... Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) Migrating... Running migrations for tastypie: - Nothing to migrate. - Loading initial data for tastypie. Installed 0 object(s) from 0 fixture(s) Running migrations for chroma_core: - Migrating forwards to 0039_add_primary_umtm_stepresults. > chroma_core:0023_auto__add_unconfigurersyslogjob__add_getcorosyncstatejob__add_pacemake FATAL ERROR - The following SQL query failed: insert into chroma_core_corosyncconfiguration (state_modified_at, state, immutable_state, content_type_id, host_id) values ('2018-05-30 16:03:37.755588', 'started', 'f', 161, 9) The error was: null value in column "corosync_reported_up" violates not-null constraint DETAIL: Failing row contains (1, 2018-05-30 16:03:37.755588+00, started, f, null, 161, 9, null, null). Error in migration: chroma_core:0023_auto__add_unconfigurersyslogjob__add_getcorosyncstatejob__add_pacemake Traceback (most recent call last): File "/usr/bin/chroma-config", line 10, in <module> load_entry_point('chroma-manager==4.0.6.0', 'console_scripts', 'chroma-config')() File "/usr/share/chroma-manager/chroma_core/lib/service_config.py", line 878, in chroma_config errors = service_config.setup(username, password, ntpserver, check_db_space) File "/usr/share/chroma-manager/chroma_core/lib/service_config.py", line 593, in setup error = self._setup_database(username, password, check_db_space) File "/usr/share/chroma-manager/chroma_core/lib/service_config.py", line 563, in _setup_database self._syncdb() File "/usr/share/chroma-manager/chroma_core/lib/service_config.py", line 545, in _syncdb ManagementUtility(args).execute() File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/site-packages/south/management/commands/syncdb.py", line 103, in handle_noargs management.call_command('migrate', **options) File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 150, in call_command return klass.execute(*args, **defaults) File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle ignore_ghosts = ignore_ghosts, File "/usr/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app success = migrator.migrate_many(target, workplan, database) File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many result = migrator.__class__.migrate_many(migrator, target, migrations, database) File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many result = self.migrate(migration, database) File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate result = self.run(migration, database) File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 114, in run return self.run_migration(migration, database) File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 84, in run_migration migration_function() File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 60, in <lambda> return (lambda: direction(orm)) File "/usr/share/chroma-manager/chroma_core/migrations/0023_auto__add_unconfigurersyslogjob__add_getcorosyncstatejob__add_pacemake.py", line 258, in forwards create_action_record(model_name, state, host_id) File "/usr/share/chroma-manager/chroma_core/migrations/0023_auto__add_unconfigurersyslogjob__add_getcorosyncstatejob__add_pacemake.py", line 242, in create_action_record "values ('%s', '%s', 'f', %s, %s)" % (model_name, datetime.datetime.now(), state, ct.id<http://ct.id>, host_id)) File "/usr/lib/python2.7/site-packages/south/db/generic.py", line 282, in execute cursor.execute(sql, params) File "/usr/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 52, in execute return self.cursor.execute(query, args) django.db.utils.IntegrityError: null value in column "corosync_reported_up" violates not-null constraint DETAIL: Failing row contains (1, 2018-05-30 16:03:37.755588+00, started, f, null, 161, 9, null, null). Thanks, Yugi On May 21, 2018, at 1:15 PM, Yugendra Guvvala <[email protected]<mailto:[email protected]>> wrote: Hi Cory, Thank you, I see for the link that Interoperability Support is only 2.9.x so I understand that we cant have client modules at version 2.4.x. also I see supported kernel versions. Thanks, Yugi On Mon, May 21, 2018 at 12:40 PM, Cory Spitz <[email protected]<mailto:[email protected]>> wrote: Hello, Yugi. Please note that 2.10.3 is the latest LTS release and 2.10.4 is about to be released very soon. RHEL/CentOS 6.9 clients and RHEL/CentOS 7.4 servers are supported in 2.10.3. See: http://wiki.lustre.org/Lustre_2.10.3_Changelog. 2.10.4 will add support for RHEL/CentOS 7.5 servers. -Cory -- From: lustre-discuss <[email protected]<mailto:[email protected]>> on behalf of Yugendra Guvvala <[email protected]<mailto:[email protected]>> Date: Monday, May 21, 2018 at 11:12 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [lustre-discuss] (no subject) Hi, We currently run Luster 2.4 We are looking to upgrade to Lustre Version 2.10.2, Do we have to upgrade Lustre Client modules or is it Backward compatible? What are the compatible kernel versions for 2.10.2 on both server and client modules. We want to keep clients OS level at CENTOS 6.8 and upgrade Storage servers to CentOS 7.4. We are trying to phase this upgrade process to Servers first and then Clients and with all softwares, Drivers compatibility we are trying to find best upgrade path any suggestions are welcome. We could only find OS version and not kernel versions on support matrix here: https://wiki.hpdd.intel.com/display/PUB/Lustre+Support+Matrix Thanks, Yugi -- Thanks, Yugendra Guvvala | HPC Technologist | Cambridge Computer | "Artists in Data Storage" Direct: 781-250-3273 | Cell: 806-773-4464 | [email protected]<mailto:[email protected]> | www.cambridgecomputer.com<http://www.cambridgecomputer.com/>
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
