By using AWS re:Post, you agree to the Terms of Use
/AWS Managed Services/

Questions tagged with AWS Managed Services

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Aurora upgrade 2 to 3 / MySql 5.7 to 8.0: potential bug in pre-check validation (depreciated words)

We have noticed that the pre-checks for the upgrade of MySQL 5.7 to MySQL 8 are having issues with character combinations that "resemble" depreciated words. For example, the depreciated "Group By ... DESC" is one of those constructs "[https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.html#USER_UpgradeDBInstance.MySQL.57to80Prechecks]()" "There must be no queries and stored program definitions from MySQL 8.0.12 or lower that use ASC or DESC qualifiers for GROUP BY clauses." While our stored procedures use Group by's, there is no associated "DESC" word with them. However, the character sequence does appear in the stored procedure in various forms: * There is a call to another stored procedure called "update_fc**desc**ription();". It has the characters "desc" within the name * There are columns in the queries (table columns) with the name "blah**Desc**riptionblah" * There is a block comment that has the word "**Desc**ription:" that describes the stored procedure (documentation) However, there are no "DESC" words associated with the "Group by". For testing, * I deleted the comments word, and that issue no longer appeared as an error * I renamed the call to the other stored procedure update_fc**desc**ription(); to update_fc**dxexscxrixp**tion();, and that issue no longer appeared as an error * The columns that have the characters "desc" I couldn't work around without a lot of changing to the stored procedure It seems that there is a Stackoverflow question outlining this behavior too: [https://stackoverflow.com/questions/71412470/aws-mysql-aurora-major-version-2-3-upgrade-pre-checks-obsolete-procedure]() Also, a "re:Post" question too: [https://repost.aws/questions/QUWJzlcpitRoGM0woZVOylBQ/aurora-2-to-3-mysql-5-7-to-8-0-upgrade-pre-check-incorrect-validation-on-store-procedure]() This is clearly a bug in the pre-check process and is limiting our upgrade from MySQL 5.7 to 8. Any updates on this being fixed/addressed? Thank you.
0
answers
0
votes
28
views
asked 2 days ago

SUSE 15 SP3 stucked on "status check 1/2" during reboot after update to latest version.

Hello Team, our SUSE 15 SP3 instance(r4.2xlarge) is stucked in "status check 1/2" during reboot after upgraded it latest version. Here are some logs as well. Please share some solutions. **"cloud-init[1276]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | [ 41.805561] cloud-init[1276]: ci-info: +--------+------+-----------+-----------+-------+------------+ [ 41.810798] cloud-init[1276]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | [ 41.816025] cloud-init[1276]: ci-info: | lo | True | ::1/128 | . | host | . | [ 41.820613] cloud-init[1276]: ci-info: +--------+------+-----------+-----------+-------+------------+ [ 41.824672] cloud-init[1276]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ [ 41.828212] cloud-init[1276]: ci-info: +-------+-------------+---------+-----------+-------+ [ 41.832368] cloud-init[1276]: ci-info: | Route | Destination | Gateway | Interface | Flags | [ 41.837993] cloud-init[1276]: ci-info: +-------+-------------+---------+-----------+-------+ [ 41.842556] cloud-init[1276]: ci-info: +-------+-------------+--------[ 0.000000] Linux version 5.3.18-150300.59.49-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Mon Feb 7 14:40:20 UTC 2022 (77d9d02)" ** Thanks, Bhupendra +91-XXXXXXXXXX Edit: Removed personally identifiable information (phone number) per Community Guidelines.
0
answers
0
votes
11
views
asked 4 months ago
  • 1
  • 90 / page