PKS cluster creation fails with error "Data too long for column 'nsxt_network_profile'
Article ID: 316733
Updated On:
Products
Issue/Introduction
-
When you try to create a PKS cluster with a network profile, it fails with an error similar to:
Error: An error occurred in the PKS API when processing -
In the /var/vcap/sys/log/pks-api/pks-api.log on PKS-API vm, you see the entries similar to:
2019-12-02 12:20:00.068 WARN 19179 --- [nio-9021-exec-4] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 1406, SQLState: 22001
2019-12-02 12:20:00.068 ERROR 19179 --- [nio-9021-exec-4] o.h.engine.jdbc.spi.SqlExceptionHelper : (conn=61) Data too long for column 'nsxt_network_profile' at row 1
2019-12-02 12:20:00.068 ERROR 19179 --- [nio-9021-exec-4] o.h.i.ExceptionMapperStandardImpl : HHH000346: Error during managed flush [org.hibernate.exception.DataException: could not execute statement]
2019-12-02 12:20:00.071 ERROR 19179 --- [nio-9021-exec-4] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement] with root cause
Environment
Cause
Network profile JSON’s total string length has a limitation of maximum of 500 characters in PKS 1.5 and earlier versions. This has been increased to 1000 characters in PKS 1.6 and will be changed to 65k in future releases.
PKS 1.6 supports increased network_profile column size but the dependent database column was not increased which results in successful creation of network_profile but the cluster creation fails with error Data too long for column 'nsxt_network_profile'
Resolution
This issue will be fixed in VMware Enterprise PKS 1.6.1 and later versions.
Workaround:
As a work around, use the network profile with maximum of 500 characters while creating the cluster.
Feedback
